Re: name-value pairs

This WebDNA talk-list message is from

2006


It keeps the original formatting.
numero = 68038
interpreted = N
texte = URL encoding is probably the issue. You'd notice how cumbersome an URL with 2048 characters was. You're probably hitting a name-value pair where the value has a space or ampersand character, which is truncating your URL. On Oct 17, 2006, at 11:30 AM, Marc Thompson wrote: > RFC 2068 states: > > Servers should be cautious about depending on URI lengths > above 255 bytes, because some older client or proxy implementations > may not properly support these lengths. > > The spec for URL length does not dictate a minimum or maximum URL > length, but implementation varies by browser. On Windows: Opera > supports ~4050 characters, IE 4.0+ supports exactly 2083 > characters, Netscape 3 -> 4.78 support up to 8192 characters before > causing errors on shut-down, and Netscape 6 supports ~2000 before > causing errors on start-up. > > As John states, switch to POST to bypass the GET limits. > Also, remember the values are URL encoded... > > Marc > > Jyoti Behrani wrote: > >> Hi, >> I am trying to capture the name/value pair from the url returned >> by my processing process, but for some reason I can only capture >> first few of the name/value pair. The rest of the name/value pair >> have null values. >> I was wondering is there any limit on how many variables or >> characters you can pass through url ? >> I can capture all the variables using a jsp but not within a .tpl >> file. Any clues on how/why this is happening. >> Thank you for your anticipation. >> --Jyoti >> ------------------------------------------------------------- >> 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 > digest@talk.smithmicro.com> >> Web Archive of this list is at: http://webdna.smithmicro.com/ > > -- > ------------------------------------------- > Marc Thompson > Software Engineer > Office of Information Technology > University of Utah > 801.585.9264 > marc.thompson@utah.edu > ------------------------------------------- > > ------------------------------------------------------------- > 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 digest@talk.smithmicro.com> > Web Archive of this list is at: http://webdna.smithmicro.com/ > ------------------------------------------------------------- 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://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: name-value pairs ( Pat McCormick 2006)
  2. Re: name-value pairs ( Marc Thompson 2006)
  3. Re: name-value pairs ( John Peacock 2006)
  4. Re: name-value pairs ( John Peacock 2006)
  5. Re: name-value pairs ( Marc Thompson 2006)
  6. name-value pairs ( "Jyoti Behrani" 2006)
URL encoding is probably the issue. You'd notice how cumbersome an URL with 2048 characters was. You're probably hitting a name-value pair where the value has a space or ampersand character, which is truncating your URL. On Oct 17, 2006, at 11:30 AM, Marc Thompson wrote: > RFC 2068 states: > > Servers should be cautious about depending on URI lengths > above 255 bytes, because some older client or proxy implementations > may not properly support these lengths. > > The spec for URL length does not dictate a minimum or maximum URL > length, but implementation varies by browser. On Windows: Opera > supports ~4050 characters, IE 4.0+ supports exactly 2083 > characters, Netscape 3 -> 4.78 support up to 8192 characters before > causing errors on shut-down, and Netscape 6 supports ~2000 before > causing errors on start-up. > > As John states, switch to POST to bypass the GET limits. > Also, remember the values are URL encoded... > > Marc > > Jyoti Behrani wrote: > >> Hi, >> I am trying to capture the name/value pair from the url returned >> by my processing process, but for some reason I can only capture >> first few of the name/value pair. The rest of the name/value pair >> have null values. >> I was wondering is there any limit on how many variables or >> characters you can pass through url ? >> I can capture all the variables using a jsp but not within a .tpl >> file. Any clues on how/why this is happening. >> Thank you for your anticipation. >> --Jyoti >> ------------------------------------------------------------- >> 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 > digest@talk.smithmicro.com> >> Web Archive of this list is at: http://webdna.smithmicro.com/ > > -- > ------------------------------------------- > Marc Thompson > Software Engineer > Office of Information Technology > University of Utah > 801.585.9264 > marc.thompson@utah.edu > ------------------------------------------- > > ------------------------------------------------------------- > 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 digest@talk.smithmicro.com> > Web Archive of this list is at: http://webdna.smithmicro.com/ > ------------------------------------------------------------- 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://webdna.smithmicro.com/ Pat McCormick

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:

Username for Admin Group (1997) More on the email templates (1997) Comments in db? (1997) [WebDNA] Error: Can't open order file. Ignoring [OrderFile] context Error: (2011) WebCat2 - [SendNews] (1997) AND/OR searches in WebCat 3.07 (2003) Re[2]: 2nd WebCatalog2 Feature Request (1996) firewall ports for Mac OS X/WebCatalog (2001) SQL Error 22003 (2001) Malformed Pages (1999) [Way OT] Workstation Security (2002) [lineitems] (2000) Nested Lookups (1998) Plugin or CGI or both (1997) WebCatalog can't find database (1997) shaopping cart limits (2000) my price won't move (1997) Re:2nd WebCatalog2 Feature Request (1996) Order file numbers different than the cart number. why? (2000) Last Record not recognized? (1999)