HTTP Response: Difference between revisions
Jump to navigation
Jump to search
Line 46: | Line 46: | ||
* [[HTTP Response Header Accept-Ranges|Accept-Ranges]] | * [[HTTP Response Header Accept-Ranges|Accept-Ranges]] | ||
* Age | * [[HTTP Response Header Age|Age]] | ||
* ETag | * [[HTTP Response Header ETag|ETag]] | ||
* Location | * [[HTTP Response Header Location| Location]] | ||
* Proxy-Authenticate | * [[HTTP Response Header Proxy-Authenticate|Proxy-Authenticate]] | ||
* Retry-After | * [[HTTP Response Header Retry-After|Retry-After]] | ||
* Server | * [[HTTP Response Header Server| Server]] | ||
* Vary | * [[HTTP Response Header Vary|Vary]] | ||
* WWW-Authenticate | * [[HTTP Response Header WWW-Authenticate|WWW-Authenticate]] | ||
==Entity Headers== | ==Entity Headers== |
Revision as of 03:05, 6 January 2017
External
- RFC 2616 Section 6 Response https://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html
Internal
Overview
A HTTP response consists of a status line, followed by an optional set of headers, followed by blank line followed by an optional message body.
This is a simple example:
HTTP/1.1 200 OK Content-Type: text/html HttpServer: Test Server Content-Length: 1024 ... ...
The Response Status Line
The status line starts with the protocol version followed by a numeric status code and its associated reason phrase, with each element separated by space. No CR or LF is allowed except in the final CRLF sequence.
For more details about the status code, see
Example:
HTTP/1.1 200 OK
The Headers
The headers included with a response are part of one of the following category:
General Headers
Response Headers
The response headers allow the server to pass additional information about the response which cannot be placed in the status line.
Entity Headers
The Blank Line
The Message Body
More about HTTP response: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html.
The HTTP Response Headers
- http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
- http://en.wikipedia.org/wiki/List_of_HTTP_headers