HTTP Response: Difference between revisions
Jump to navigation
Jump to search
| (22 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=External= | |||
* RFC 2616 Section 6 Response https://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html | |||
=Internal= | =Internal= | ||
| Line 6: | Line 9: | ||
=Overview= | =Overview= | ||
A ''HTTP response'' consists of a | A ''HTTP response'' consists of a [[#The_Response_Status_Line|status line]], followed by an optional set of [[#The_Headers|headers]], followed by [[#The_Blank_Line|blank line]] followed by an optional [[#The_Message_Body|message body]]. | ||
This is a simple example: | |||
<pre> | <pre> | ||
| Line 16: | Line 19: | ||
Content-Length: 1024 | Content-Length: 1024 | ||
... | |||
... | |||
</pre> | </pre> | ||
=The Response Status Line= | |||
The status line starts with the [[#Protocol_Version|protocol version]] followed by a numeric [[#Status_Code|status code]] and its associated [[Reason_Phrase|reason phrase]], with each element separated by space. No CR or LF is allowed except in the final CRLF sequence. | |||
Example: | |||
HTTP/1.1 200 OK | |||
==Protocol Version== | |||
==Status Code== | |||
The '''status code''' is also called '''response code'''. | |||
For more details about the status code, see {{Internal|HTTP Status Codes|HTTP Status Codes}} | |||
==Reason Phrase== | |||
=The Headers= | |||
{{External2|http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html|http://en.wikipedia.org/wiki/List_of_HTTP_headers}} | |||
The headers included with a response are part of one of the following category: | |||
==General Headers== | |||
{{Internal|General HTTP Header Fields|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. | |||
* [[HTTP Response Header Accept-Ranges|Accept-Ranges]] | |||
* [[HTTP Response Header Age|Age]] | |||
* [[HTTP Response Header ETag|ETag]] | |||
* [[HTTP Response Header Location| Location]] | |||
* [[HTTP Response Header Proxy-Authenticate|Proxy-Authenticate]] | |||
* [[HTTP Response Header Retry-After|Retry-After]] | |||
* [[HTTP Response Header Server| Server]] | |||
* [[HTTP Response Header Vary|Vary]] | |||
* [[HTTP Response Header WWW-Authenticate|WWW-Authenticate]] | |||
==Entity Headers== | |||
{{Internal|Entity HTTP Header Fields|Entity Headers}} | |||
=The Blank Line= | |||
=The HTTP Response | =The HTTP Response Body= | ||
The optional response body is referred to as the '''HTTP entity''': | |||
{{Internal|HTTP Entity|HTTP Entity}} | |||
Latest revision as of 19:21, 26 September 2018
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.
Example:
HTTP/1.1 200 OK
Protocol Version
Status Code
The status code is also called response code.
For more details about the status code, see
Reason Phrase
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 HTTP Response Body
The optional response body is referred to as the HTTP entity: