Learn / Field guide

HTTP: requests and responses

HTTP is how browsers and apps ask for pages and data. Over plain HTTP, every header and body is readable on the network; over HTTPS, the same messages travel inside TLS.

23 HTTP fields, explained

Field names are the ones Wireshark and TShark use, so you can search for them or use them in display filters.

http.request.line

The request: a method (like GET), a path, and the HTTP version.

Why it matters: Because it's unencrypted HTTP, anyone on the path can read it.

http.response.line

The server's status: a code like 200 (OK) or 404 (Not Found).

Why it matters: Codes in the 400s are client errors; 500s are server errors.

http.host

The website name the request is for.

Why it matters: One server can host many sites; this says which one.

http.user_agent

Identifies the software making the request.

http.accept

The content types the client will accept.

http.content_type

The format of the response body, such as JSON or HTML.

http.content_length

The size of the response body in bytes.

http.request.method

What the client wants to do: GET reads something, POST sends something.

http.request.uri

The path of the page or resource requested.

http.request.uri.path

The path part of the address, without the query.

http.request.uri.query

The part of the address after ?, often carrying search terms or IDs.

Why it matters: Over plain HTTP, anyone on the path can read it.

http.request.uri.query.parameter

One name=value pair from the query.

http.request.full_uri

The full address requested, rebuilt by Wireshark from the host and path.

http.request.version

The HTTP version the client uses.

http.response.version

The HTTP version the server uses.

http.response.code

The status code: 200 means OK, 404 not found, 500 server error.

http.response.code.desc

The meaning of the status code.

http.response.phrase

The short text after the status code, such as OK.

http.content_length_header

How many bytes of content follow the headers.

http.request_in

Which packet carried the request this response answers.

http.time

Time from the request to this response.

Why it matters: The server's thinking time plus one round trip.

http.file_data

The content of the response, such as the HTML of a page.

http.server

The software the server says it runs.