Tradução em progresso.
Cabeçalhos proprietários personalizados podem ser adicionados usando o prefixo 'X-', mas essa convenção foi depreciada em Junho de 2012, devido aos inconvenientes que causou quando os campos não-padronizados tornaram-se padronizados na RFC 6648; outros estão listados em um registro IANA, cujo o conteúdo original foi definido na RFC 4229. O IANA também mantém o registro das propostas de novas mensagens de cabeçalhos HTTP.
Cabeçalhos podem ser classificados de acordo com os seus contextos:
- Cabeçalho genérico: Cabeçalhos que podem ser usados tanto em solicitações quanto em respostas, porém sem relação com os dados eventualmente transmitidos no corpo da mensagem.
- Cabeçalho de solicitação: Cabeçalhos contendo mais informação sobre o recurso a ser obtido ou sobre o próprio cliente.
- Cabeçalho de resposta: Cabeçalhos contendo informação adicional sobre a solicitação, como a sua localização ou sobre o servidor.
- Cabeçalho de entidade: Cabeçalhos contendo mais informação sobre o conteúdo da entidade, como o tamanho do conteúdo ou o seu MIME-type.
Cabeçalhos também podem ser classificados de acordo com a forma que são manipulados por proxies.
- End-to-end headers
- Esses cabeçalhos devem ser transmitidos para o destinatário final da mensagem; isso é, o servidor em caso de solicitação ou o cliente caso resposta. Proxies intermediários devem reenviar cabeçalhos de end-to-end sem alterações e caches devem armazená-los.
- Hop-by-hop headers
- Esses cabeçalhos são significativos apenas para uma única conexão a nível de transporte e não devem ser reenviados por proxies ou armazenados em cache. Tais cabeçalhos são:
Upgrade. Observe que apenas cabeçalhos hop-by-hop podem ser definidos utilizando o cabeçalho genérico
A lista a seguir resume os cabeçalhos HTTP pela categoria de uso. Para uma lista alfabética, utilize o menu à esquerda.
- The time in seconds the object has been in a proxy cache.
- Specifies directives for caching mechanisms in both, requests and responses.
- The date/time after which the response is considered stale.
- Implementation-specific header that may have various effects anywhere along the request-response chain. Used for backwards compatibility with HTTP/1.0 caches where the
Cache-Controlheader is not yet present.
- A general warning field containing information about possible problems.
- It is a validator, the last modification date of the resource, used to compare several versions of the same resource. It is less accurate than
ETag, but easier to calculate in some environments. Conditional requests using
If-Unmodified-Sinceuse this value to change the behavior of the request.
- It is a validator, a unique string identifying the version of the resource. Conditional requests using
If-None-Matchuse this value to change the behavior of the request.
- Makes the request conditional and applies the method only if the stored resource matches one of the given ETags.
- Makes the request conditional and applies the method only if the stored resource doesn't match any of the given ETags. This is used to update caches (for safe requests), or to prevent to upload a new resource when one is already existing.
- Makes the request conditional and expects the entity to be transmitted only if it has been modified after the given date. This is used to transmit data only when the cache is out of date.
- Makes the request conditional and expects the entity to be transmitted only if it has not been modified after the given date. This is used to ensure the coherence of a new fragment of a specific range with previous ones, or to implement an optimistic concurrency control system when modifying existing documents.
- Controls whether or not the network connection stays open after the current transaction finishes.
- Controla por quanto tempo uma conexão persistente deve permanecer aberta.
Negociação de conteúdo
- Informs the server about the types of data that can be sent back. It is MIME-type.
- Informs the server about which character set the client is able to understand.
- Informs the server about the encoding algorithm, usually a compression algorithm, that can be used on the resource sent back.
- Informs the server about the language the server is expected to send back. This is a hint and is not necessarily under the full control of the user: the server should always pay attention not to override an explicit user choice (like selecting a language in a drop down list).
- Contains stored HTTP cookies previously sent by the server with the
- Send cookies from the server to the user agent.
- Used to contain an HTTP cookie, previously sent by the server with the
Set-Cookie2header, but has been obsoleted by the specification. Use
- Used to send cookies from the server to the user agent, but has been obsoleted by the specification. Use
- Indica se a resposta pode ser compartilhada.
- Indicates whether or not the response to the request can be exposed when the credentials flag is true.
- Used in response to a preflight request to indicate which HTTP headers can be used when making the actual request.
- Specifies the method or methods allowed when accessing the resource in response to a preflight request.
- Indicates which headers can be exposed as part of the response by listing their names.
- Indicates how long the results of a preflight request can be cached.
- Used when issuing a preflight request to let the server know which HTTP headers will be used when the actual request is made.
- Used when issuing a preflight request to let the server know which HTTP method will be used when the actual request is made.
- Indicates where a fetch originates from.
Do Not Track
- Used for expressing the user's tracking preference.
- Indicates the tracking status that applied to the corresponding request.
- Is a response header if the ressource transmitted should be displayed inline (default behavior when the header is not present), or it should be handled like a download and the browser should present a 'Save As' window.
Informações do corpo da mensagem
- indicates the size of the entity-body, in decimal number of octets, sent to the recipient.
- Indica o tipo de mídia do recurso.
- Usado para especificar o algoritmo de compressão.
- Describes the language(s) intended for the audience, so that it allows a user to differentiate according to the users' own preferred language.
- Indicates an alternate location for the returned data.
Roteamento de mensagens
- Added by proxies, both forward and reverse proxies, and can appear in the request headers and the response headers.
- Indicates the URL to redirect a page to.
Contexto da requisição
- Contains an Internet email address for a human user who controls the requesting user agent.
- Specifies the domain name of the server (for virtual hosting), and (optionally) the TCP port number on which the server is listening.
- The address of the previous web page from which a link to the currently requested page was followed.
- Governs which referrer information sent in the
Refererheader should be included with requests made.
- Contains a characteristic string that allows the network protocol peers to identify the application type, operating system, software vendor or software version of the requesting software user agent. See also the Firefox user agent string reference.
Contexto da resposta
- Contains information about the software used by the origin server to handle the request.
- Indicates if the server supports range requests and, if so, in which unit the range can be expressed.
- Create a conditional range request that is only fulfilled if the etag or date given in parameter match the remote resource. Used to prevent downloading two ranges from incompatible version of the resource.
- Controls resources the user agent is allowed to load for a given page.
- Allows web developers to experiment with policies by monitoring (but not enforcing) their effects. These violation reports consist of JSON documents sent via an HTTP
POSTrequest to the specified URI.
- Associates a specific cryptographic public key with a certain web server to decrease the risk of MITM attacks with forged certificates.
- Sends reports to the report-uri specified in the header and does still allow clients to connect to the server even if the pinning is violated.
- Force communication using HTTPS instead of HTTP.
- Sends a signal to the server expressing the client’s preference for an encrypted and authenticated response, and that it can successfully handle the
- Disables MIME sniffing and forces browser to use the type given in
- Indicates whether or not a browser should be allowed to render a page in a
- Enables cross-site scripting filtering.
- Specifies the the form of encoding used to safely transfer the entity to the user.
- Specifies the transfer encodings the user agent is willing to accept.
- Allows the sender to include additional fields at the end of chunked message.
- Contains the date and time at which the message was originated.
- Indicates how long the user agent should wait before making a follow-up request.
- This is a Proposed Internet Standard. To view a comprehensive list of all Official and Proposed Internet Standards with detailed information about each, visit this Internet Standards reference, which is updated daily. The relevant RFC document for the Upgrade header field standard is RFC 7230, section 6.7. The standard establishes rules for upgrading or changing to a different protocol on the current client, server, transport protocol connection. For example, this header standard allows a client to change from HTTP 1.1 to HTTP 2.0, assuming the server decides to acknowledge and implement the Upgrade header field. Niether party is required to accept the terms specified in the Upgrade header field. It can be used in both client and server headers. If the Upgrade header field is specified, then the sender MUST also send the Connection header field with the upgrade option specified. For details on the Connection header field please see section 6.1 of the aforementioned RFC.
- Determines how to match future request headers to decide whether a cached response can be used rather than requesting a fresh one from the origin server.