If you want to fix it then fix the web server to conform with HTTP
specifications. (see RFC2616 section 4.3, last paragraph).
If you want to work around it (i.e. you do not have control of the web
server) then try disabling server side persistent connections in
squid.conf.
-- Henrik Nordstrom Squid Hacker Marc Hansen wrote: > > Tanks! > Should I change it in Squid or on the Webserver? > > Marc > > On 12-Jun-2001 Henrik Nordstrom wrote: > > Looks like WebSitePro/2.0.36e is generating bad 304 replies (304 replies > > should not contain a message body) > > > > You can probably work around this by disabling server side persistent > > connections. > > > > -- > > Henrik Nordstrom > > Squid Hacker > > > > > > > > > > Marc Hansen wrote: > >> > >> Hi, > >> I'm using Squid 2.4Stable1 on Linux and get sometimes errormessages I > >> don't understand, that there are on that place. > >> Squid run in the ACCL-Mode and give this errormessage from the Webserver > >> to the Client. > >> This message is ok for me, but it should not be send to the client. The > >> proxy should then give the side out of it's cache to the client. > >> > >> Marc > >> > >> 304 Not modified > >> > >> The document has not been modified, you can use your local copy. > >> HTTP/1.0 200 OK Date: Tue, 12 Jun 2001 14:59:30 GMT Server: > >> WebSitePro/2.0.36e Accept-Ranges: bytes > >> Content-Type: text/html Page-Completion-Status: Normal > >> Page-Completion-Status: Normal X-Cache: MISS from ... close. > > -- > E-Mail: Marc Hansen <marc.hansen@tg.fh-giessen.de> > Date: 13-Jun-2001 > Time: 09:05:59 > > Marc Hansen, Giessen > ----------------------------------Received on Wed Jun 13 2001 - 02:14:51 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:00:44 MST