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

More documents

Recommendations

Info

eferred to as "HTTP/1.1", and is an update to RFC 2068 [33].Fielding, et al. Standards Track [Page 1]RFC 2616 HTTP/1.1 June 1999Table of Contents1 Introduction ...................................................71.1 Purpose......................................................71.2 Requirements .................................................81.3 Terminology ..................................................81.4 Overall Operation ...........................................122 Notational Conventions and Generic Grammar ....................142.1 Augmented BNF ...............................................142.2 Basic Rules .................................................153 Protocol Parameters ...........................................173.1 HTTP Version ................................................173.2 Uniform Resource Identifiers ................................183.2.1 General Syntax ...........................................193.2.2 http URL .................................................193.2.3 URI Comparison ...........................................203.3 Date/Time Formats ...........................................203.3.1 Full Date ................................................203.3.2 Delta Seconds ............................................213.4 Character Sets ..............................................213.4.1 Missing Charset ..........................................223.5 Content Codings .............................................233.6 Transfer Codings ............................................243.6.1 Chunked Transfer Coding ..................................253.7 Media Types .................................................263.7.1 Canonicalization and Text Defaults .......................273.7.2 Multipart Types ..........................................273.8 Product Tokens ..............................................283.9 Quality Values ..............................................293.10 Language Tags ...............................................293.11 Entity Tags .................................................303.12 Range Units .................................................304 HTTP Message ..................................................314.1 Message Types ...............................................314.2 Message Headers .............................................314.3 Message Body ................................................324.4 Message Length ..............................................334.5 General Header Fields .......................................345 Request .......................................................35
Page 4 and 5: 10.2.2 201 Created ................
Page 6 and 7: 14.6 Age ..........................
Page 8 and 9: 21 Full Copyright Statement .......
Page 10: esolutions) or vary in other ways.e
Page 13 and 14: messages flow from upstream to down
Page 15 and 16: needs of those who build web applic
Page 17 and 18: A semi-colon, set off some distance
Page 19 and 20: value.comment = "(" *( ctext | quot
Page 21 and 22: with a scheme name followed by a co
Page 23 and 24: Fielding, et al. Standards Track [P
Page 25 and 26: Unfortunately, some older HTTP/1.0
Page 27 and 28: the Transfer-Encoding header field
Page 29 and 30: An example process for decoding a C
Page 31 and 32: any other media type: strictly as p
Page 33 and 34: and any two-letter initial subtag i
Page 35 and 36: there might exist some implementati
Page 37 and 38: the message.2.If a Transfer-Encodin
Page 39 and 40: | request-header ; Section 5.3| ent
Page 41 and 42: the Request-URI, and the network lo
Page 43 and 44: | Referer ; Section 14.36| TE ; Sec
Page 45 and 46: RFC 2616 HTTP/1.1 June 1999| "407"
Page 47 and 48: The extension-header mechanism allo
Page 49 and 50: - Latency on subsequent requests is
Page 51 and 52: It is especially important that pro
Page 53 and 54:
The purpose of the 100 (Continue) s
Page 55 and 56:
- Proxies SHOULD maintain a cache r
Page 57 and 58:
Fielding, et al. Standards Track [P
Page 59 and 60:
completed without transferring data
Page 61 and 62:
error response SHOULD be given that
Page 63 and 64:
proxy that can dynamically switch t
Page 65 and 66:
SHOULD include an entity containing
Page 67 and 68:
- Expires, Cache-Control, and/or Va
Page 69 and 70:
Page 71 and 72:
observing these limitations has sig
Page 73 and 74:
public why the request has not been
Page 75 and 76:
The requested resource is no longer
Page 77 and 78:
y the next-hop server.10.5 Server E
Page 79 and 80:
Page 81 and 82:
automatic selection, though it also
Page 83 and 84:
careful and complete analysis shows
Page 85 and 86:
used.Multiple warnings MAY be attac
Page 87 and 88:
esponse without validating it. Clie
Page 89 and 90:
with every response, giving the tim
Page 91 and 92:
Page 93 and 94:
unconditionally, and includeCache-C
Page 95 and 96:
decide if they represent the same o
Page 97 and 98:
- The validator is being compared b
Page 99 and 100:
cache-conditional requests. This al
Page 101 and 102:
RFC 2616 HTTP/1.1 June 199913.5 Con
Page 103 and 104:
according to the rules in section 4
Page 105 and 106:
equest-header fields were used to s
Page 107 and 108:
13.9 Side Effects of GET and HEADUn
Page 109 and 110:
13.13 History ListsUser agents ofte
Page 111 and 112:
SHOULD be interpreted as "I prefer
Page 113 and 114:
Page 115 and 116:
use of prefix tags if this is the c
Page 117 and 118:
Allow = "Allow" ":" #MethodExample
Page 119 and 120:
Cache-Control = "Cache-Control" ":"
Page 121 and 122:
If the no-cache directive does not
Page 123 and 124:
s-maxageIf a response includes an s
Page 125 and 126:
evalidate its own entry, if any, wi
Page 127 and 128:
14.9.5 No-Transform Directiveno-tra
Page 129 and 130:
Message headers listed in the Conne
Page 131 and 132:
Waitangi," presented simultaneously
Page 133 and 134:
MIC is good for detecting accidenta
Page 135 and 136:
Page 137 and 138:
An example isDate: Tue, 15 Nov 1994
Page 139 and 140:
with appropriate error status. The
Page 141 and 142:
From: webmaster@w3.orgThis header f
Page 143 and 144:
as PUT, from modifying a resource t
Page 145 and 146:
Since date is derived from the clie
Page 147 and 148:
Page 149 and 150:
An example is:Location: http://www.
Page 151 and 152:
the current connection and SHOULD N
Page 153 and 154:
containing the satisfiable ranges o
Page 155 and 156:
Unavailable) response to indicate h
Page 157 and 158:
RFC 2616 HTTP/1.1 June 19993. If mu
Page 159 and 160:
The Upgrade header field only appli
Page 161 and 162:
Via = "Via" ":" 1#( received-protoc
Page 163 and 164:
; the name or pseudonym of the serv
Page 165 and 166:
whose version is HTTP/1.0 or lower,
Page 167 and 168:
The information sent in the From fi
Page 169 and 170:
Page 171 and 172:
they would protect any system that
Page 173 and 174:
suggestions and comments from indiv
Page 175 and 176:
[19] Reynolds, J. and J. Postel, "A
Page 177 and 178:
Extensions (MIME) Part Two: Media T
Page 179 and 180:
Paul J. LeachMicrosoft Corporation1
Page 181 and 182:
Page 183 and 184:
- HTTP/1.1 clients and caches SHOUL
Page 185 and 186:
19.4.4 Introduction of Content-Enco
Page 187 and 188:
disposition-type *( ";" disposition
Page 189 and 190:
- A client that sends an HTTP/1.1 r
Page 191 and 192:
Page 193 and 194:
show all

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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?