Re: Secure server question
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 11594
interpreted = N
texte = >First, do I have to run Configure WebStar again for SSL?Yes. WebSTAR SSL is a completely different program, so it needs its configuration set.>Second, what's the best way to set up the servers on one machine to work>best with WebCatalog?* Run both WebSTAR and WebSTAR-SSL in exactly the same folder, so you don't have to worry about URLs being different when you switch over to secure mode.* Use WebCatalog CGI, not plugin (until we get a workaround that solves the unsynchronized database problem).* Keep WebSTAR-SSL in the background so your non-SSL version runs fastest* Keep users on the non-SSL for as long as possible for speed reasons. That means don't ask sensitive information (credit card numbers) until the very last.* Use http[SecureBrowser]s[/SecureBrowser]://xxx/xxx on your credit card info page so that visitors get switched over to https: only if their browser supports it.* On the final ThankYou page, put a link that leads back to http: (non-secure) so visitors don't continue to browse your site in slow SSL mode.I hope this helps.Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors =====Pacific Coast Software | WebCatalog Pro, WebCommerce Solution11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMasterSan Diego, CA 92128 | SiteGuard619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com
Associated Messages, from the most recent to the oldest:
>First, do I have to run Configure WebStar again for SSL?Yes. WebSTAR SSL is a completely different program, so it needs its configuration set.>Second, what's the best way to set up the servers on one machine to work>best with WebCatalog?* Run both WebSTAR and WebSTAR-SSL in exactly the same folder, so you don't have to worry about URLs being different when you switch over to secure mode.* Use WebCatalog CGI, not plugin (until we get a workaround that solves the unsynchronized database problem).* Keep WebSTAR-SSL in the background so your non-SSL version runs fastest* Keep users on the non-SSL for as long as possible for speed reasons. That means don't ask sensitive information (credit card numbers) until the very last.* Use http[SecureBrowser]s[/SecureBrowser]://xxx/xxx on your credit card info page so that visitors get switched over to https: only if their browser supports it.* On the final ThankYou page, put a link that leads back to http: (non-secure) so visitors don't continue to browse your site in slow SSL mode.I hope this helps.Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors =====Pacific Coast Software | WebCatalog Pro, WebCommerce Solution11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMasterSan Diego, CA 92128 | SiteGuard619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com
Grant Hulbert
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:
Orderfile context problem (1998)
FORMS: Returning a specific page (1997)
Nav. 4 probs with cart (1997)
RE: Adding headers to email (1997)
2 databases (1997)
Protect and Serve (1999)
Automatic thumbnail images (1998)
[WebDNA] An actual attempt to get WebDNA and MAMP Pro to work - (2018)
Searching for words equal to A or equal to B (1999)
Accepting credit cards (1997)
I give up!! (1997)
Sorting Various Sizes (2003)
IE, Layers, and Select (2002)
2.1 Stuff (1998)
about this server and links to who (1997)
webcat license???? (1997)
Sorting LISTFILES (1997)
RePost: NAT and the CART (1999)
code to phantom spacing (2001)
[WebDNA] What is the diff. btwn. Commerce & Enterprise edition? (2008)