RE: [squid-users] 2 Content-Length headers

From: Elsen Marc <elsen@dont-contact.us>
Date: Thu, 31 Mar 2005 11:02:28 +0200

 
> dear all,
>
> similiar to below problems, I have access.log came-up with this :
>
> 2005/03/31 15:22:43| ctx: enter level 0:
> 'http://www.conflictanddevelopment.org/Home.php'
> 2005/03/31 15:22:43| WARNING: found whitespace in HTTP header
> {File 'c}
>
> on browser came-up this one:
>
> GET /Home.php HTTP/1.0
> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
> application/x-shockwave-flash, */*
> Accept-Language: en-us
> Pragma: no-cache
> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
> Host: www.conflictanddevelopment.org
> Proxy-Connection: Keep-Alive
>
> I believed that this is some malprogramed flash or something.
> If I bypass the squid cache....it went thru normally.
> Squid 2.5STABLE9 has new tag to handle this one ? I'm still
> using stable7-20050405
>
> thank you in advance.
>

 Again this remote webserver is or has gone totally bananas :
 
 % wget -s > http://www.conflictanddevelopment.org/Home.php

HTTP/1.1 200 OK
Content-Type: text/html
Server: Microsoft-IIS/6.0
^GFile 'c: \mysql\share\charsets\?.conf' not found (Errcode: 2)
^GCharacter set '#33' is not a compiled character set and is not specified in the 'c: \mysql\share\charsets\Index' file
X-Powered-By: PHP/4.3.6
Set-Cookie: PHPSESSID=b0529900444ca49650a1838b57af288a; path=/
Set-Cookie: server=1
MicrosoftOfficeWebServer: 5.0_Pub
Date: Thu, 31 Mar 2005 08:54:35 GMT
Connection: close

<html>^M
<!-- InstanceBegin template="/Templates/master.dwt" codeOutsideHTMLIsLocked="false" -->^M

 The webserver includes garbage in the response headers :

^GFile 'c: \mysql\share\charsets\?.conf' not found (Errcode: 2)
^GCharacter set '#33' is not a compiled character set and is not specified in the 'c: \mysql\share\charsets\Index' file

 As far as bypassing the cache makes the site work; it's simple
 luck thet the browser is more interested in html, and doesn't have
 to be that fierce as caches will have to do.
 They have or must have more interest in the response headers to make
 proper decisions on caching etc.

 The browser will just 'wait for the html'.

 But that webserver is seriously ill....
  
 M.
Received on Thu Mar 31 2005 - 02:05:36 MST

This archive was generated by hypermail pre-2.1.9 : Fri Apr 01 2005 - 12:00:03 MST