[squid-users] URL encoded data

 I am not sure if this is squid related, or Netscape related, but I
tend to think it is squid:

SQUID 2.3 STABLE4.
Netscape 4.75 or 3.0 as client.

Here's the situation :

URL that works :

http://www.mysite.com/cgi/myscript?value='somevalue%20somevalue'&value2=somevalue

This works always, as it is a URL encoded string, with blank converted
to %20.
However :
http://www.mysite.com/cgi/myscript?value='somevalue
somevalue'&value2=somevalue

Notice the blank.
If NO proxy is configured, Netscape will consider the URL as
http://www.mysite.com/cgi/myscript?value='somevalue
which is wrong for the user wanting to retrieve the data, but correct
with respect to URL handling, the blank was not encoded as required.

If squid is the proxy used, the web server will get the following
request :
http://www.mysite.com/cgi/myscript?value='somevaluesomevalue'&value2=somevalue

Notice the blank has been removed.
Since all parameters are present, I tend to think Netscape sent it the
URL as it found it in the link definition (or location bar) directly to
the proxy, no modifications. Then squid, when forwarding the URL, cut
out the space character, thus joining the two words.
Because without proxy Netscape sends only a partial URL, I tend to
think it would have sent a partial URL to the proxy, too.

access.log for squid shows only the path, not the parameters, so I
don't know for sure.

Please tell me, is squid skipping that space character? If so, can
someone write a patch, please, for 2.3STABLE4 to correct URL encoding
when necessary?

Thank you.

=====
ing. Andrei Boros
Centrul pt. Tehnologia Informatiei
Societatea Romana de Radiodifuziune

__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions!
http://auctions.yahoo.com
Received on Mon Jan 28 2002 - 02:37:20 MST