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:
Release Date? (2002)
trouble updating records in database (1998)
Playin Tricks (2006)
RE: How much ram??? (1997)
Which GUI HTML editors work with WC ? (1997)
WCS Newbie question (1997)
WebCat2 Append problem (B14Macacgi) (1997)
AccountAuthorizer doing something useful (2002)
Emailer (1997)
Timeout question .. (2003)
[WebDNA] FCKeditor (2009)
Emailer help....! (1997)
Adding content advice needed (1998)
Multiple catalog databases and showcart (1997)
problems with 2 tags (1997)
Speeding up my [showif] performance (1999)
syntax question, not in online refernce (1997)
Nested vs conditional (1997)
[WebDNA] Useful (to me) [function]s (2013)
Merging databases (1997)