Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am using Wireshark to view my HTTP activity. When there is a 404 Not Found error returned, I can't find an easy way to determine what request could not found. Can anyone explain how to do this?

share|improve this question
up vote 2 down vote accepted

If you're using a windows system, try Fiddler. I love WS, but Fiddler tends to be more helpful for me in these scenarios.

share|improve this answer
+1 If you're debugging HTTP(S) traffic, Fiddler makes it a lot easier. Wireshark is meant for the more general packet analysis, it won't show the data as structured as Fiddler can. – Tom Wijsman Aug 9 '10 at 0:40

If you're interested in only traffic to a specific webserver:port combination, wireshark may be useful. But so many websites have traffic coming from more than one server (bugs, central javascript libraries, ad libraries, server farms, etc) that your Wireshark capture rules will get unwieldy.

I'd recommend using a proxy (such as Fiddler as @Taylor suggested). If you are using Firefox (or are willing to use it for this debugging) you can also add Live HTTP Headers.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .