This is our old Q&A Site. Please post any new questions and answers at

I've noticed that Wireshark isn't able to capture certain browser GET requests. For example, TamperData (Firefox addon) shows a GET request for a URL. In Wireshark that URL is not seen as an HTTP.REQUEST.URI, rather it is found as an XML.ATTRIBUTE. I'm wondering where I am having the disconnect understanding this.


Update: NGREP is able to capture the HTTP GET request.

Edit: There were some odd dynamic caching that was occurring. It wasn't showing because it had been cached.

Though this problem is solved, there's still another one that I've run into. If the traffic is SSL, Wireshark won't be able to see it, but TamperData will, since it is getting the request before it is encrypted and sent off.

asked 11 Jan '13, 21:35

naisanza's gravatar image

accept rate: 0%

edited 11 Jan '13, 22:12

Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 11 Jan '13, 21:35

question was seen: 4,000 times

last updated: 11 Jan '13, 22:12

p​o​w​e​r​e​d by O​S​Q​A