Our organization is running squid 2.5.9-10.
We're having a problem sending a request to tomcat through squid that
has a 4,377 chars or more URI. (it's a very long GET request).
If the GET URI is only 3,734 characters long then the request is
properly passed to Tomcat and Tomcat correctly sends the response. If
we send a larger 4,377 character request directly to tomcat via 8080 it
responds correctly.
But when send to port 80 through squid I get the following squid's
access.log:
1210964572.259 1 10.100.0.2 TCP_DENIED/400 5704 GET
(cutting out long request here, I can show if you want) - NONE/-
text/html
We tried to edit the squid.conf to request_body_max_size 8192 KB
(in order to get the request past tomcat I had changed tomcat's
maxHttpHeaderSize = "8192")
After trying this change in the squid.conf file the error message was
the same.
Then we also examined squid's request_header_max_size which was set to
the default of 0 meaning no limit.
Since it is a GET request we assume there's no body.
Headers are not large.
There is no ACL in place.
Why does a very long URI not work, is there a configuration option to
affect this?
Received on Fri May 16 2008 - 19:14:06 MDT
This archive was generated by hypermail 2.2.0 : Tue Aug 05 2008 - 01:05:13 MDT