http - What is a networking monitoring tool/plugin that can provide detailed information on requests in Chrome

08
2014-07
  • Berlin Brown

    I use a tool called tamperdata in Firefox that provides a decent listing of the request information. I think it does a better job filtering out the content and also provides a way to tamper the request. For example, tamperdata lists the cookies and posts per request. The other tools in firefox and chrome don't do that. Is there a chrome tool like tamperdata that does a good job at detailing request information? I am mainly looking for a tool in chrome that does this?

    • Answers
  • mtak

    If you activate the Google Developer Tools from Extra->Developer Tools (CTRL+SHIFT+I) there is a 'Network' tab. This tab if you click on a resource on the page, it will give you the request and response HTTP headers:

    enter image description here


    • Related Question

    Is it possible to change Chrome's view-source behaviour to use the current request instead of starting a new one?
  • Aron Rotteveel

    I like Firefox's behaviour of loading the source from the currently loaded webpage. Chrome, instead, starts a new request. This makes it especially hard to view source of POST-requests, for example, since every view-source request utilizes GET.

    Is there a way to change the way Google Chrome's view-source works, so that it does not initialize a new request?

    EDIT, little bit of clarification regarding the way Firefox works:

    Firefox does not initiate a new request when viewing the source. It does only after refreshing the page while viewing the source. It then respects the GET/POST of the request as well. When viewing the source of a page that is already loaded, it does not seem to initiate a new request.


    • Related Answers
  • Sathya

    Is there a way to change the way Google Chrome's view-source works, so that it does not initialize a new request?

    No, this is the way Chrome works by design.

    When you "view source", you're really opening a new tab that opens the page again and displays the source rather than renders the page. Many web pages are dynamic and modify their HTML content (eg. using JavaScript/XMLHttpRequest) so we cannot display the current HTML - this is why a new request is made.

    If you want to view the current state of a dynamic page, you should use the inspector. "File icon -> Developer -> JavaScript console"

    I don't see how this is a security bug or a bug at all - the behavior is by design - closing as such.

  • SamB

    I don't think you can change the behavior of view-source: URLs, or the View page source command, you can get to the source as received for this page: first, open the Developer tools (WebKit's "Web Inspector"), found at Wrench > Tools > Developer tools. Now click on Resources and (if necessary) scroll down the list on the left until you find the resource of interest. And there you go: the source as it was transmitted in the original HTTP response.