Re: Separate SSL Server
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 11057
interpreted = N
texte = >At 9:27 AM 4/26/97, Gary Richter altered the fabric of cyberspace, >writing: > > >> >> I beg to differ with you on this one. The file has nothing to do if the >> doc is secure or not. It is done by the server software. The simple thing >> to do if you are worried about somebody typing in a long path name to a >> secure doc from http vs https is have the non secure pages serve .html and >> have the secure server dish out .htm (no l). We have tested this already >> and by setting up suffix mapping in webstar you can control this easily. >> Take any file on your hard disk and copy it and rename it to .htm. Make >> sure your suffix mapping is set in the non-secure server to NOT serve .htm. >> Try to load the page. You get an alert box that says this document >> contains no data. Not an issue running both on the same box. >> > >Gary, > >Your right! This would seem to work. Perhaps their is a solution to >running both ssl and non ssl servers on the same box. Instead of .htm (for >sucure pages) make up your own suffix and map it in WebStar SSL. Perhaps >something like .ssl or .secure. > >Can you tell WebCat what suffix to use when generating a 'pickup' url? > >Can you change server name when ssl is called? I.E. http://www.abc.com to >https://secure.abc.com ? > >Tell me more.... > ><--Glenn--> Somebody else is gonna have to take it from here, we are purely data base and page creation on the fly using WebCat currently. We don't plan to tackle the shopping issue until June. Have a ton of other stuff to do first. We saw Grants message about running them both on the same server and my assitant rasied the same question you did. Then this morning he tried this using the .html vs .htm to make sure somebody could not get into pages where they don't belong. How all this ties together with the [cart] function needs to be explained by either Ken (the public expert) or Grant or Jay (the PCS experts). In our minds the concept should work unless there is a quirk in the commerce stuff we don't have a grasp of yet.Regarding the secure.abc.com, again that is over our heads and how the digital id relates to a single domain. It is within your domain so the concept sounds reasonable. But a digital ID expert will have to chime in on this.=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com ===============================================
Associated Messages, from the most recent to the oldest:
>At 9:27 AM 4/26/97, Gary Richter altered the fabric of cyberspace, >writing: > > >> >> I beg to differ with you on this one. The file has nothing to do if the >> doc is secure or not. It is done by the server software. The simple thing >> to do if you are worried about somebody typing in a long path name to a >> secure doc from http vs https is have the non secure pages serve .html and >> have the secure server dish out .htm (no l). We have tested this already >> and by setting up suffix mapping in webstar you can control this easily. >> Take any file on your hard disk and copy it and rename it to .htm. Make >> sure your suffix mapping is set in the non-secure server to NOT serve .htm. >> Try to load the page. You get an alert box that says this document >> contains no data. Not an issue running both on the same box. >> > >Gary, > >Your right! This would seem to work. Perhaps their is a solution to >running both ssl and non ssl servers on the same box. Instead of .htm (for >sucure pages) make up your own suffix and map it in WebStar SSL. Perhaps >something like .ssl or .secure. > >Can you tell WebCat what suffix to use when generating a 'pickup' url? > >Can you change server name when ssl is called? I.E. http://www.abc.com to >https://secure.abc.com ? > >Tell me more.... > ><--Glenn--> Somebody else is gonna have to take it from here, we are purely data base and page creation on the fly using WebCat currently. We don't plan to tackle the shopping issue until June. Have a ton of other stuff to do first. We saw Grants message about running them both on the same server and my assitant rasied the same question you did. Then this morning he tried this using the .html vs .htm to make sure somebody could not get into pages where they don't belong. How all this ties together with the
[cart] function needs to be explained by either Ken (the public expert) or Grant or Jay (the PCS experts). In our minds the concept should work unless there is a quirk in the commerce stuff we don't have a grasp of yet.Regarding the secure.abc.com, again that is over our heads and how the digital id relates to a single domain. It is within your domain so the concept sounds reasonable. But a digital ID expert will have to chime in on this.=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com ===============================================
grichter@panavise.com (Gary Richter)
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
[object] context (2002)
WebCatalog can't find database (1997)
Country & Ship-to address & other fields ? (1997)
Problem with summary on date / inconsequent webcat behaviour (1998)
Sorting a [listfiles] (2003)
Re: (1998)
Country & Ship-to address & other fields ? (1997)
HELP WITH DATES (1997)
Serving images from databases (1998)
Tiny Store: Remove Line Item? (2000)
Likelihood of a duplicate (2005)
Emailer setup (1997)
% (mod) was looping table rows (1999)
passing info to thankyou.tpl (1998)
HELP WITH DATES (1997)
Accessing Server Environment Variables (2003)
WebCat2: Items xx to xx shown, etc. (1997)
Hiding Email Addresses (2003)
Feature requests (1998)
Roundup function? (1997)