Feature request: Display available network request details before response is received

I believe I have an idea on how to make web developers’ life easier.

One of the features I’m missing in Firefox is the following:

When request is sent to the server, the request record under “Network” tab has no details on URL, headers or any other data until the response is received.

The browser for sure knows which data is used to make the request. Thus, it would make sense to have that data available for inspection.

Lack of such data is especially frustrating when developing Web API or requests handlers, which do not work as expected. At that point, I wish there was easy and comfortable way of examining the request data before the response is received. Sometimes the response never comes, which makes the situation even worse.

Please, consider making request details available at the moment the request is sent as opposed to the moment the response received.

Steps to reproduce:

  • Create some dummy web project
  • Set a breakpoint at the request processing code before the response is sent to the requester
  • In Firefox open dev tools (F12)
  • Open Network tab
  • Send the request to the handler, which has breakpoint set
  • Under Network tab click on the request record

Expected result:

  • Request details has all the available data displayed (the data related to the request

Actual result:

  • There is no request data displayed

Thank you! We are tracking a related issue here: https://bugzilla.mozilla.org/show_bug.cgi?id=1556508 , which seems to cover your use case, right?


I’ve checked the other issue. No, this one is different from the one you’ve linked.

In current issue, there is no request data available until response is received from the server. In the linked issue, the complaint is regarding video stop playing and a part of the browser hanging.

Please, consider examining current issue and providing an update to the browser. I believe it will be very beneficial for development experience.

Right, this bug got a bit muddled. The bug I duped it for looks like the right one though: https://bugzilla.mozilla.org/show_bug.cgi?id=1557795


Yes, 1557795 is the same issue as the current one.