My HTTP Headers

Browsers do not send URLs alone — they attach HTTP headers describing device, language, and capabilities. Here is what your browser actually transmitted.

3-Line Summary

1Collect the live HTTP request headers your browser sent to this server.
2Inspect cookies, cache directives, and compression support.
3Learn how HTTP/2 and HTTP/3 compress headers for faster loading.

Role of HTTP Request Headers

HTTP headers carry metadata before the body of each request. Servers read them first to accept or reject requests and to choose language, format, and caching behavior.

Common HTTP Header Fields

- **Host:** Target server domain name. - **Connection:** Whether to keep the socket alive (e.g., keep-alive). - **Accept-Encoding:** Compression formats supported (gzip, deflate, br). - **Accept-Language:** Preferred language (e.g., en-US). - **Referer:** Previous page URL that linked here.

Cookie Headers and Security

Logged-in sessions work because browsers send Cookie headers with identity tokens. Servers should mark sensitive cookies HttpOnly, and you should log out or close the browser on shared PCs to clear session cookies.

GOOGLE ADSENSE

Frequently Asked Questions (FAQ)

Request headers carry client requirements to the server. Response headers carry status (200 OK), content type, security policies, and other instructions back to the browser.

Repeated headers grew large. Modern protocols store previous headers and send only differences, cutting overhead and speeding page loads.

Related Networking Utility Tools

Check My IP Address My Browser User-Agent VPN IP Check My IP Address Lookup