Everything went well for requests I had made using IE. Burp captured all requests and responses that were sent. Then I noticed another request/response that I didn't trigger through IE:
GET /msdownload/update/v3/static/trustedr/en/authrootseq.txt HTTP/1.1 Accept: */* User-Agent: Microsoft-CryptoAPI/5.131.2600.5512 Host: www.download.windowsupdate.com Proxy-Connection: Keep-Alive Cache-Control: no-cache Pragma: no-cache HTTP/1.1 200 OK Content-Length: 18 Content-Type: text/plain Accept-Ranges: bytes ETag: "0e4bf26aecac91:803b" Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Age: 9261 Date: Mon, 17 Aug 2009 13:00:35 GMT Last-Modified: Fri, 01 May 2009 22:42:48 GMT Connection: keep-alive 1401C9CAAE2685483A
I did notice, however, that all requests/responses sent through Google Chrome also get captured by the local proxy I had setup for IE with Burp. Not only do all Chrome requests get captured, but so do all http requests sent by all Visual Studio Express products (probably Visual Studio as well). I'm sure there are tons of other requests as well that would be captured by doing this.
No comments:
Post a Comment