HTTP Headers Sent

Header	Value
Host	headers.utils.com
X-Real-Ip	216.73.216.6
X-Forwarded-For	216.73.216.6
X-Scheme	https
Connection	close
Accept	*/*
User-Agent	Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
Accept-Encoding	gzip, br, zstd, deflate

---

Web Headers definition

HTTP headers are a method for client and the server to share additional information that will help with web request.

An HTTP header consists of its case-insensitive name followed by a colon (:), then by its value. Whitespace before the value is ignored.

Below is a list of common HTTP headers you might encounter, each accompanied by a simple description to illustrate its purpose and how it influences web communication:

• Host: Specifies the domain name of the server (and optionally the TCP port number).
• X-Real-Ip: Used by proxies to indicate the original IP address of the client connecting to them.
• X-Forwarded-For: Identifies the originating IP addresses of a client connecting through an HTTP proxy or load balancer.
• X-Scheme: Indicates the protocol (HTTP or HTTPS) that a client used to connect to your server.
• Connection: Manages whether the network connection stays open or closes after the current transaction completes.
• Sec-Ch-Ua: Provides information about the browser's brand and version to the server.
• Sec-Ch-Ua-Mobile: Indicates if the browser is on a mobile device (Yes or No).
• Sec-Ch-Ua-Platform: Provides the platform (operating system) of the browser to the server.
• Upgrade-Insecure-Requests: Requests the server to prefer secure versions of the URL when possible.
• User-Agent: Describes the browser and operating system to the server.
• Accept: Specifies the media types (HTML, JSON, etc.) that the browser is willing to receive.
• Sec-Fetch-Site: Indicates the relationship between the origin of the request and the origin of the fetched resource.
• Sec-Fetch-Mode: Specifies the mode for the request (e.g., cors, no-cors).
• Sec-Fetch-User: Indicates if the request was triggered by user activation.
• Sec-Fetch-Dest: Indicates the intended destination of the request (e.g., document, script).
• Referer: Indicates the address of the previous web page from which a link to the currently requested page was followed.
• Accept-Encoding: Indicates what content encodings (gzip, deflate) the client understands.
• Accept-Language: Indicates the language(s) preferred by the user for the response.
• Priority: Indicates the importance of the resource in the context of the client’s current set of tasks.
• Cookie: Sends stored cookies from the user's computer to the server.

Typically proprietary headers start with the X- prefix. However, this convention was deprecated in June 2012 because of the inconveniences it caused when nonstandard fields became standard in RFC 6648; others are listed in an IANA registry, whose original content was defined in RFC 4229. IANA also maintains a registry of proposed new HTTP headers.

---

---

Feedback