Re: Perl CGI Cookies "Content-Type:text/html" showing at top of html.

Here is where a client-side debugger such as FireBug is extremely useful. It really helps to “see for yourself,” byte for byte, what the client is actually receiving. Sometimes that is a lot more insightful than looking at the code and trying to figure out just what it is sending. Obviously, at some point the browser decided it wasn’t looking at HTML headers anymore, so LQQK at what it says it got.

Replies are listed 'Best First'.
Re^2: Perl CGI Cookies "Content-Type:text/html" showing at top of html. by Corion (Patriarch) on Aug 19, 2011 at 14:03 UTC
It is worth to note that Firefox does not show in its "View Source" part and in Firebug what it received, but what DOM it constructed from that. Especially if it is receiving "invalid" HTML (according to some standard or other), the DOM might or might not reflect the intention of what was sent.	[reply]
Re^3: Perl CGI Cookies "Content-Type:text/html" showing at top of html. by locked_user sundialsvc4 (Abbot) on Aug 19, 2011 at 22:07 UTC
No, I am specifically thinking of the “Net” displays of FireBug, which is of course the debugging plug-in for FireFox. Other browsers offer similar developer-oriented debugging features. I have more than one flat-spot on my head (“Doh!!”) from things that Firebug has told me about what an application was actually sending. These sorts of problems are usually fairly effortless to resolve once you can see them, but, “aye, there’s the rub.”