Which filter targets HTTP requests in Wireshark?

Study for the Wireshark Block 5 Exam. Prepare with flashcards and multiple choice questions, each offering hints and explanations. Ace your exam with the best resources!

Multiple Choice

Which filter targets HTTP requests in Wireshark?

Explanation:
Target HTTP requests means filtering for the HTTP request messages themselves, not just any traffic on a port. The best filter for this in Wireshark is http.request, which matches packets that carry an HTTP request (like GET or POST) and lets you inspect the request line, headers, and body. In contrast, http.response filters for server responses, so you’d use that to see replies. A port-based filter such as tcp.port==80 would include all traffic to and from port 80, not just requests, and may pull in non-HTTP traffic if any exists on that port. ip.addr is too broad, selecting packets by IP address rather than the HTTP protocol. You can further refine with http.request.method to see specific methods (e.g., GET, POST) if needed.

Target HTTP requests means filtering for the HTTP request messages themselves, not just any traffic on a port. The best filter for this in Wireshark is http.request, which matches packets that carry an HTTP request (like GET or POST) and lets you inspect the request line, headers, and body. In contrast, http.response filters for server responses, so you’d use that to see replies. A port-based filter such as tcp.port==80 would include all traffic to and from port 80, not just requests, and may pull in non-HTTP traffic if any exists on that port. ip.addr is too broad, selecting packets by IP address rather than the HTTP protocol. You can further refine with http.request.method to see specific methods (e.g., GET, POST) if needed.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy