Sign up ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Is it possible to configure firefox and IE9 to display the raw HTTP error pages sent from a server instead of the user friendly one they now use (pic below)

enter image description here

This would save me having to go to my server logs all the time for the specific codes etc.

I preferred the olden' days of doing it (pic below)

enter image description here


share|improve this question
Please see the answer below for tools suggestion although I need to clarify that you are misinterpreting errors in your question. First is the result of lack of response from the server which means your computer did not established connection - for example due to closed port. The second one is the result of missing file and it a valid response from server sent after connection on specific port was established successfully. – mnmnc Jan 10 '13 at 13:30

2 Answers 2

up vote 2 down vote accepted

Within Firefox use LiveHttp headers pluggin to view the Http Headers responses from server. You will see the Status Code like HTTP/1.1 404 FILE NOT FOUND in there.

It will look like this: enter image description here

I don't think there is a pluggin for IE but you could use Fiddler to analyse the web Traffic - it will show you in details all packets including Headers.

Here is how Fiddler looks: enter image description here

To summarize: Browsers are created to interpret the Hyper Text not display all the content of the packets - this is the job for sniffers/debuggers. You can use mentioned above tools in Windows or tcpdump on Linux. As a side note - you could see Headers in Wireshark on Windows as well but this is overkill since you will see more then the network layer you need. You need only Application Layer and you would see That plus Network and Data Link layer in there as well.

share|improve this answer
Thanks for this. I decided to use Firebug – kaleeway Jan 10 '13 at 13:38

These are actually two different error conditions. The first one means there was never a true HTTP/HTTPS session established. The second means the server is there and responding, it just doesn't have what you want. The first is analogous to "The store is supposed to be at the corner of Columbus and First, but there's nothing here but an empty lot!" while the second is analogous to "Target didn't have any Zabbrox Bleach, we'll have to find another type of bleach."

share|improve this answer
This does not answer the question! – kaleeway Jan 10 '13 at 13:37
That's because the question cannot be answered the way it was asked - the question as asked relies on a false premise, namely that the first error message is coming from the server you're trying to reach. – John Jan 10 '13 at 14:18

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.