[Webkit-unassigned] [Bug 13710] HTTP headers being displayed in page body

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon May 14 09:39:39 PDT 2007


http://bugs.webkit.org/show_bug.cgi?id=13710


bdash at webkit.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bdash at webkit.org




------- Comment #6 from bdash at webkit.org  2007-05-14 09:39 PDT -------
Based on the packet trace it appears something is sending buggy HTTP responses.
 There are two responses in which the Content-Length mentioned in the header
does not match the apparent length of the data:

('192.168.0.13', '192.168.0.52', 3128, 55552)
HTTP/1.0 200 OK
Server: Mathopd/1.5p5
Date: Mon, 14 May 2007 14:00:31 GMT
Content-Type: text/css
Content-Length: 28623
Last-Modified: Wed, 04 Apr 2007 08:05:32 GMT
X-Cache: MISS from localhost.localdomain
X-Cache-Lookup: HIT from localhost.localdomain:3128
Proxy-Connection: keep-alive

Content-Length header says:  28623
Next response start appears to be at:  23102

and

('192.168.0.13', '192.168.0.52', 3128, 55557)
HTTP/1.0 200 OK
Server: DCLK-AdSvr
Content-Type: text/html
Content-Length: 3939
Set-Cookie: test_cookie=CheckForPermission; path=/; domain=.doubleclick.net;
expires=Mon, 14 May 2007 14:15:27 GMT
P3P: CP="CURa ADMa DEVa PSAo PSDo OUR BUS UNI PUR INT DEM STA PRE COM NAV OTC
NOI DSP COR"
Cache-Control: no-cache
Pragma: no-cache
X-Cache: MISS from localhost.localdomain
X-Cache-Lookup: MISS from localhost.localdomain:3128
Proxy-Connection: keep-alive

Content-Length header says:  3939
Next response start appears to be at:  3940



In the case of the former it looks as though the upstream proxy server starts
sending packets from an entirely *different* TCP connection to this port.  I
can't think of any reasonable explanation for the mixed up packets, but it's
very probable that they are the cause of the headers appearing on the page. 
Squid or any network device along the trip could be to blame.


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list