I've been noticing this strange behavior when working with my web application. When I send a request and it takes a while to get a response, I want to check what I sent in the request body. However, I can't see any of the request headers or the body in the network tab of the browser's devtools until the response is either received or the request fails. Is this a common issue? I've used Firefox on MacOS, but I think I've seen this happen in other browsers too. I'd rather not have to log the details manually in the code. What's the reason for this behavior?
4 Answers
In Chrome, you can actually see the request headers while it's still pending, which is pretty helpful. It's odd that Firefox doesn't show this right away, likely because they want to streamline the logging process. A lot of developers find this behavior in Firefox frustrating, especially when debugging. You could use console logs or even the 'Edit and Resend' feature as a workaround.
I’ve noticed the same thing in Firefox—request headers and body only show up after the request resolves. It's a pain when you’re trying to debug slow requests. If you really want to get a better experience, switching to Chrome could help, as it displays those details upfront.
I totally get your frustration! I work with a Laravel app that sometimes runs as slow as molasses. It's super annoying not being able to see the request details until the server responds. But you might want to consider other tools, like Burp Suite, for a better view of what's happening with your requests.
On Chrome, you can check request headers and payloads immediately, unlike Firefox, which is just plain weird. Why not try Chrome for web development? Lots of devs recommend it for its tools and responsiveness.
Related Questions
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads