I'm curious about a quirk in browser behavior: why is it that in the network tab of devtools, I can't see the request headers and body until after the response comes back? I encountered this while working on my web application—it sends a request that takes quite a while, and I want to check what I sent in the request body. The only times I can see it are when the request either fails or succeeds. So far, my only way around this has been to log the details in the code itself. I primarily use Firefox on MacOS, but I believe this is an issue across all browsers, not just Firefox. By the way, I've heard it works differently in Chrome, but I'm not a fan of that browser. Still, it seems odd that Firefox handles it this way.
5 Answers
Just tried it on my Mac, and you're right—Chrome shows the headers and payload right off the bat, but Firefox waits until the request is completed. This design choice is perplexing and definitely needs some improvement from Mozilla.
You should definitely check out Burp Suite! It’s a great tool for intercepting requests and allows you to see everything before the response. It can really help with situations like this.
I feel you! I've got a Laravel app that's slower than molasses in a local Docker setup. It’s tough when you have to wait to see what’s being sent in the request—it can really slow down your debugging. But hey, using an Nginx configuration instead of `artisan serve` might speed things up for you!
In Chrome, you actually can see the request headers while it’s still pending! Firefox is definitely lagging behind here. It's frustrating, especially when you're trying to debug slow requests.
Honestly, if you want better visibility for web development, switching to Chrome might be a good idea. It’s just more robust for this kind of work!
Yeah, `artisan serve` does limit to one request at a time. Nginx can definitely handle multiple requests better.