[squid-users] Content lengh being added to if-modified-since http header?

From: Richard Fuser <m3@dont-contact.us>
Date: Thu, 3 Jul 2003 19:20:50 +1000

Hi Everyone,

Have a problem with a java menu app when going via squid and have been
looking at http headers being passed back and forth and I have seen the
following:

When using our squid proxy server (2.5STABLE3) the header lines for
if-modified-since have a length tagged onto the end.

818 GET
http://server.internal.domain.com/servlet/eyconnindex?readviewentries&expandview&restricttocategory=100%7EBenefits&count=1500

Header Contents
If-Modified-Since: Wed, 02 Jul 2003 04:29:55 GMT; length=3807

the end of this last line shows a ;length=3807 which must have been
added by squid becasue the following lines are when the connection is
made direct:

302 GET
/servlet/eyconnindex?readviewentries&expandview&restricttocategory=110%7EDirectories&count=1500
HTTP/1.1
Header Contents
If-Modified-Since: Wed, 02 Jul 2003 19:20:58 GMT

I also noticed that for some reason when squid fetches makes the GET
request its making it to the FQDN

The servlet is trying to convert: If-Modified-Since: Wed, 02 Jul 2003
04:29:55 GMT; length=3807, to a java date.

When the length is tagged afterwards we get a internal server error
presumably becasue the length=3807 is being included ?

Im trying to figure out:

1: Why is squid doing this ?

2: Is squid doing the wrong thing or is the app doing the wrong thing?

3: How could it be fixed

If anyone has any clues it would be appreciated, break out the RFC's if
need be! :)

-- 
Regards,
Richard Fuser
Received on Thu Jul 03 2003 - 03:21:04 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:17:49 MST