Re: encrypted query string trouble on OSX

This WebDNA talk-list message is from

2001


It keeps the original formatting.
numero = 37717
interpreted = N
texte = On 8/8/01 11:19 PM, Jon Robinson wrote:>> I think sooner or later you will run into problems with this. > > I'd be very interested in what you see as problematic, as indeed we *are* > running into problems but don't know why!Browser change. Netscape just released 6.1 and I heard they changed a lot.> >> Can you store the values in a temp.db file or cookies. > > Cookies are probably out due to security issues.? What security concerns? The customers? > A temp db may offer a solution, but there are a few issues that may limit > that as well.I have successfully used temp dbs where long URL's cause hickups in the browser. Plus with a temp db you only need to pass one value (cart, maybe) trough a URL and do a search on top of each page and evaluate from there. No need to pass encrypted values in a URL. >> Some browsers joke on this long URL. > > Both browsers seem to be fine hitting the Win98 version but not the MacOSX > version, so I don't think it's a browser issue.In my internal testing, IE on Win always behaved ok, but then taking it to a real server and hitting Netscape and IE (both platforms) always seemed to cause troubles. I think there is a limit of how much data you can pass in a URL.I can vaguely remember that there was some posts in the past about encrypted values in a url. Did you try to search the archives?Sincerely, Nitai Aventaggiato -- We make tools to energize your business Content Management & eBusiness SystemsComputerOil GmbH http://computeroil.com/ Hauptstrasse 12 info@computeroil.com 8252 Schlatt/Switzerland Tel: +41 (0)52 654 15 55 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: encrypted query string trouble on OSX (Kenneth Grome 2001)
  2. Re: encrypted query string trouble on OSX (Stuart Tremain 2001)
  3. Re: encrypted query string trouble on OSX (John Peacock 2001)
  4. Re: encrypted query string trouble on OSX (Stuart Tremain 2001)
  5. Re: encrypted query string trouble on OSX (Jon Robinson 2001)
  6. Re: encrypted query string trouble on OSX (John Peacock 2001)
  7. Re: encrypted query string trouble on OSX (Jon Robinson 2001)
  8. Re: encrypted query string trouble on OSX (Nitai @ ComputerOil 2001)
  9. Re: encrypted query string trouble on OSX (Jon Robinson 2001)
  10. Re: encrypted query string trouble on OSX (John Peacock 2001)
  11. Re: encrypted query string trouble on OSX (Jon Robinson 2001)
  12. Re: encrypted query string trouble on OSX (Nitai @ ComputerOil 2001)
  13. encrypted query string trouble on OSX (Jon Robinson 2001)
On 8/8/01 11:19 PM, Jon Robinson wrote:>> I think sooner or later you will run into problems with this. > > I'd be very interested in what you see as problematic, as indeed we *are* > running into problems but don't know why!Browser change. Netscape just released 6.1 and I heard they changed a lot.> >> Can you store the values in a temp.db file or cookies. > > Cookies are probably out due to security issues.? What security concerns? The customers? > A temp db may offer a solution, but there are a few issues that may limit > that as well.I have successfully used temp dbs where long URL's cause hickups in the browser. Plus with a temp db you only need to pass one value (cart, maybe) trough a URL and do a search on top of each page and evaluate from there. No need to pass encrypted values in a URL. >> Some browsers joke on this long URL. > > Both browsers seem to be fine hitting the Win98 version but not the MacOSX > version, so I don't think it's a browser issue.In my internal testing, IE on Win always behaved ok, but then taking it to a real server and hitting Netscape and IE (both platforms) always seemed to cause troubles. I think there is a limit of how much data you can pass in a URL.I can vaguely remember that there was some posts in the past about encrypted values in a url. Did you try to search the archives?Sincerely, Nitai Aventaggiato -- We make tools to energize your business Content Management & eBusiness SystemsComputerOil GmbH http://computeroil.com/ Hauptstrasse 12 info@computeroil.com 8252 Schlatt/Switzerland Tel: +41 (0)52 654 15 55 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Nitai @ ComputerOil

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:

Grep Question - MAY NEVER BE SOLVED (2003) Migrating to NT -Reply (1997) searching multiple databases (1997) Rhapsody? (1997) shipcost (1997) OT: Apache's mod_rewrite (2005) WebCat2_Mac RETURNs in .db (1997) A quickie question (1997) 2.0 Info (1997) Quickie question on the email templates (1997) Separate SSL Server (1997) Tracking inbound links for discounts (1997) Nested Loops and SHOWIFs (1997) I'm tired of all this! (2000) Constructive criticism (2000) Restart of DBserver (1997) # fields limited? (1997) Help with Repost Data msg from form (1997) [WebDNA] Problem with SendMail - seems succesfull but nothing to recieve (2016) SiteGuard Use Question (1997)