What Http Request Header Is Used to Identify the Acceptable Content Types That Can Be Returned?

HTTP headers provide vital information required for a HTTP transaction send via http protocol.

The general HTTP header format contains colon-separated proper noun - value pairs in the header field. Each of the name-value pair end with a wagon return (CR) and a line feed (LF) character sequence. Empty fields at the end of each header indicate the cease of the header.

The common header format followed by applications looks similar:

Types of HTTP headers

There are four types of HTTP message headers. They are:

• Full general Header
• Asking Header
• Response Header
• Entity Header

General Header

General Header fields take common applicability in request and response letters. The header fields use simply to the transmitted message and do non apply on the transferred entity.

The construction of a general header looks like:

Where,

Cache-control field specifies directives that accept to be followed by every caching mechanism on a asking and response system.

Connection field allows the sender to specify options required for a connection. The connectedness header has the following format:

Date field represents the engagement and fourth dimension during the initiation of the message. The date format specified in HTTP look like:

Pragma field helps to include implementation specific directive applicable to any recipient on a request and response system.

Trailer field value specifies whether a ready of header fields in bulletin trailer is encoded with chunk transfer-coding.

Transfer-Encoding field indicate whether whatsoever type of transformation is practical to the message trunk.

Upgrade field enables clients to specify boosted supported communication protocols. It also enables the server to switch protocols with the additional protocols.

Via field are mandatory fields used by proxies and gateways which indicate intermediate protocols. It too indicates asking recipient betwixt user-agent and server and response between server and customer.

Alarm field carries additional information on message condition and bulletin transformations which are non reflected in the message.

Alarm headers are usually sent with responses.

HTTP Request Header

The request header field allows clients to additionally pass request information and customer information to the server.

The structure of a request header looks like:

Where,

Accept field specifies media types which are adequate for response.

Here,

'*' is used to group media types in range

'*/*' indicate all media types

'type/*' indicate all subtypes of a type

Accept-Charset field indicates response acceptable character sets. Information technology makes clients capable to understand special-purpose grapheme sets to betoken the server to correspond the document in these character sets.

Accept-Encoding field is similar to Accept, restricts response acceptable content-coding.

Accept-Language field is similar to Take, restricts preferred set of natural languages.

Say-so field is for user agents who wish to authenticate themselves with the server.

Expect field indicates server behaviors required by a client.

From field contains e-mail service address of a user who controls the requesting user-agent.

Host field specifies the cyberspace host and requested resources port number from user URI.

If-Match field is used to make conditional methods.

If-Modified-Since field is used to make a provisional method. If the requested variant is non modified within the specified fourth dimension, the entity will not be returned from the server.

If-None-Match field allows efficient update of cache data with minimum transaction overhead.

If-Range field allows clients to receive part of the missing entity or otherwise, clients tin enquire to send the entire new entity.

If-Unmodified-Since field allows the server to perform requested operation if it has not been modified since the time specified in this field.

Max Forward field provides mechanisms with TRACE and OPTIONS methods to limit the asking forwarding proxies or gateways.

Proxy Authorisation field allows client to identify to secure proxy.

Range field specifies the HTTP entities in HTTP messages represented as a sequence of bytes. HTTP retrieval asking requests one or more sub range of entity using Get methods.

Referrer field allows clients to specify the address URI of the resource from which Asking-URI is establish.

TE field indicates extension transfer-coding information technology can accept in the response. Additionally, information technology indicates whether it will accept trailer fields in clamper transfer-coding.

User-Agent field contains information near the requesting user-amanuensis.

HTTP Response Header

The response header field allows the server to pass additional data through the responses other than elementary Status-Line response.

The structure of the response header looks similar:

Where,

Accept-Ranges field enables servers to indicate acceptance of resource range requests.

Age field indicates sender the estimate amount of time since server responded.

ETag field provides current value of the entity tag for a request.

Location field redirects recipients to locations other than Request-URI to complete identification of a new resources.

Proxy-Cosign field is a mandatory inclusion for proxy authentication response.

Retry-After field is used equally a response when a service is unavailable to bespeak the length of period for which service will remain unavailable to the client.

Server field contains information about software used by server to handle requests.

Vary field indicates request field that decide whether a cache is eligible to utilise the response of a request without revalidation of the response.

Www-Cosign field are used when a response message is unauthorized.

HTTP Entity Header

Entity header fields define metainformation almost the entity-body or the requested resource. The entity-header format looks like:

Where,

Let field listing the gear up of methods supported by Asking-URI identified resource.

Content-Encoding field is used as a media-type modifier.

Content-Language field describes natural language for clients of an entity.

Content-Length field indicates the size of an entity represented in decimal number.

Content-Location field provides resource location for an entity when it is attainable from a location other than Requested-URI.

Content-MD5 field provides message integrity cheque (MIC) using an MD5 digest on the entity body.

Content-Range field specifies where fractional body of the total entity-torso should exist practical.

Content-Type field indicates whether the media type of the entity trunk is sent to the recipient or Get method is used to send requests.

Expires field provides the date/time after which the response becomes stale.

Last Modified field indicates the date and time of last modification of the variant.

The gild in which field proper name appears in the header when received is insignificant. Conventionally general headers are placed first, followed by request or response header with entity header at the end.

Copyright Find: Please don't copy or translate this article without prior written permission from the HTTPDebugger.com

---

HTTP Debugger is a proxy-less HTTP analyzer for developers that provides the ability to capture and analyze HTTP headers, cookies, POST params, HTTP content and CORS headers from whatever browser or desktop application. Awesome UI and very easy to use. Non a proxy, no network issues!
Download Costless vii-Twenty-four hours Trial

housepriatter.blogspot.com

Source: https://www.httpdebugger.com/http/http_header.html

Share this post