Re: browser info.txt and SSL

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 14975
interpreted = N
texte = 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.ThanksSandy Grant Hulbert wrote: > > >But once I am in the SSL area (https), the [issecureclient] no longer > >works. It does not recognize my browser type and [issecureclient] > >always returns false. the [BROWSERNAME] works fine in non-SSL, but > >stops working in SSL. > > Try looking at [browsername] to see if it's different when you hit the server with SSL vs. non-SSL. That may give a clue as to how to modify Browser Info.txt properly. > > Grant Hulbert, V.P. Engineering | ==== eCommerce for the Rest of Us ==== > Pacific Coast Software | WebCatalog, WebMerchant, > 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, > San Diego, CA 92128 | Typhoon > 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ 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)
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.ThanksSandy Grant Hulbert wrote: > > >But once I am in the SSL area (https), the [issecureclient] no longer > >works. It does not recognize my browser type and [issecureclient] > >always returns false. the [browsername] works fine in non-SSL, but > >stops working in SSL. > > Try looking at [browsername] to see if it's different when you hit the server with SSL vs. non-SSL. That may give a clue as to how to modify Browser Info.txt properly. > > Grant Hulbert, V.P. Engineering | ==== eCommerce for the Rest of Us ==== > Pacific Coast Software | WebCatalog, WebMerchant, > 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, > San Diego, CA 92128 | Typhoon > 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ 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:

Re[2]: Next X hits (1996) [SHOWIF AND/OR] (1997) Searching multiple Databases (1997) Help name our technology! (1997) [WebDNA] 8.6 Download links (2018) Orderfile Problem (2004) Showif, Hideif reverse logic ? (1997) Nested tags count question (1997) Getting the protocol (2004) [WriteFile] problems (1997) Server capacity (2003) Nested tags count question (1997) webmerch and serials - almost there (1997) XML Woes (2004) [WebDNA] two ideas for running a cluster of WebDNA servers (2019) includes and cart numbers (1997) Netscape 3.01 can't see db in form (was problems problemsproblems) (1997) SSL and reg web* (1997) WebCatalog2 Feature Feedback (1996) Providing hard copy of database to client (1997)