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:
Bug Report, maybe (1997)
[quantity] solved (1997)
Linux ODBC and the ODBC Bridge (2000)
MacAuthorize Directory (2000)
Configuring E-mail (1997)
Huge databases and RAM (1998)
Multiple Ad databases? (1997)
Order not created error (1997)
Caching [include] files ... (1997)
More to Expire (1998)
normal users.db calls ... (1998)
webcat (2000)
Trigger Validation Text Broken (2003)
relogin same user? (1998)
SKU lookup (1997)
Dummy Credit Card Number for debug? (1997)
Re1000001: Setting up shop (1997)
Execute Applescript (1997)
Search bug. Help (2002)
Cookie Newbie (2002)