Network Working Group R. Fielding Request for Comments: 2616 ...

More documents

Recommendations

Info

names) MUST use the following rules for determining the requestedresource on an HTTP/1.1 request:1. If Request-URI is an absoluteURI, the host is part of theRequest-URI. Any Host header field value in the request MUST beignored.2. If the Request-URI is not an absoluteURI, and the request includesa Host header field, the host is determined by the Host headerfield value.3. If the host as determined by rule 1 or 2 is not a valid host onthe server, the response MUST be a 400 (Bad Request) error message.Recipients of an HTTP/1.0 request that lacks a Host header field MAYattempt to use heuristics (e.g., examination of the URI path forsomething unique to a particular host) in order to determine whatexact resource is being requested.5.3 Request Header FieldsThe request-header fields allow the client to pass additionalinformation about the request, and about the client itself, to theserver. These fields act as request modifiers, with semanticsequivalent to the parameters on a programming language methodinvocation.request-header = Accept ; Section 14.1| Accept-Charset ; Section 14.2| Accept-Encoding ; Section 14.3| Accept-Language ; Section 14.4| Authorization ; Section 14.8| Expect ; Section 14.20| From ; Section 14.22| Host ; Section 14.23| If-Match ; Section 14.24Fielding, et al. Standards Track [Page 38]RFC 2616 HTTP/1.1 June 1999| If-Modified-Since ; Section 14.25| If-None-Match ; Section 14.26| If-Range ; Section 14.27| If-Unmodified-Since ; Section 14.28| Max-Forwards ; Section 14.31| Proxy-Authorization ; Section 14.34| Range ; Section 14.35
| Referer ; Section 14.36| TE ; Section 14.39| User-Agent ; Section 14.43Request-header field names can be extended reliably only incombination with a change in the protocol version. However, new orexperimental header fields MAY be given the semantics of requestheaderfields if all parties in the communication recognize them tobe request-header fields. Unrecognized header fields are treated asentity-header fields.6 ResponseAfter receiving and interpreting a request message, a server respondswith an HTTP response message.Response = Status-Line ; Section 6.1*(( general-header ; Section 4.5| response-header ; Section 6.2| entity-header ) CRLF) ; Section 7.1CRLF[ message-body ] ; Section 7.26.1 Status-LineThe first line of a Response message is the Status-Line, consistingof the protocol version followed by a numeric status code and itsassociated textual phrase, with each element separated by SPcharacters. No CR or LF is allowed except in the final CRLF sequence.Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF6.1.1 Status Code and Reason PhraseThe Status-Code element is a 3-digit integer result code of theattempt to understand and satisfy the request. These codes are fullydefined in section 10. The Reason-Phrase is intended to give a shorttextual description of the Status-Code. The Status-Code is intendedfor use by automata and the Reason-Phrase is intended for the humanuser. The client is not required to examine or display the Reason-Phrase.Fielding, et al. Standards Track [Page 39]RFC 2616 HTTP/1.1 June 1999The first digit of the Status-Code defines the class of response. Thelast two digits do not have any categorization role. There are 5
Page 2: eferred to as "HTTP/1.1", and is an
Page 5 and 6: 12.1 Server-driven Negotiation ....
Page 7 and 8: 14.40 Trailer .....................
Page 9 and 10: 1.2 RequirementsThe key words "MUST
Page 12 and 13: Fielding, et al. Standards Track [P
Page 14 and 15: equest chain ----------------------
Page 16 and 17: Elements separated by a bar ("|") a
Page 18 and 19: HTTP/1.1 header field values can be
Page 20 and 21: An application that sends a request
Page 22 and 23: 3.2.3 URI ComparisonWhen comparing
Page 26 and 27: is not desirable and is discouraged
Page 28 and 29: CRLFchunk = chunk-size [ chunk-exte
Page 30 and 31: When in canonical form, media subty
Page 32 and 33: 3.9 Quality ValuesHTTP content nego
Page 34 and 35: RFC 2616 HTTP/1.1 June 1999HTTP/1.1
Page 36 and 37: message-body = entity-body| Transfe
Page 38 and 39: in advance.Messages MUST NOT includ
Page 40 and 41: equested resource, and 501 (Not Imp
Page 44 and 45: values for the first digit:- 1xx: I
Page 48 and 49: how the transfer-length of a messag
Page 50 and 51: connection-token close.If either th
Page 52 and 53: idempotent (see section 9.1.2). Non
Page 54 and 55: compatibility with RFC 2068, a serv
Page 56 and 57: If at any point an error status is
Page 58 and 59: optional features implemented by th
Page 60 and 61: - Extending a database through an a
Page 62 and 63: intervention (or other means) on th
Page 64 and 65: 10.1.2 101 Switching ProtocolsThe s
Page 66 and 67: esponse MAY include new or updated
Page 70 and 71: The response MUST include the follo
Page 72 and 73: If the client is sending data, a se
Page 74 and 75: If the response could be unacceptab
Page 76 and 77: 10.4.15 414 Request-URI Too LongThe
Page 78 and 79: 10.5.5 504 Gateway TimeoutThe serve
Page 82 and 83: Caching would be useless if it did
Page 84 and 85: Warning (but without removing any e
Page 86 and 87: If the user has overridden the basi
Page 88 and 89: in the past. This means that the re
Page 90 and 91: RFC 2616 HTTP/1.1 June 1999the time
Page 92 and 93:
simple:response_is_fresh = (freshne
Page 94 and 95:
match.In HTTP/1.1, a conditional re
Page 96 and 97:
validators or strong validators. Cl
Page 98 and 99:
- MAY send a weak entity tag instea
Page 100 and 101:
Unless specifically constrained by
Page 102 and 103:
Fielding, et al. Standards Track [P
Page 104 and 105:
warn-code 1xx, which are deleted ev
Page 106 and 107:
for the associated entity, its enti
Page 108 and 109:
- DELETE- POSTIn order to prevent d
Page 110 and 111:
The Accept request-header field can
Page 112 and 113:
image/jpeg = 0.5text/html;level=2 =
Page 114 and 115:
Note: If the request does not inclu
Page 116 and 117:
Accept-Ranges: bytesbut are not req
Page 118 and 119:
containing an Authorization field,
Page 120 and 121:
- Restrictions on what may be store
Page 122 and 123:
improve privacy in some cases, we c
Page 124 and 125:
Page 126 and 127:
must-revalidateBecause a cache MAY
Page 128 and 129:
understand.For example, consider a
Page 130 and 131:
new coding is known to be acceptabl
Page 132 and 133:
14.14 Content-LocationThe Content-L
Page 134 and 135:
Note: while the definition of Conte
Page 136 and 137:
server SHOULD return them in the or
Page 138 and 139:
Some origin server implementations
Page 140 and 141:
Expires = "Expires" ":" HTTP-dateAn
Page 142 and 143:
A client MUST include a Host header
Page 144 and 145:
een modified since the date given b
Page 146 and 147:
RFC 2616 HTTP/1.1 June 1999If none
Page 148 and 149:
14.29 Last-ModifiedThe Last-Modifie
Page 150 and 151:
MAY require that behavior be consis
Page 152 and 153:
yte-ranges-specifier = bytes-unit "
Page 154 and 155:
Content) instead of 200 (OK).- The
Page 156 and 157:
The TE request-header field indicat
Page 158 and 159:
Page 160 and 161:
a cache cannot determine from the r
Page 162 and 163:
SHOULD NOT, by default, forward the
Page 164 and 165:
this user agent behavior in mind.Re
Page 166 and 167:
designers and implementors be parti
Page 168 and 169:
strongly correlated to the membersh
Page 170 and 171:
serious security considerations. Co
Page 172 and 173:
The HTTP protocol has evolved consi
Page 174 and 175:
Protocol -- HTTP/1.0", RFC 1945, Ma
Page 176 and 177:
Implementation and Analysis", RFC 1
Page 178 and 179:
University of California, IrvineIrv
Page 180 and 181:
Page 182 and 183:
Notes:1) Additional CRLFs may prece
Page 184 and 185:
full compliance with the MIME proto
Page 186 and 187:
ead chunk-size and CRLF}read entity
Page 188 and 189:
- understand any valid response in
Page 190 and 191:
CREATE had a race that required an
Page 192 and 193:
also needed to be a general header,
Page 194:
show all

Network Working Group R. Fielding Request for Comments: 2616 ...

Create successful ePaper yourself

Delete template?

Save as template?