[squid-users] URL length problem... what is the max url length?

G'day all,

hitting problems with a long URL through squid. Does anyone know what the
max URL length squid can handle is? Is there any way to change this?

Details of long URL below;

----- Forwarded message from abo -----

Date: Wed, 21 Aug 2002 15:08:47 +1000
To: Drew <drew@no6.com>
Subject: Re: [MLB-WIRELESS] URL length problem with nodemap.

On Tue, Aug 20, 2002 at 05:56:12PM -0700, Drew wrote:
> Donovan Baarda wrote:
[...]
> >The nodemap currently uses a reduced number of nodes in the nodemap for IE
> >because IE has known problems with long URLs. However, when using a less
> >braindead browser like Galeon, the full list of nodes is included in the
> >URL, resulting in a single URL nearly 8K long! This is so long I believe
> >even squid truncates it. The end result is only IE can see the nodemaps.
> >
> Actually, the url is truncated to 65 for IE, and 300 for everything
> else. 300 works fine with mozilla/netscape, so galeon being based on
> gecko not working is a bit odd. You mentioned that you're using Squid,
> could you perhaps test galeon on a box not using squid to see if the
> problem lies with squid or galeon?

I see the followinging in my /var/log/squid/cache.log;

2002/08/21 14:51:25| urlParse: URL too large (7932 bytes)

A cut and paste of the url into a text document from Galeon fed through wc
gives;

$ wc url2.txt
      1 2 7931 url2.txt

Note that the squid url length probably includes a terminating character or
something. Bypassing the proxy I keep getting timeout errors...

In anycase, the URL genuinely is greater than 300 characters... you didn't
mean 300 nodes did you? I'm taking about the map image url;
"http://life.csu.edu.au/cgi-bin/gis/MapGIF?..."

It seems that galleon can handle the long URL, given that it looks
well-formed to me when pasted into a text file, and the length complained
about by squid is the lenth of the url. I don't know if the server
at the other end can handle it though, and maybe that's causing the
timeouts.

In any case, squid certainly cant handle it, and I don't think
there are any options I can tweak to make it handle it. I think 8K is pretty
unreasonable myself... that's what POST requests are for :-). Perhaps
cutting it back to a max length of 2K would be reasonable?

-- 
----------------------------------------------------------------------
ABO: finger abo@minkirri.apana.org.au for more info, including pgp key
----------------------------------------------------------------------
----- End forwarded message -----
-- 
----------------------------------------------------------------------
ABO: finger abo@minkirri.apana.org.au for more info, including pgp key
----------------------------------------------------------------------