Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I'm running Windows Vista home premium. I want to see all outgoing HTTP requests from my PC along with the URL. Is there any free tool for this?

share|improve this question

migrated from serverfault.com Nov 14 '11 at 2:33

This question came from our site for professional system and network administrators.

    
The first answer below from @Mikey is correct, if your need for "http requests" is accurate. Do you want to see the content of each request, or do you just want to monitor web usage? –  Paul Nov 14 '11 at 7:36
    
Request URL is enough but response content is better to have. –  Moe Sweet Nov 14 '11 at 7:41
1  
Cool, then the answer given is good to go. –  Paul Nov 14 '11 at 9:22

4 Answers 4

up vote 5 down vote accepted

You can use http://www.wireshark.org/

The user guide can be found at http://www.wireshark.org/docs/wsug_html/

To filter http traffic specifically you can refer to; http://serverfault.com/questions/96272/how-to-filter-http-traffic-in-wireshark

share|improve this answer
    
wireshark is the absolute best for monitoring –  Fergus Nov 14 '11 at 21:30

You could use the command prompt by typing the command netstat /f. This will show you a list of the connections to your local interface. The /f tells the command to resolve the external ip addresses as well.

share|improve this answer
    
This shows you active connections, not http requests –  Sinaesthetic Oct 30 '13 at 3:37

Fiddler is specialized in HTTP(S) packet monitoring, manipluation and generation, so it provides such features as requested in the question in an easier way. However, Wireshark is much more comprehensive in terms of network protocol monitoring and analysis.

share|improve this answer

There is a detailed article on this topic at Hubpages. It describes a solution to easily log and filter HTTP requests made in a home LAN based on Wireshark and some supplemental free software.

In a nutshell, the article deals with the problem of memory overgrowth that prevents using Wireshark for continuous HTTP requests monitoring. To address the issue, the author suggests using tshark.exe (the commandline version of Wireshark) periodically killing and restarting it with System Scheduler and a batch file like this:

    FOR /F "usebackq tokens=2" %%i IN (`tasklist ^| findstr /r /b "tshark.exe"`) DO start /MIN sendsignal.exe %%i
    ping 127.0.0.1 -n 7 -w 1000
    tshark -2 -l -t ad -R "http.request.method == GET" -N nC -i 2 | ts_rdln.exe

where sendsignal.exe is a utility to send Ctrl+C to a program; ts_rdln.exe is a simple tshark log parser/filterer; ping command is used to introduce a delay; and the i argument of the last line is the number of your NIC looking out into the Internet.

share|improve this answer
    
When linking to a site it is best to summarise the information on the page. Otherwise if the link goes down your answer is useless. –  Joe Taylor Oct 7 '13 at 8:42

Your Answer

 
discard

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.