Re: browser info.txt and SSL

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 14979
interpreted = N
texte = Grant Hulbert wrote: > > >The [browsername] comes up empty when it is in SSL but is Mozilla/3. > >when in non-SSL. Why would the SSL not recognize the browser type when > >non-SSL does? Does it need its own table of browser types, or perhaps > >be more confused by path (inside the Webcatalog folder inside the > >Webstar folder). The servers are both inside the same WebStar folder. > > Wow. Sounds like a bug in Netscape, where it doesn't transmit its name over SSL. Very strange. I've never bumped into this because we always put the SSL check onto a page that is hit via non-SSL -- then we lead the user to an SSL page and never check from there on. > I'm curious to hear how most web stores handle this. Do you give any sorts of warning to shoppers with non secure browsers? Do you lead them down a different path, offer faxing etc.Discover card won't even let us take an order on Discover card unless the browser is secure, so we do need an order info. page that is sensistive to whether or not the customer has a secure browser.I'm guessing the best thing to do is to have two order information pages, one for SSL and one for non-SSL customers.ThanksSandy Associated Messages, from the most recent to the oldest:

    
  1. Re: browser info.txt and SSL (Grant Hulbert 1997)
  2. Re: browser info.txt and SSL (Sandra L. Pitner 1997)
  3. Re: browser info.txt and SSL (Sandra L. Pitner 1997)
  4. Re: browser info.txt and SSL (Grant Hulbert 1997)
  5. Re: browser info.txt and SSL (Grant Hulbert 1997)
  6. browser info.txt and SSL (Sandra L. Pitner 1997)
Grant Hulbert wrote: > > >The [browsername] comes up empty when it is in SSL but is Mozilla/3. > >when in non-SSL. Why would the SSL not recognize the browser type when > >non-SSL does? Does it need its own table of browser types, or perhaps > >be more confused by path (inside the Webcatalog folder inside the > >Webstar folder). The servers are both inside the same WebStar folder. > > Wow. Sounds like a bug in Netscape, where it doesn't transmit its name over SSL. Very strange. I've never bumped into this because we always put the SSL check onto a page that is hit via non-SSL -- then we lead the user to an SSL page and never check from there on. > I'm curious to hear how most web stores handle this. Do you give any sorts of warning to shoppers with non secure browsers? Do you lead them down a different path, offer faxing etc.Discover card won't even let us take an order on Discover card unless the browser is secure, so we do need an order info. page that is sensistive to whether or not the customer has a secure browser.I'm guessing the best thing to do is to have two order information pages, one for SSL and one for non-SSL customers.ThanksSandy Sandra L. Pitner

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:

access denied problem (1997) Why are some admin pages not encrypted? (2000) Protect Tag and Groups (1998) Still More on EudoraPro Email (1998) How To question on setting up downloads (1997) [WebDNA] WebDNA app (2013) A Global Variable (1997) Add message to Order (1997) can WC render sites out? (1997) Secure server question (1997) Email (1998) [WebDNA] Linix v 6.2 Server (2013) Reversing [ipaddress] normalization (1998) [subtotal] problems -- help? (1998) unusual search problem (1998) showcart (2000) Nested Loops and SHOWIFs (1997) Replace context problem ... (1997) Protecting Images (2003) WebCat2b13MacPlugin - [math][date][/math] problem (1997)