How to Filter HTTP POST Requests in Wireshark
To filter HTTP POST requests in Wireshark, type http.request.method == "POST" into the display filter bar and press Enter. Wireshark then hides every packet except the HTTP requests that send data to a server, such as login forms, file uploads and API calls. That makes POST requests one of the fastest ways to see what left a host during an investigation. This post shows you how to filter HTTP POST requests in Wireshark, read what they carry, and do the same from the command line with tshark.
What an HTTP POST request is
HTTP clients send each request with a method, a word that says what the client wants the server to do. GET asks for a resource. POST sends data in the body of the request for the server to process. The full list of methods is in RFC 9110, the HTTP standard.
POST requests matter to analysts because they carry data out of a network. A POST request can hold:
- Form data. User names, passwords and search terms typed into a web page.
- File uploads. Documents sent to a web application or a file-sharing site.
- API calls. JSON sent to a web service by a script or application.
- Malware traffic. Stolen data, or check-ins to a command and control (C2) server.
Wireshark can only read HTTP that is not encrypted. HTTPS hides the method and body inside Transport Layer Security (TLS), unless you give Wireshark the session keys. The Wireshark TLS wiki page explains how to decrypt traffic from a browser you control, using the SSLKEYLOGFILE variable.
Filter HTTP POST requests in Wireshark
Open your capture, click the display filter bar above the packet list, and enter:
http.request.method == "POST"
The bar turns green when the filter is valid. Press Enter and the packet list shows only POST requests. Each line shows the source and destination, and the Info column shows the request line, such as POST /login.php HTTP/1.1.
You can combine the filter with other fields to narrow the results further. The Wireshark HTTP field reference lists every field you can use:
| Filter | What it shows |
|---|---|
http.request.method == "POST" && ip.src == 192.0.2.25 |
POST requests from one host. |
http.request.method == "POST" && http.host contains "example" |
POST requests to matching sites. |
http.request.method == "POST" && http.content_type contains "form" |
Submitted web forms only. |
http.request.method == "POST" && http.content_length > 100000 |
Requests carrying more than about 100 KB. |
For a quick overview, add the host and URI as columns. Right-click Host in the packet details pane of any HTTP request and choose Apply as Column, then do the same for Request URI. The packet list then reads like a list of the pages each host posted to.
Read what a POST request carried
Select a POST request and expand Hypertext Transfer Protocol in the packet details pane. For a submitted form, Wireshark also shows an HTML Form URL Encoded section, with each field name and value on its own line.
To read the whole exchange, right-click the packet and choose Follow > HTTP Stream. Wireshark shows the request in one colour and the server's reply in another:
POST /login.php HTTP/1.1
Host: intranet.example.com
Content-Type: application/x-www-form-urlencoded
Content-Length: 37
user=j.smith&pass=Summer2026&submit=1
HTTP/1.1 302 Found
Location: /dashboard.php
Set-Cookie: session=4f7a1c9e; HttpOnly
This example shows why plain HTTP is a problem. The password Summer2026 crossed the network in clear text, and anyone who could capture the traffic could read it. The 302 Found reply, which sends the browser to a dashboard, shows that the login worked.
Filter HTTP POST requests with tshark
tshark is Wireshark's command-line version. It takes the same display filters with -Y, which helps when a capture is too large to open comfortably, or when you want to script the search. The tshark manual page lists every option.
Windows PowerShell
& 'C:\Program Files\Wireshark\tshark.exe' -r capture.pcap -Y 'http.request.method == "POST"' -T fields -e ip.src -e http.host -e http.request.uri
Windows Command Prompt
"C:\Program Files\Wireshark\tshark.exe" -r capture.pcap -Y "http.request.method == \"POST\"" -T fields -e ip.src -e http.host -e http.request.uri
Linux
tshark -r capture.pcap -Y 'http.request.method == "POST"' -T fields -e ip.src -e http.host -e http.request.uri
macOS and BSD
tshark -r capture.pcap -Y 'http.request.method == "POST"' -T fields -e ip.src -e http.host -e http.request.uri
-T fields prints only the fields you name with -e, one request per line:
192.0.2.25 intranet.example.com /login.php
192.0.2.25 intranet.example.com /search.php
192.0.2.31 203.0.113.80 /gate.php
192.0.2.31 203.0.113.80 /gate.php
192.0.2.31 203.0.113.80 /gate.php
The last three lines stand out. Host 192.0.2.31 is posting repeatedly to a bare IP address rather than a named site, which is a common sign of malware checking in with its C2 server.
When the filter shows nothing
If you know there was HTTP traffic but the filter shows nothing, check these causes:
- The traffic is HTTPS. Encrypted requests show up as TLS, not HTTP. Filter on
tlsto confirm. - The server uses an unusual port. Wireshark only decodes HTTP on ports it expects. Right-click a packet, choose Decode As, and set the port to HTTP.
- The traffic is HTTP/2. Use
http2.headers.method == "POST"instead. - You set a capture filter, not a display filter. Capture filters use a different syntax and decide what is saved in the first place. The capture filter section of the user guide explains the difference.
Security considerations
POST requests show threat actors and defenders the same thing: data leaving a host. A threat actor who can capture unencrypted HTTP can read every password in it, which ATT&CK lists as Network Sniffing (T1040). Malware also uses POST requests to blend in with normal web traffic, which ATT&CK lists as Web Protocols (T1071.001).
To reduce the risk:
- Retire plain HTTP. Serve every login and form over HTTPS, and redirect HTTP to HTTPS.
- Watch for POSTs to bare IP addresses. Legitimate sites almost always use a name.
- Look for regular timing. Requests to the same address at fixed intervals suggest automated check-ins.
- Capture only with permission. Packet captures can hold passwords and personal data, so capture only on networks you are authorised to monitor, and store the files securely.
Our earlier post on analysing DNS tunnelling in Wireshark applies the same filtering approach to DNS. Network analysis is covered in depth in our Network Analysis Fundamentals module; browse the GemForge Labs catalogue to see what is available.
Further reading
- Building display filter expressions – The Wireshark guide to display filter syntax and operators.
- HTTP display filter reference – Every HTTP field Wireshark can filter on.
- Following protocol streams – How Follow Stream rebuilds a conversation.
