Re: Detecting SSL or port
This WebDNA talk-list message is from 2005
It keeps the original formatting.
numero = 60956
interpreted = N
texte = Morten Madsen wrote:> I want to make sure that the customers have a secure connection during> checkout. In ASP it is very easy to get information about which port the> client is using on the server (Request.ServerVariables("SERVER_PORT")),> PSEUDO: if the port = 80 redirect to HTTPS://rightside - if it is 443 do> nothing.One easy way to do it is to require SSL for a specific URL on the server (this is commonly available on all web servers I have experience with) and then place your checkout files in that directory only. Then you "know" that the only time someone can access that file is via SSL and you are safe.FWIW, we switch to SSL automatically during the checkout phase (when they click the "Check Out" button but before they start keying in their information). If the user wants to go back and change the URL to be insecure, that is their problem, not mine.It would be nice in general to be able to retrieve the CGI environment variables from within WebDNA (that is what ASP's ServerVariables method is reporting).HTHJohn-- John PeacockDirector of Information Research and TechnologyRowman & Littlefield Publishing Group4501 Forbes BoulevardSuite HLanham, MD 20706301-459-3366 x.5010fax 301-429-5748-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list
.To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Morten Madsen wrote:> I want to make sure that the customers have a secure connection during> checkout. In ASP it is very easy to get information about which port the> client is using on the server (Request.ServerVariables("SERVER_PORT")),> PSEUDO: if the port = 80 redirect to HTTPS://rightside - if it is 443 do> nothing.One easy way to do it is to require SSL for a specific URL on the server (this is commonly available on all web servers I have experience with) and then place your checkout files in that directory only. Then you "know" that the only time someone can access that file is via SSL and you are safe.FWIW, we switch to SSL automatically during the checkout phase (when they click the "Check Out" button but before they start keying in their information). If the user wants to go back and change the URL to be insecure, that is their problem, not mine.It would be nice in general to be able to retrieve the CGI environment variables from within WebDNA (that is what ASP's ServerVariables method is reporting).HTHJohn-- John PeacockDirector of Information Research and TechnologyRowman & Littlefield Publishing Group4501 Forbes BoulevardSuite HLanham, MD 20706301-459-3366 x.5010fax 301-429-5748-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
John Peacock
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:
Help! WebCat2 bug (1997)
Product Name Fields and the Ampersand (1999)
WebCatalog 2.0 & WebDNA docs in HTML ... (1997)
[WebDNA] Search on a database (2012)
WebCatalog NT beta 18 now available (1997)
Summing fields (1997)
WebCat for Unix?? (1997)
Word wrapping (1997)
Variable prices and Formulas.db (1997)
Size limit for tmpl editor ? (1997)
[OT] On a side note.. (2003)
WC2b15 File Corruption (1997)
Questions To Answer (1997)
Monitoring Script (2008)
SIMS setup (1998)
Sku numbers (1997)
[WebDNA] WebDNA 8.6 Ubuntu 16.04 (2018)
Shipping Tables (1999)
[UPPERCASE] (1997)
problems with 2 tags (1997)