spinsurf.net
The place to be
de liste proxies
de liste proxies
List of HTTP header fields
From Wikipedia, the free encyclopedia Jump to: navigation, search | This article includes a list of references, related reading or external links, but its sources remain unclear because it lacks inline citations. Please improve this article by introducing more precise citations where appropriate. (September 2010) |
 | This article needs additional citations for verification. Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (September 2010) |
| HTTP |
| Persistence · Compression · HTTPS |
| Request methods |
| GET · POST · PUT · DELETE |
| Header fields |
| Cookie · ETag · Location · Referrer |
| X-Forwarded-For |
| Status codes |
| 301 Moved permanently |
| 302 Found |
| 303 See Other |
| 403 Forbidden |
| 404 Not Found |
| This box: view · talk · edit |
HTTP header fields are components of the message header of requests and responses in the Hypertext Transfer Protocol (HTTP). They define the operating parameters of an HTTP transaction.
The header fields are transmitted after the request or response line, the first line of a message. Header fields are colon-separated name-value pairs in clear-text string format, terminated by a carriage return (CR) and line feed (LF) character sequence. The end of the header fields is indicated by an empty field, resulting in the transmission of two consecutive CR-LF pairs.
A core set of fields is standardized by the Internet Engineering Task Force (IETF) in RFC 2616 and other updates and extension documents (e.g., RFC 4229), and must be implemented by all HTTP-compliant protocol implementations. Additional field names and permissible values may be defined by each application.
Many field values may contain a quality (q) key-value pair, specifying a statistical weight to use in content negotiation.
Contents
|
Requests
| Field name | Description | Example |
|---|---|---|
| Accept | Content-Types that are acceptable | Accept: text/plain |
| Accept-Charset | Character sets that are acceptable | Accept-Charset: utf-8 |
| Accept-Encoding | Acceptable encodings | Accept-Encoding: <compress | gzip | deflate | sdch | identity> |
| Accept-Language | Acceptable languages for response | Accept-Language: en-US |
| Authorization | Authentication credentials for HTTP authentication | Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ== |
| Cache-Control | Used to specify directives that MUST be obeyed by all caching mechanisms along the request/response chain | Cache-Control: no-cache |
| Connection | What type of connection the user-agent would prefer | Connection: close |
| Cookie | an HTTP cookie previously sent by the server with Set-Cookie (below) | Cookie: $Version=1; Skin=new; |
| Content-Length | The length of the request body in octets (8-bit bytes) | Content-Length: 348 |
| Content-MD5 | A Base64-encoded binary MD5 sum of the content of the request body | Content-MD5: Q2hlY2sgSW50ZWdyaXR5IQ== |
| Content-Type | The mime type of the body of the request (used with POST and PUT requests) | Content-Type: application/x-www-form-urlencoded |
| Date | The date and time that the message was sent | Date: Tue, 15 Nov 1994 08:12:31 GMT |
| Expect | Indicates that particular server behaviors are required by the client | Expect: 100-continue |
| From | The email address of the user making the request | From: user@example.com |
| Host | The domain name of the server (for virtual hosting), mandatory since HTTP/1.1 | Host: en.wikipedia.org |
| If-Match | Only perform the action if the client supplied entity matches the sam
Nothing was found!
Even more about de liste proxiesMedia
Network
sponsoredMetaCrawler |
