Re: "WARNING: unparseable HTTP header field {: }"

tis 2006-03-28 klockan 17:11 -0500 skrev Steve Snyder:
> I assume that this website is screwed up, but, really, is this a valid
> reaction to bad HTML/JavaScript?

It's not bad HTML/JavaScript, it's bad HTTP protocol with junk in the
HTTP headers.

HTTP/1.1 200 OK
Server: Microsoft-IIS/5.0
Date: Wed, 29 Mar 2006 08:23:17 GMT
404;badcast.cfm:
:
:
:
:
Content-type: text/html
Page-Completion-Status: Normal
Page-Completion-Status: Normal
Set-Cookie: CFGLOBALS=HITCOUNT%3D1%23LASTVISIT%3D%7Bts+%272006%2D03%2D29
+00%3A23%3A18%27%7D%23TIMECREATED%3D%7Bts+%272006%2D03%2D29+00%3A23%
3A18%27%7D%23; expires=Sun, 27-Sep-2037 00:00:00 GMT; path=/;
Set-Cookie: CFID=41428110; expires=Sun, 27-Sep-2037 00:00:00 GMT;
path=/;
Set-Cookie: CFTOKEN=28311720; expires=Sun, 27-Sep-2037 00:00:00 GMT;
path=/;

The crap between the Date and Content-Type headers is what Squid is
upset about.

Regards
Henrik