Как найти post запрос

asked Mar 24, 2013 at 20:23

1. Go to Chrome Developer Tools (Chrome Menu -> More Tools -> Developer Tools)
2. Choose “Network” tab
3. Refresh the page you’re on
4. You’ll get list of http queries that happened, while the network console was on. Select one of them in the left
5. Choose “Headers” tab

Voila!

You can filter for HTTP POST requests with the Chrome DevTools. Just do the following:

1. Open Chrome DevTools (Cmd+Opt+I on Mac, Ctrl+Shift+I or F12 on
   Windows) and click on the “Network” tab
2. Click on the “Filter” icon
3. Enter your filter method: method:POST
4. Select the request you want to debug
5. View the details of the request you want to debug

Screenshot

Tested with Chrome Version 53.

You can use Canary version of Chrome to see request payload of POST requests.

answered Aug 25, 2015 at 8:51

Another option that may be useful is a dedicated HTTP debugging tool. There’s a few available, I’d suggest HTTP Toolkit: an open-source project I’ve been working on (yeah, I might be biased) to solve this same problem for myself.

The main difference is usability & power. The Chrome dev tools are good for simple things, and I’d recommend starting there, but if you’re struggling to understand the information there, and you need either more explanation or more power then proper focused tools can be useful!

For this case, it’ll show you the full POST body you’re looking for, with a friendly editor and highlighting (all powered by VS Code) so you can dig around. It’ll give you the request & response headers of course, but with extra info like docs from MDN (the Mozilla Developer Network) for every standard header and status code you can see.

A picture is worth a thousand StackOverflow answers:

answered Sep 13, 2019 at 18:43

On Chrome 96 DevTools Network Tab;

After clicking the request, there is a “Payload” tab that shows the Form Data:

You can view the data as url encoded / decoded:

You can view the data as source / parsed:

Even if the method is GET you can see the Payload as Query String Parameters:

answered Nov 21, 2021 at 10:56

It has a tricky situation: If you submit a post form, then Chrome will open a new tab to send the request. It’s right until now, but if it triggers an event to download file(s), this tab will close immediately so that you cannot capture this request in the Dev Tool.

Solution:
Before submitting the post form, you need to cut off your network, which makes the request cannot send successfully so that the tab will not be closed. And then you can capture the request message in the Chrome Devtool(Refreshing the new tab if necessary)

answered Mar 16, 2019 at 13:49

dev mambadev mamba

6767 silver badges10 bronze badges

The other people made very nice answers, but I would like to complete their work with an extra development tool. It is called Live HTTP Headers and you can install it into your Firefox, and in Chrome we have the same plug in like this.

Working with it is queit easy.

1. Using your Firefox, navigate to the website which you want to get your post request to it.

2. In your Firefox menu Tools->Live Http Headers

3. A new window pop ups for you, and all the http method details would be saved in this window for you. You don’t need to do anything in this step.

4. In the website, do an activity(log in, submit a form, etc.)

5. Look at your plug in window. It is all recorded.

Just remember you need to check the Capture.

answered Nov 5, 2017 at 15:05

asked Oct 25, 2009 at 23:23

You could just use the Chrome Developer Tools, if you only need to track requests.
Activate them with Ctrl+Shift+I and select the Network tab.

This works also when Chrome talks HTTPS with another server (and unless you have the HTTPS private key you cannot use Wireshark to sniff that traffic).

(I copied this answer from this related query.)

With Firefox you can use the Network tab (Ctrl+Shift+E or Command+Option+E). The sub-tab “Params” shows the submitted form data.

Reference: https://developer.mozilla.org/en-US/docs/Tools/Network_Monitor/request_details#Params

Alternatively, in the console (Ctrl+Shift+K or Command+Option+K) right click on the big pane and check “Log Request and Response Bodies”. Then when the form is submitted, a line with POST <url> will appear. Click on it; it will open a new window with the form data.

As of the time of originally writing this reply, both methods messed up newlines in textarea fields. The former deleted them, the latter converted them to blanks. I haven’t checked with a newer version.

answered Aug 24, 2015 at 15:20

Do you have control of the browser POSTing the data?

If you do, then just use Firebug. It’s got a lot of usefull features, including this

answered Oct 25, 2009 at 23:27

answered Oct 26, 2009 at 0:07

fgohilfgohil

431 silver badge7 bronze badges

parmer_110parmer_110

3052 silver badges8 bronze badges