Reply to thread

Message

<blockquote data-quote="Psionicist" data-source="post: 2628112" data-attributes="member: 1874">This is an odd problem; based on your screenshot it appears Firefox printed the complete server response.When you visit a website, the web browser sends a request to the server, such as &quot;Please send me the page index.php, the forum front page!&quot;. As you probably know, a web page is made up of HTML. Complex (heck, all modern) web pages consists not only of HTML however but of several images too. To grab the image the web browser have to ask the server again, &quot;Please send me the image logo.gif, the enworld logotype!&quot;. This is repeated for all images not cached until the web browser can paint the webpage on screen as intended.Because computers are dumb and usually have problems to make their own decisions web servers always send some additional information with the HTML and images. This information can be how large the image is, or if the contents of a response is a jpg-image or html-page (so the web browser knows what to do with the file sent), or what the web browser should save in a cookie. This extra information is sent first (so we will call it the &quot;header&quot;), then the actual contents. This is what you are seeing. The annoying part is of course this information shouldn't be printed in the browser at all. It appears the web server software sends headers twice sometimes, for reasons unknown. This would explain why the info is printed at all.</blockquote>

[QUOTE="Psionicist, post: 2628112, member: 1874"] This is an odd problem; based on your screenshot it appears Firefox printed the complete server response. When you visit a website, the web browser sends a request to the server, such as "Please send me the page index.php, the forum front page!". As you probably know, a web page is made up of HTML. Complex (heck, all modern) web pages consists not only of HTML however but of several images too. To grab the image the web browser have to ask the server again, "Please send me the image logo.gif, the enworld logotype!". This is repeated for all images not cached until the web browser can paint the webpage on screen as intended. Because computers are dumb and usually have problems to make their own decisions web servers always send some additional information with the HTML and images. This information can be how large the image is, or if the contents of a response is a jpg-image or html-page (so the web browser knows what to do with the file sent), or what the web browser should save in a cookie. This extra information is sent first (so we will call it the "header"), then the actual contents. This is what you are seeing. The annoying part is of course this information shouldn't be printed in the browser at all. It appears the web server software sends headers twice sometimes, for reasons unknown. This would explain why the info is printed at all. [/QUOTE]

Verification