3 ms·
> The network tools suck (why is it so hard to find the request payload??) Speaking as a non-web-dev who looks at web inspector once in a blue moon, this took
by lilyball 6y ago
> The network tools suck (why is it so hard to find the request payload??)
Speaking as a non-web-dev who looks at web inspector once in a blue moon, this took me about 5 seconds. I looked at the Network tab, selected a resource, noticed the information in the detail pane had headers but not payload, and then right-clicked the resource and selected "Reveal in Sources Tab" which revealed the payload there.
- phaemon 6y agoClearly not an old-school mac user. Right click?!
- usmannk 6y agoIf I followed your instructions correctly, that's the response payload not the request.
- ianwalter 6y agoYes, which I think helps prove the parent's point!
- thiht 6y agoExactly :) the request payload is hidden at the bottom of the Headers tab (yep...), you need to uncollapse it. I always forget where it is and confuse it with the response payload, which is really confusing when trying to debug what you send to a REST endpoint
- quicklyfrozen 6y agoPersonally I'm usually looking through a bunch of responses trying to find the one I'm interested in, and that workflow sounds pretty awful.
- ianwalter 6y agoIsn't that the response payload and not the request payload?