Changeset 205 for draft-ietf-httpbis
- Timestamp:
- 06/02/08 19:15:29 (14 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 14 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/outlineALL.html
r193 r205 1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en-US">1 <!DOCTYPE html 2 PUBLIC "-//W3C//DTD HTML 4.01//EN"> 3 <html> 4 4 <head> 5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> 5 6 <title>HTTP/1.1 Drafts: Combined Table of Contents</title> 6 <meta http-equiv="content-type" content="application/xhtml+xml; charset=utf-8" /> 7 <link type="text/css" href="http://www3.tools.ietf.org/wg/httpbis/trac/chrome/common/css/trac.css" rel="stylesheet"/> 8 <link type="image/x-icon" href="http://www3.tools.ietf.org/ietf.ico" rel="icon"/> 9 <link type="image/x-icon" href="http://www3.tools.ietf.org/ietf.ico" rel="shortcut icon"/> 10 <style type="text/css" title="xml2rfc TOC"> 7 <link type="text/css" href="http://www3.tools.ietf.org/wg/httpbis/trac/chrome/common/css/trac.css" rel="stylesheet"> 8 <link type="image/x-icon" href="http://www.tools.ietf.org/ietf.ico" rel="icon"> 9 <link type="image/x-icon" href="http://www.tools.ietf.org/ietf.ico" rel="shortcut icon"><style type="text/css" title="xml2rfc TOC"> 11 10 ul.toc { 12 11 list-style: none; … … 35 34 } 36 35 #content { padding-top: 2em; position: relative } 37 </style> 38 </head> 36 </style></head> 39 37 <body> 40 <div id="page"> 41 <div id="banner"> 42 <div id="mainnav" class="nav"> 43 <ul><li class="first"><a accesskey="1" href="http://www3.tools.ietf.org/wg/httpbis/trac/wiki">Wiki</a></li> 44 <li><a accesskey="2" href="http://www3.tools.ietf.org/wg/httpbis/trac/timeline">Timeline</a></li> 45 <li><a href="http://www3.tools.ietf.org/wg/httpbis/trac/browser">Browse Source</a></li> 46 <li><a href="http://www3.tools.ietf.org/wg/httpbis/trac/report">View Tickets</a></li> 47 <li class="active"><a href="outlineALL.html">Outline Parts</a></li> 48 <li><a href="outline2616.html">Outline 2616</a></li> 49 <li class="last"><a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">Mail Archive</a></li> 50 </ul> 38 <div id="page"> 39 <div id="banner"> 40 <div id="mainnav" class="nav"> 41 <ul> 42 <li class="first"><a accesskey="1" href="http://www3.tools.ietf.org/wg/httpbis/trac/wiki">Wiki</a></li> 43 <li><a accesskey="2" href="http://www3.tools.ietf.org/wg/httpbis/trac/timeline">Timeline</a></li> 44 <li><a href="http://www3.tools.ietf.org/wg/httpbis/trac/browser">Browse Source</a></li> 45 <li><a href="http://www3.tools.ietf.org/wg/httpbis/trac/report">View Tickets</a></li> 46 <li class="active"><a href="outlineALL.html">Outline Parts</a></li> 47 <li><a href="outline2616.html">Outline 2616</a></li> 48 <li class="last"><a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">Mail Archive</a></li> 49 </ul> 50 </div> 51 </div> 52 <div id="content"> 53 <h1>HTTP/1.1 Drafts: Combined Table of Contents</h1> 54 <h2><a href="p1-messaging.html">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a></h2> 55 <ul class="toc"> 56 <li class="tocline0">1. <a href="p1-messaging.html#introduction">Introduction</a><ul class="toc"> 57 <li class="tocline1">1.1 <a href="p1-messaging.html#intro.purpose">Purpose</a></li> 58 <li class="tocline1">1.2 <a href="p1-messaging.html#intro.requirements">Requirements</a></li> 59 <li class="tocline1">1.3 <a href="p1-messaging.html#intro.terminology">Terminology</a></li> 60 <li class="tocline1">1.4 <a href="p1-messaging.html#intro.overall.operation">Overall Operation</a></li> 61 </ul> 62 </li> 63 <li class="tocline0">2. <a href="p1-messaging.html#notation">Notational Conventions and Generic Grammar</a><ul class="toc"> 64 <li class="tocline1">2.1 <a href="p1-messaging.html#notation.abnf">Augmented BNF</a></li> 65 <li class="tocline1">2.2 <a href="p1-messaging.html#basic.rules">Basic Rules</a></li> 66 </ul> 67 </li> 68 <li class="tocline0">3. <a href="p1-messaging.html#protocol.parameters">Protocol Parameters</a><ul class="toc"> 69 <li class="tocline1">3.1 <a href="p1-messaging.html#http.version">HTTP Version</a></li> 70 <li class="tocline1">3.2 <a href="p1-messaging.html#uri">Uniform Resource Identifiers</a><ul class="toc"> 71 <li class="tocline1">3.2.1 <a href="p1-messaging.html#general.syntax">General Syntax</a></li> 72 <li class="tocline1">3.2.2 <a href="p1-messaging.html#http.url">http URL</a></li> 73 <li class="tocline1">3.2.3 <a href="p1-messaging.html#uri.comparison">URI Comparison</a></li> 74 </ul> 75 </li> 76 <li class="tocline1">3.3 <a href="p1-messaging.html#date.time.formats">Date/Time Formats</a><ul class="toc"> 77 <li class="tocline1">3.3.1 <a href="p1-messaging.html#full.date">Full Date</a></li> 78 </ul> 79 </li> 80 <li class="tocline1">3.4 <a href="p1-messaging.html#transfer.codings">Transfer Codings</a><ul class="toc"> 81 <li class="tocline1">3.4.1 <a href="p1-messaging.html#chunked.transfer.encoding">Chunked Transfer Coding</a></li> 82 </ul> 83 </li> 84 <li class="tocline1">3.5 <a href="p1-messaging.html#product.tokens">Product Tokens</a></li> 85 </ul> 86 </li> 87 <li class="tocline0">4. <a href="p1-messaging.html#http.message">HTTP Message</a><ul class="toc"> 88 <li class="tocline1">4.1 <a href="p1-messaging.html#message.types">Message Types</a></li> 89 <li class="tocline1">4.2 <a href="p1-messaging.html#message.headers">Message Headers</a></li> 90 <li class="tocline1">4.3 <a href="p1-messaging.html#message.body">Message Body</a></li> 91 <li class="tocline1">4.4 <a href="p1-messaging.html#message.length">Message Length</a></li> 92 <li class="tocline1">4.5 <a href="p1-messaging.html#general.header.fields">General Header Fields</a></li> 93 </ul> 94 </li> 95 <li class="tocline0">5. <a href="p1-messaging.html#request">Request</a><ul class="toc"> 96 <li class="tocline1">5.1 <a href="p1-messaging.html#request-line">Request-Line</a><ul class="toc"> 97 <li class="tocline1">5.1.1 <a href="p1-messaging.html#method">Method</a></li> 98 <li class="tocline1">5.1.2 <a href="p1-messaging.html#request-uri">Request-URI</a></li> 99 </ul> 100 </li> 101 <li class="tocline1">5.2 <a href="p1-messaging.html#the.resource.identified.by.a.request">The Resource Identified by a Request</a></li> 102 </ul> 103 </li> 104 <li class="tocline0">6. <a href="p1-messaging.html#response">Response</a><ul class="toc"> 105 <li class="tocline1">6.1 <a href="p1-messaging.html#status-line">Status-Line</a><ul class="toc"> 106 <li class="tocline1">6.1.1 <a href="p1-messaging.html#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li> 107 </ul> 108 </li> 109 </ul> 110 </li> 111 <li class="tocline0">7. <a href="p1-messaging.html#connections">Connections</a><ul class="toc"> 112 <li class="tocline1">7.1 <a href="p1-messaging.html#persistent.connections">Persistent Connections</a><ul class="toc"> 113 <li class="tocline1">7.1.1 <a href="p1-messaging.html#persistent.purpose">Purpose</a></li> 114 <li class="tocline1">7.1.2 <a href="p1-messaging.html#persistent.overall">Overall Operation</a><ul class="toc"> 115 <li class="tocline1">7.1.2.1 <a href="p1-messaging.html#persistent.negotiation">Negotiation</a></li> 116 <li class="tocline1">7.1.2.2 <a href="p1-messaging.html#pipelining">Pipelining</a></li> 117 </ul> 118 </li> 119 <li class="tocline1">7.1.3 <a href="p1-messaging.html#persistent.proxy">Proxy Servers</a></li> 120 <li class="tocline1">7.1.4 <a href="p1-messaging.html#persistent.practical">Practical Considerations</a></li> 121 </ul> 122 </li> 123 <li class="tocline1">7.2 <a href="p1-messaging.html#message.transmission.requirements">Message Transmission Requirements</a><ul class="toc"> 124 <li class="tocline1">7.2.1 <a href="p1-messaging.html#persistent.flow">Persistent Connections and Flow Control</a></li> 125 <li class="tocline1">7.2.2 <a href="p1-messaging.html#persistent.monitor">Monitoring Connections for Error Status Messages</a></li> 126 <li class="tocline1">7.2.3 <a href="p1-messaging.html#use.of.the.100.status">Use of the 100 (Continue) Status</a></li> 127 <li class="tocline1">7.2.4 <a href="p1-messaging.html#connection.premature">Client Behavior if Server Prematurely Closes Connection</a></li> 128 </ul> 129 </li> 130 </ul> 131 </li> 132 <li class="tocline0">8. <a href="p1-messaging.html#header.fields">Header Field Definitions</a><ul class="toc"> 133 <li class="tocline1">8.1 <a href="p1-messaging.html#header.connection">Connection</a></li> 134 <li class="tocline1">8.2 <a href="p1-messaging.html#header.content-length">Content-Length</a></li> 135 <li class="tocline1">8.3 <a href="p1-messaging.html#header.date">Date</a><ul class="toc"> 136 <li class="tocline1">8.3.1 <a href="p1-messaging.html#clockless.origin.server.operation">Clockless Origin Server Operation</a></li> 137 </ul> 138 </li> 139 <li class="tocline1">8.4 <a href="p1-messaging.html#header.host">Host</a></li> 140 <li class="tocline1">8.5 <a href="p1-messaging.html#header.te">TE</a></li> 141 <li class="tocline1">8.6 <a href="p1-messaging.html#header.trailer">Trailer</a></li> 142 <li class="tocline1">8.7 <a href="p1-messaging.html#header.transfer-encoding">Transfer-Encoding</a></li> 143 <li class="tocline1">8.8 <a href="p1-messaging.html#header.upgrade">Upgrade</a></li> 144 <li class="tocline1">8.9 <a href="p1-messaging.html#header.via">Via</a></li> 145 </ul> 146 </li> 147 <li class="tocline0">9. <a href="p1-messaging.html#IANA.considerations">IANA Considerations</a></li> 148 <li class="tocline0">10. <a href="p1-messaging.html#security.considerations">Security Considerations</a><ul class="toc"> 149 <li class="tocline1">10.1 <a href="p1-messaging.html#personal.information">Personal Information</a></li> 150 <li class="tocline1">10.2 <a href="p1-messaging.html#abuse.of.server.log.information">Abuse of Server Log Information</a></li> 151 <li class="tocline1">10.3 <a href="p1-messaging.html#attack.pathname">Attacks Based On File and Path Names</a></li> 152 <li class="tocline1">10.4 <a href="p1-messaging.html#dns.spoofing">DNS Spoofing</a></li> 153 <li class="tocline1">10.5 <a href="p1-messaging.html#attack.proxies">Proxies and Caching</a></li> 154 <li class="tocline1">10.6 <a href="p1-messaging.html#attack.DoS">Denial of Service Attacks on Proxies</a></li> 155 </ul> 156 </li> 157 <li class="tocline0">11. <a href="p1-messaging.html#ack">Acknowledgments</a></li> 158 <li class="tocline0">12. <a href="p1-messaging.html#rfc.references">References</a><ul class="toc"> 159 <li class="tocline1">12.1 <a href="p1-messaging.html#rfc.references.1">Normative References</a></li> 160 <li class="tocline1">12.2 <a href="p1-messaging.html#rfc.references.2">Informative References</a></li> 161 </ul> 162 </li> 163 <li class="tocline0"><a href="p1-messaging.html#rfc.authors">Authors' Addresses</a></li> 164 <li class="tocline0">A. <a href="p1-messaging.html#internet.media.type.http">Internet Media Types</a><ul class="toc"> 165 <li class="tocline1">A.1 <a href="p1-messaging.html#internet.media.type.message.http">Internet Media Type message/http</a></li> 166 <li class="tocline1">A.2 <a href="p1-messaging.html#internet.media.type.application.http">Internet Media Type application/http</a></li> 167 </ul> 168 </li> 169 <li class="tocline0">B. <a href="p1-messaging.html#tolerant.applications">Tolerant Applications</a></li> 170 <li class="tocline0">C. <a href="p1-messaging.html#conversion.of.date.formats">Conversion of Date Formats</a></li> 171 <li class="tocline0">D. <a href="p1-messaging.html#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 172 <li class="tocline1">D.1 <a href="p1-messaging.html#changes.from.1.0">Changes from HTTP/1.0</a><ul class="toc"> 173 <li class="tocline1">D.1.1 <a href="p1-messaging.html#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses">Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses</a></li> 174 </ul> 175 </li> 176 <li class="tocline1">D.2 <a href="p1-messaging.html#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li> 177 <li class="tocline1">D.3 <a href="p1-messaging.html#changes.from.rfc.2068">Changes from RFC 2068</a></li> 178 <li class="tocline1">D.4 <a href="p1-messaging.html#changes.from.rfc.2616">Changes from RFC 2616</a></li> 179 </ul> 180 </li> 181 <li class="tocline0">E. <a href="p1-messaging.html#rfc.section.E">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> 182 <li class="tocline1">E.1 <a href="p1-messaging.html#rfc.section.E.1">Since RFC2616</a></li> 183 <li class="tocline1">E.2 <a href="p1-messaging.html#rfc.section.E.2">Since draft-ietf-httpbis-p1-messaging-00</a></li> 184 <li class="tocline1">E.3 <a href="p1-messaging.html#rfc.section.E.3">Since draft-ietf-httpbis-p1-messaging-01</a></li> 185 </ul> 186 </li> 187 <li class="tocline0"><a href="p1-messaging.html#rfc.ipr">Intellectual Property and Copyright Statements</a></li> 188 <li class="tocline0"><a href="p1-messaging.html#rfc.index">Index</a></li> 189 </ul> 190 <h2><a href="p2-semantics.html">HTTP/1.1, part 2: Message Semantics</a></h2> 191 <ul class="toc"> 192 <li class="tocline0">1. <a href="p2-semantics.html#introduction">Introduction</a><ul class="toc"> 193 <li class="tocline1">1.1 <a href="p2-semantics.html#intro.requirements">Requirements</a></li> 194 </ul> 195 </li> 196 <li class="tocline0">2. <a href="p2-semantics.html#notation">Notational Conventions and Generic Grammar</a></li> 197 <li class="tocline0">3. <a href="p2-semantics.html#method">Method</a></li> 198 <li class="tocline0">4. <a href="p2-semantics.html#request.header.fields">Request Header Fields</a></li> 199 <li class="tocline0">5. <a href="p2-semantics.html#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li> 200 <li class="tocline0">6. <a href="p2-semantics.html#response.header.fields">Response Header Fields</a></li> 201 <li class="tocline0">7. <a href="p2-semantics.html#entity">Entity</a></li> 202 <li class="tocline0">8. <a href="p2-semantics.html#method.definitions">Method Definitions</a><ul class="toc"> 203 <li class="tocline1">8.1 <a href="p2-semantics.html#safe.and.idempotent">Safe and Idempotent Methods</a><ul class="toc"> 204 <li class="tocline1">8.1.1 <a href="p2-semantics.html#safe.methods">Safe Methods</a></li> 205 <li class="tocline1">8.1.2 <a href="p2-semantics.html#idempotent.methods">Idempotent Methods</a></li> 206 </ul> 207 </li> 208 <li class="tocline1">8.2 <a href="p2-semantics.html#OPTIONS">OPTIONS</a></li> 209 <li class="tocline1">8.3 <a href="p2-semantics.html#GET">GET</a></li> 210 <li class="tocline1">8.4 <a href="p2-semantics.html#HEAD">HEAD</a></li> 211 <li class="tocline1">8.5 <a href="p2-semantics.html#POST">POST</a></li> 212 <li class="tocline1">8.6 <a href="p2-semantics.html#PUT">PUT</a></li> 213 <li class="tocline1">8.7 <a href="p2-semantics.html#DELETE">DELETE</a></li> 214 <li class="tocline1">8.8 <a href="p2-semantics.html#TRACE">TRACE</a></li> 215 <li class="tocline1">8.9 <a href="p2-semantics.html#CONNECT">CONNECT</a></li> 216 </ul> 217 </li> 218 <li class="tocline0">9. <a href="p2-semantics.html#status.codes">Status Code Definitions</a><ul class="toc"> 219 <li class="tocline1">9.1 <a href="p2-semantics.html#status.1xx">Informational 1xx</a><ul class="toc"> 220 <li class="tocline1">9.1.1 <a href="p2-semantics.html#status.100">100 Continue</a></li> 221 <li class="tocline1">9.1.2 <a href="p2-semantics.html#status.101">101 Switching Protocols</a></li> 222 </ul> 223 </li> 224 <li class="tocline1">9.2 <a href="p2-semantics.html#status.2xx">Successful 2xx</a><ul class="toc"> 225 <li class="tocline1">9.2.1 <a href="p2-semantics.html#status.200">200 OK</a></li> 226 <li class="tocline1">9.2.2 <a href="p2-semantics.html#status.201">201 Created</a></li> 227 <li class="tocline1">9.2.3 <a href="p2-semantics.html#status.202">202 Accepted</a></li> 228 <li class="tocline1">9.2.4 <a href="p2-semantics.html#status.203">203 Non-Authoritative Information</a></li> 229 <li class="tocline1">9.2.5 <a href="p2-semantics.html#status.204">204 No Content</a></li> 230 <li class="tocline1">9.2.6 <a href="p2-semantics.html#status.205">205 Reset Content</a></li> 231 <li class="tocline1">9.2.7 <a href="p2-semantics.html#status.206">206 Partial Content</a></li> 232 </ul> 233 </li> 234 <li class="tocline1">9.3 <a href="p2-semantics.html#status.3xx">Redirection 3xx</a><ul class="toc"> 235 <li class="tocline1">9.3.1 <a href="p2-semantics.html#status.300">300 Multiple Choices</a></li> 236 <li class="tocline1">9.3.2 <a href="p2-semantics.html#status.301">301 Moved Permanently</a></li> 237 <li class="tocline1">9.3.3 <a href="p2-semantics.html#status.302">302 Found</a></li> 238 <li class="tocline1">9.3.4 <a href="p2-semantics.html#status.303">303 See Other</a></li> 239 <li class="tocline1">9.3.5 <a href="p2-semantics.html#status.304">304 Not Modified</a></li> 240 <li class="tocline1">9.3.6 <a href="p2-semantics.html#status.305">305 Use Proxy</a></li> 241 <li class="tocline1">9.3.7 <a href="p2-semantics.html#status.306">306 (Unused)</a></li> 242 <li class="tocline1">9.3.8 <a href="p2-semantics.html#status.307">307 Temporary Redirect</a></li> 243 </ul> 244 </li> 245 <li class="tocline1">9.4 <a href="p2-semantics.html#status.4xx">Client Error 4xx</a><ul class="toc"> 246 <li class="tocline1">9.4.1 <a href="p2-semantics.html#status.400">400 Bad Request</a></li> 247 <li class="tocline1">9.4.2 <a href="p2-semantics.html#status.401">401 Unauthorized</a></li> 248 <li class="tocline1">9.4.3 <a href="p2-semantics.html#status.402">402 Payment Required</a></li> 249 <li class="tocline1">9.4.4 <a href="p2-semantics.html#status.403">403 Forbidden</a></li> 250 <li class="tocline1">9.4.5 <a href="p2-semantics.html#status.404">404 Not Found</a></li> 251 <li class="tocline1">9.4.6 <a href="p2-semantics.html#status.405">405 Method Not Allowed</a></li> 252 <li class="tocline1">9.4.7 <a href="p2-semantics.html#status.406">406 Not Acceptable</a></li> 253 <li class="tocline1">9.4.8 <a href="p2-semantics.html#status.407">407 Proxy Authentication Required</a></li> 254 <li class="tocline1">9.4.9 <a href="p2-semantics.html#status.408">408 Request Timeout</a></li> 255 <li class="tocline1">9.4.10 <a href="p2-semantics.html#status.409">409 Conflict</a></li> 256 <li class="tocline1">9.4.11 <a href="p2-semantics.html#status.410">410 Gone</a></li> 257 <li class="tocline1">9.4.12 <a href="p2-semantics.html#status.411">411 Length Required</a></li> 258 <li class="tocline1">9.4.13 <a href="p2-semantics.html#status.412">412 Precondition Failed</a></li> 259 <li class="tocline1">9.4.14 <a href="p2-semantics.html#status.413">413 Request Entity Too Large</a></li> 260 <li class="tocline1">9.4.15 <a href="p2-semantics.html#status.414">414 Request-URI Too Long</a></li> 261 <li class="tocline1">9.4.16 <a href="p2-semantics.html#status.415">415 Unsupported Media Type</a></li> 262 <li class="tocline1">9.4.17 <a href="p2-semantics.html#status.416">416 Requested Range Not Satisfiable</a></li> 263 <li class="tocline1">9.4.18 <a href="p2-semantics.html#status.417">417 Expectation Failed</a></li> 264 </ul> 265 </li> 266 <li class="tocline1">9.5 <a href="p2-semantics.html#status.5xx">Server Error 5xx</a><ul class="toc"> 267 <li class="tocline1">9.5.1 <a href="p2-semantics.html#status.500">500 Internal Server Error</a></li> 268 <li class="tocline1">9.5.2 <a href="p2-semantics.html#status.501">501 Not Implemented</a></li> 269 <li class="tocline1">9.5.3 <a href="p2-semantics.html#status.502">502 Bad Gateway</a></li> 270 <li class="tocline1">9.5.4 <a href="p2-semantics.html#status.503">503 Service Unavailable</a></li> 271 <li class="tocline1">9.5.5 <a href="p2-semantics.html#status.504">504 Gateway Timeout</a></li> 272 <li class="tocline1">9.5.6 <a href="p2-semantics.html#status.505">505 HTTP Version Not Supported</a></li> 273 </ul> 274 </li> 275 </ul> 276 </li> 277 <li class="tocline0">10. <a href="p2-semantics.html#header.fields">Header Field Definitions</a><ul class="toc"> 278 <li class="tocline1">10.1 <a href="p2-semantics.html#header.allow">Allow</a></li> 279 <li class="tocline1">10.2 <a href="p2-semantics.html#header.expect">Expect</a></li> 280 <li class="tocline1">10.3 <a href="p2-semantics.html#header.from">From</a></li> 281 <li class="tocline1">10.4 <a href="p2-semantics.html#header.location">Location</a></li> 282 <li class="tocline1">10.5 <a href="p2-semantics.html#header.max-forwards">Max-Forwards</a></li> 283 <li class="tocline1">10.6 <a href="p2-semantics.html#header.referer">Referer</a></li> 284 <li class="tocline1">10.7 <a href="p2-semantics.html#header.retry-after">Retry-After</a></li> 285 <li class="tocline1">10.8 <a href="p2-semantics.html#header.server">Server</a></li> 286 <li class="tocline1">10.9 <a href="p2-semantics.html#header.user-agent">User-Agent</a></li> 287 </ul> 288 </li> 289 <li class="tocline0">11. <a href="p2-semantics.html#IANA.considerations">IANA Considerations</a></li> 290 <li class="tocline0">12. <a href="p2-semantics.html#security.considerations">Security Considerations</a><ul class="toc"> 291 <li class="tocline1">12.1 <a href="p2-semantics.html#security.sensitive">Transfer of Sensitive Information</a></li> 292 <li class="tocline1">12.2 <a href="p2-semantics.html#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li> 293 <li class="tocline1">12.3 <a href="p2-semantics.html#location.spoofing">Location Headers and Spoofing</a></li> 294 </ul> 295 </li> 296 <li class="tocline0">13. <a href="p2-semantics.html#ack">Acknowledgments</a></li> 297 <li class="tocline0">14. <a href="p2-semantics.html#rfc.references">References</a><ul class="toc"> 298 <li class="tocline1">14.1 <a href="p2-semantics.html#rfc.references.1">Normative References</a></li> 299 <li class="tocline1">14.2 <a href="p2-semantics.html#rfc.references.2">Informative References</a></li> 300 </ul> 301 </li> 302 <li class="tocline0"><a href="p2-semantics.html#rfc.authors">Authors' Addresses</a></li> 303 <li class="tocline0">A. <a href="p2-semantics.html#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 304 <li class="tocline1">A.1 <a href="p2-semantics.html#changes.from.rfc.2068">Changes from RFC 2068</a></li> 305 <li class="tocline1">A.2 <a href="p2-semantics.html#changes.from.rfc.2616">Changes from RFC 2616</a></li> 306 </ul> 307 </li> 308 <li class="tocline0">B. <a href="p2-semantics.html#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> 309 <li class="tocline1">B.1 <a href="p2-semantics.html#rfc.section.B.1">Since RFC2616</a></li> 310 <li class="tocline1">B.2 <a href="p2-semantics.html#rfc.section.B.2">Since draft-ietf-httpbis-p2-semantics-00</a></li> 311 <li class="tocline1">B.3 <a href="p2-semantics.html#rfc.section.B.3">Since draft-ietf-httpbis-p2-semantics-01</a></li> 312 </ul> 313 </li> 314 <li class="tocline0"><a href="p2-semantics.html#rfc.ipr">Intellectual Property and Copyright Statements</a></li> 315 <li class="tocline0"><a href="p2-semantics.html#rfc.index">Index</a></li> 316 </ul> 317 <h2><a href="p3-payload.html">HTTP/1.1, part 3: Message Payload and Content Negotiation</a></h2> 318 <ul class="toc"> 319 <li class="tocline0">1. <a href="p3-payload.html#introduction">Introduction</a><ul class="toc"> 320 <li class="tocline1">1.1 <a href="p3-payload.html#intro.requirements">Requirements</a></li> 321 </ul> 322 </li> 323 <li class="tocline0">2. <a href="p3-payload.html#notation">Notational Conventions and Generic Grammar</a></li> 324 <li class="tocline0">3. <a href="p3-payload.html#protocol.parameters">Protocol Parameters</a><ul class="toc"> 325 <li class="tocline1">3.1 <a href="p3-payload.html#character.sets">Character Sets</a><ul class="toc"> 326 <li class="tocline1">3.1.1 <a href="p3-payload.html#missing.charset">Missing Charset</a></li> 327 </ul> 328 </li> 329 <li class="tocline1">3.2 <a href="p3-payload.html#content.codings">Content Codings</a></li> 330 <li class="tocline1">3.3 <a href="p3-payload.html#media.types">Media Types</a><ul class="toc"> 331 <li class="tocline1">3.3.1 <a href="p3-payload.html#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li> 332 <li class="tocline1">3.3.2 <a href="p3-payload.html#multipart.types">Multipart Types</a></li> 333 </ul> 334 </li> 335 <li class="tocline1">3.4 <a href="p3-payload.html#quality.values">Quality Values</a></li> 336 <li class="tocline1">3.5 <a href="p3-payload.html#language.tags">Language Tags</a></li> 337 </ul> 338 </li> 339 <li class="tocline0">4. <a href="p3-payload.html#entity">Entity</a><ul class="toc"> 340 <li class="tocline1">4.1 <a href="p3-payload.html#entity.header.fields">Entity Header Fields</a></li> 341 <li class="tocline1">4.2 <a href="p3-payload.html#entity.body">Entity Body</a><ul class="toc"> 342 <li class="tocline1">4.2.1 <a href="p3-payload.html#type">Type</a></li> 343 <li class="tocline1">4.2.2 <a href="p3-payload.html#entity.length">Entity Length</a></li> 344 </ul> 345 </li> 346 </ul> 347 </li> 348 <li class="tocline0">5. <a href="p3-payload.html#content.negotiation">Content Negotiation</a><ul class="toc"> 349 <li class="tocline1">5.1 <a href="p3-payload.html#server-driven.negotiation">Server-driven Negotiation</a></li> 350 <li class="tocline1">5.2 <a href="p3-payload.html#agent-driven.negotiation">Agent-driven Negotiation</a></li> 351 <li class="tocline1">5.3 <a href="p3-payload.html#transparent.negotiation">Transparent Negotiation</a></li> 352 </ul> 353 </li> 354 <li class="tocline0">6. <a href="p3-payload.html#header.fields">Header Field Definitions</a><ul class="toc"> 355 <li class="tocline1">6.1 <a href="p3-payload.html#header.accept">Accept</a></li> 356 <li class="tocline1">6.2 <a href="p3-payload.html#header.accept-charset">Accept-Charset</a></li> 357 <li class="tocline1">6.3 <a href="p3-payload.html#header.accept-encoding">Accept-Encoding</a></li> 358 <li class="tocline1">6.4 <a href="p3-payload.html#header.accept-language">Accept-Language</a></li> 359 <li class="tocline1">6.5 <a href="p3-payload.html#header.content-encoding">Content-Encoding</a></li> 360 <li class="tocline1">6.6 <a href="p3-payload.html#header.content-language">Content-Language</a></li> 361 <li class="tocline1">6.7 <a href="p3-payload.html#header.content-location">Content-Location</a></li> 362 <li class="tocline1">6.8 <a href="p3-payload.html#header.content-md5">Content-MD5</a></li> 363 <li class="tocline1">6.9 <a href="p3-payload.html#header.content-type">Content-Type</a></li> 364 </ul> 365 </li> 366 <li class="tocline0">7. <a href="p3-payload.html#IANA.considerations">IANA Considerations</a></li> 367 <li class="tocline0">8. <a href="p3-payload.html#security.considerations">Security Considerations</a><ul class="toc"> 368 <li class="tocline1">8.1 <a href="p3-payload.html#privacy.issues.connected.to.accept.headers">Privacy Issues Connected to Accept Headers</a></li> 369 <li class="tocline1">8.2 <a href="p3-payload.html#content-disposition.issues">Content-Disposition Issues</a></li> 370 </ul> 371 </li> 372 <li class="tocline0">9. <a href="p3-payload.html#ack">Acknowledgments</a></li> 373 <li class="tocline0">10. <a href="p3-payload.html#rfc.references">References</a><ul class="toc"> 374 <li class="tocline1">10.1 <a href="p3-payload.html#rfc.references.1">Normative References</a></li> 375 <li class="tocline1">10.2 <a href="p3-payload.html#rfc.references.2">Informative References</a></li> 376 </ul> 377 </li> 378 <li class="tocline0"><a href="p3-payload.html#rfc.authors">Authors' Addresses</a></li> 379 <li class="tocline0">A. <a href="p3-payload.html#differences.between.http.entities.and.rfc.2045.entities">Differences Between HTTP Entities and RFC 2045 Entities</a><ul class="toc"> 380 <li class="tocline1">A.1 <a href="p3-payload.html#mime-version">MIME-Version</a></li> 381 <li class="tocline1">A.2 <a href="p3-payload.html#conversion.to.canonical.form">Conversion to Canonical Form</a></li> 382 <li class="tocline1">A.3 <a href="p3-payload.html#introduction.of.content-encoding">Introduction of Content-Encoding</a></li> 383 <li class="tocline1">A.4 <a href="p3-payload.html#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li> 384 <li class="tocline1">A.5 <a href="p3-payload.html#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li> 385 <li class="tocline1">A.6 <a href="p3-payload.html#mhtml.line.length">MHTML and Line Length Limitations</a></li> 386 </ul> 387 </li> 388 <li class="tocline0">B. <a href="p3-payload.html#additional.features">Additional Features</a><ul class="toc"> 389 <li class="tocline1">B.1 <a href="p3-payload.html#content-disposition">Content-Disposition</a></li> 390 </ul> 391 </li> 392 <li class="tocline0">C. <a href="p3-payload.html#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 393 <li class="tocline1">C.1 <a href="p3-payload.html#changes.from.rfc.2068">Changes from RFC 2068</a></li> 394 <li class="tocline1">C.2 <a href="p3-payload.html#changes.from.rfc.2616">Changes from RFC 2616</a></li> 395 </ul> 396 </li> 397 <li class="tocline0">D. <a href="p3-payload.html#rfc.section.D">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> 398 <li class="tocline1">D.1 <a href="p3-payload.html#rfc.section.D.1">Since RFC2616</a></li> 399 <li class="tocline1">D.2 <a href="p3-payload.html#rfc.section.D.2">Since draft-ietf-httpbis-p3-payload-00</a></li> 400 <li class="tocline1">D.3 <a href="p3-payload.html#rfc.section.D.3">Since draft-ietf-httpbis-p3-payload-01</a></li> 401 </ul> 402 </li> 403 <li class="tocline0"><a href="p3-payload.html#rfc.ipr">Intellectual Property and Copyright Statements</a></li> 404 <li class="tocline0"><a href="p3-payload.html#rfc.index">Index</a></li> 405 </ul> 406 <h2><a href="p4-conditional.html">HTTP/1.1, part 4: Conditional Requests</a></h2> 407 <ul class="toc"> 408 <li class="tocline0">1. <a href="p4-conditional.html#introduction">Introduction</a><ul class="toc"> 409 <li class="tocline1">1.1 <a href="p4-conditional.html#intro.requirements">Requirements</a></li> 410 </ul> 411 </li> 412 <li class="tocline0">2. <a href="p4-conditional.html#notation">Notational Conventions and Generic Grammar</a></li> 413 <li class="tocline0">3. <a href="p4-conditional.html#entity.tags">Entity Tags</a></li> 414 <li class="tocline0">4. <a href="p4-conditional.html#rfc.section.4">Status Code Definitions</a><ul class="toc"> 415 <li class="tocline1">4.1 <a href="p4-conditional.html#status.304">304 Not Modified</a></li> 416 <li class="tocline1">4.2 <a href="p4-conditional.html#status.412">412 Precondition Failed</a></li> 417 </ul> 418 </li> 419 <li class="tocline0">5. <a href="p4-conditional.html#weak.and.strong.validators">Weak and Strong Validators</a></li> 420 <li class="tocline0">6. <a href="p4-conditional.html#rules.for.when.to.use.entity.tags.and.last-modified.dates">Rules for When to Use Entity Tags and Last-Modified Dates</a></li> 421 <li class="tocline0">7. <a href="p4-conditional.html#header.fields">Header Field Definitions</a><ul class="toc"> 422 <li class="tocline1">7.1 <a href="p4-conditional.html#header.etag">ETag</a></li> 423 <li class="tocline1">7.2 <a href="p4-conditional.html#header.if-match">If-Match</a></li> 424 <li class="tocline1">7.3 <a href="p4-conditional.html#header.if-modified-since">If-Modified-Since</a></li> 425 <li class="tocline1">7.4 <a href="p4-conditional.html#header.if-none-match">If-None-Match</a></li> 426 <li class="tocline1">7.5 <a href="p4-conditional.html#header.if-unmodified-since">If-Unmodified-Since</a></li> 427 <li class="tocline1">7.6 <a href="p4-conditional.html#header.last-modified">Last-Modified</a></li> 428 </ul> 429 </li> 430 <li class="tocline0">8. <a href="p4-conditional.html#IANA.considerations">IANA Considerations</a></li> 431 <li class="tocline0">9. <a href="p4-conditional.html#security.considerations">Security Considerations</a></li> 432 <li class="tocline0">10. <a href="p4-conditional.html#ack">Acknowledgments</a></li> 433 <li class="tocline0">11. <a href="p4-conditional.html#rfc.references">References</a><ul class="toc"> 434 <li class="tocline1">11.1 <a href="p4-conditional.html#rfc.references.1">Normative References</a></li> 435 <li class="tocline1">11.2 <a href="p4-conditional.html#rfc.references.2">Informative References</a></li> 436 </ul> 437 </li> 438 <li class="tocline0"><a href="p4-conditional.html#rfc.authors">Authors' Addresses</a></li> 439 <li class="tocline0">A. <a href="p4-conditional.html#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 440 <li class="tocline1">A.1 <a href="p4-conditional.html#changes.from.rfc.2616">Changes from RFC 2616</a></li> 441 </ul> 442 </li> 443 <li class="tocline0">B. <a href="p4-conditional.html#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> 444 <li class="tocline1">B.1 <a href="p4-conditional.html#rfc.section.B.1">Since RFC2616</a></li> 445 <li class="tocline1">B.2 <a href="p4-conditional.html#rfc.section.B.2">Since draft-ietf-httpbis-p4-conditional-00</a></li> 446 <li class="tocline1">B.3 <a href="p4-conditional.html#rfc.section.B.3">Since draft-ietf-httpbis-p4-conditional-01</a></li> 447 </ul> 448 </li> 449 <li class="tocline0"><a href="p4-conditional.html#rfc.ipr">Intellectual Property and Copyright Statements</a></li> 450 <li class="tocline0"><a href="p4-conditional.html#rfc.index">Index</a></li> 451 </ul> 452 <h2><a href="p5-range.html">HTTP/1.1, part 5: Range Requests and Partial Responses</a></h2> 453 <ul class="toc"> 454 <li class="tocline0">1. <a href="p5-range.html#introduction">Introduction</a><ul class="toc"> 455 <li class="tocline1">1.1 <a href="p5-range.html#intro.requirements">Requirements</a></li> 456 </ul> 457 </li> 458 <li class="tocline0">2. <a href="p5-range.html#notation">Notational Conventions and Generic Grammar</a></li> 459 <li class="tocline0">3. <a href="p5-range.html#range.units">Range Units</a></li> 460 <li class="tocline0">4. <a href="p5-range.html#rfc.section.4">Status Code Definitions</a><ul class="toc"> 461 <li class="tocline1">4.1 <a href="p5-range.html#status.206">206 Partial Content</a></li> 462 <li class="tocline1">4.2 <a href="p5-range.html#status.416">416 Requested Range Not Satisfiable</a></li> 463 </ul> 464 </li> 465 <li class="tocline0">5. <a href="p5-range.html#combining.byte.ranges">Combining Byte Ranges</a></li> 466 <li class="tocline0">6. <a href="p5-range.html#header.fields">Header Field Definitions</a><ul class="toc"> 467 <li class="tocline1">6.1 <a href="p5-range.html#header.accept-ranges">Accept-Ranges</a></li> 468 <li class="tocline1">6.2 <a href="p5-range.html#header.content-range">Content-Range</a></li> 469 <li class="tocline1">6.3 <a href="p5-range.html#header.if-range">If-Range</a></li> 470 <li class="tocline1">6.4 <a href="p5-range.html#header.range">Range</a><ul class="toc"> 471 <li class="tocline1">6.4.1 <a href="p5-range.html#byte.ranges">Byte Ranges</a></li> 472 <li class="tocline1">6.4.2 <a href="p5-range.html#range.retrieval.requests">Range Retrieval Requests</a></li> 473 </ul> 474 </li> 475 </ul> 476 </li> 477 <li class="tocline0">7. <a href="p5-range.html#IANA.considerations">IANA Considerations</a></li> 478 <li class="tocline0">8. <a href="p5-range.html#security.considerations">Security Considerations</a></li> 479 <li class="tocline0">9. <a href="p5-range.html#ack">Acknowledgments</a></li> 480 <li class="tocline0">10. <a href="p5-range.html#rfc.references">References</a><ul class="toc"> 481 <li class="tocline1">10.1 <a href="p5-range.html#rfc.references.1">Normative References</a></li> 482 <li class="tocline1">10.2 <a href="p5-range.html#rfc.references.2">Informative References</a></li> 483 </ul> 484 </li> 485 <li class="tocline0"><a href="p5-range.html#rfc.authors">Authors' Addresses</a></li> 486 <li class="tocline0">A. <a href="p5-range.html#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li> 487 <li class="tocline0">B. <a href="p5-range.html#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 488 <li class="tocline1">B.1 <a href="p5-range.html#changes.from.rfc.2068">Changes from RFC 2068</a></li> 489 <li class="tocline1">B.2 <a href="p5-range.html#changes.from.rfc.2616">Changes from RFC 2616</a></li> 490 </ul> 491 </li> 492 <li class="tocline0">C. <a href="p5-range.html#rfc.section.C">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> 493 <li class="tocline1">C.1 <a href="p5-range.html#rfc.section.C.1">Since RFC2616</a></li> 494 <li class="tocline1">C.2 <a href="p5-range.html#rfc.section.C.2">Since draft-ietf-httpbis-p5-range-00</a></li> 495 <li class="tocline1">C.3 <a href="p5-range.html#rfc.section.C.3">Since draft-ietf-httpbis-p5-range-01</a></li> 496 </ul> 497 </li> 498 <li class="tocline0"><a href="p5-range.html#rfc.ipr">Intellectual Property and Copyright Statements</a></li> 499 <li class="tocline0"><a href="p5-range.html#rfc.index">Index</a></li> 500 </ul> 501 <h2><a href="p6-cache.html">HTTP/1.1, part 6: Caching</a></h2> 502 <ul class="toc"> 503 <li class="tocline0">1. <a href="p6-cache.html#caching">Introduction</a><ul class="toc"> 504 <li class="tocline1">1.1 <a href="p6-cache.html#intro.purpose">Purpose</a></li> 505 <li class="tocline1">1.2 <a href="p6-cache.html#intro.terminology">Terminology</a></li> 506 <li class="tocline1">1.3 <a href="p6-cache.html#intro.requirements">Requirements</a></li> 507 </ul> 508 </li> 509 <li class="tocline0">2. <a href="p6-cache.html#notation">Notational Conventions and Generic Grammar</a></li> 510 <li class="tocline0">3. <a href="p6-cache.html#caching.overview">Overview</a><ul class="toc"> 511 <li class="tocline1">3.1 <a href="p6-cache.html#cache.correctness">Cache Correctness</a></li> 512 <li class="tocline1">3.2 <a href="p6-cache.html#warnings">Warnings</a></li> 513 <li class="tocline1">3.3 <a href="p6-cache.html#cache-control.mechanisms">Cache-control Mechanisms</a></li> 514 <li class="tocline1">3.4 <a href="p6-cache.html#explicit.ua.warnings">Explicit User Agent Warnings</a></li> 515 <li class="tocline1">3.5 <a href="p6-cache.html#exceptions.to.the.rules.and.warnings">Exceptions to the Rules and Warnings</a></li> 516 <li class="tocline1">3.6 <a href="p6-cache.html#client-controlled.behavior">Client-controlled Behavior</a></li> 517 </ul> 518 </li> 519 <li class="tocline0">4. <a href="p6-cache.html#expiration.model">Expiration Model</a><ul class="toc"> 520 <li class="tocline1">4.1 <a href="p6-cache.html#server-specified.expiration">Server-Specified Expiration</a></li> 521 <li class="tocline1">4.2 <a href="p6-cache.html#heuristic.expiration">Heuristic Expiration</a></li> 522 <li class="tocline1">4.3 <a href="p6-cache.html#age.calculations">Age Calculations</a></li> 523 <li class="tocline1">4.4 <a href="p6-cache.html#expiration.calculations">Expiration Calculations</a></li> 524 <li class="tocline1">4.5 <a href="p6-cache.html#disambiguating.expiration.values">Disambiguating Expiration Values</a></li> 525 <li class="tocline1">4.6 <a href="p6-cache.html#disambiguating.multiple.responses">Disambiguating Multiple Responses</a></li> 526 </ul> 527 </li> 528 <li class="tocline0">5. <a href="p6-cache.html#validation.model">Validation Model</a></li> 529 <li class="tocline0">6. <a href="p6-cache.html#response.cacheability">Response Cacheability</a></li> 530 <li class="tocline0">7. <a href="p6-cache.html#constructing.responses.from.caches">Constructing Responses From Caches</a><ul class="toc"> 531 <li class="tocline1">7.1 <a href="p6-cache.html#end-to-end.and.hop-by-hop.headers">End-to-end and Hop-by-hop Headers</a></li> 532 <li class="tocline1">7.2 <a href="p6-cache.html#non-modifiable.headers">Non-modifiable Headers</a></li> 533 <li class="tocline1">7.3 <a href="p6-cache.html#combining.headers">Combining Headers</a></li> 534 </ul> 535 </li> 536 <li class="tocline0">8. <a href="p6-cache.html#caching.negotiated.responses">Caching Negotiated Responses</a></li> 537 <li class="tocline0">9. <a href="p6-cache.html#shared.and.non-shared.caches">Shared and Non-Shared Caches</a></li> 538 <li class="tocline0">10. <a href="p6-cache.html#errors.or.incomplete.response.cache.behavior">Errors or Incomplete Response Cache Behavior</a></li> 539 <li class="tocline0">11. <a href="p6-cache.html#side.effects.of.get.and.head">Side Effects of GET and HEAD</a></li> 540 <li class="tocline0">12. <a href="p6-cache.html#invalidation.after.updates.or.deletions">Invalidation After Updates or Deletions</a></li> 541 <li class="tocline0">13. <a href="p6-cache.html#write-through.mandatory">Write-Through Mandatory</a></li> 542 <li class="tocline0">14. <a href="p6-cache.html#cache.replacement">Cache Replacement</a></li> 543 <li class="tocline0">15. <a href="p6-cache.html#history.lists">History Lists</a></li> 544 <li class="tocline0">16. <a href="p6-cache.html#header.fields">Header Field Definitions</a><ul class="toc"> 545 <li class="tocline1">16.1 <a href="p6-cache.html#header.age">Age</a></li> 546 <li class="tocline1">16.2 <a href="p6-cache.html#header.cache-control">Cache-Control</a><ul class="toc"> 547 <li class="tocline1">16.2.1 <a href="p6-cache.html#what.is.cacheable">What is Cacheable</a></li> 548 <li class="tocline1">16.2.2 <a href="p6-cache.html#what.may.be.stored.by.caches">What May be Stored by Caches</a></li> 549 <li class="tocline1">16.2.3 <a href="p6-cache.html#modifications.of.the.basic.expiration.mechanism">Modifications of the Basic Expiration Mechanism</a></li> 550 <li class="tocline1">16.2.4 <a href="p6-cache.html#cache.revalidation.and.reload.controls">Cache Revalidation and Reload Controls</a></li> 551 <li class="tocline1">16.2.5 <a href="p6-cache.html#no-transform.directive">No-Transform Directive</a></li> 552 <li class="tocline1">16.2.6 <a href="p6-cache.html#cache.control.extensions">Cache Control Extensions</a></li> 553 </ul> 554 </li> 555 <li class="tocline1">16.3 <a href="p6-cache.html#header.expires">Expires</a></li> 556 <li class="tocline1">16.4 <a href="p6-cache.html#header.pragma">Pragma</a></li> 557 <li class="tocline1">16.5 <a href="p6-cache.html#header.vary">Vary</a></li> 558 <li class="tocline1">16.6 <a href="p6-cache.html#header.warning">Warning</a></li> 559 </ul> 560 </li> 561 <li class="tocline0">17. <a href="p6-cache.html#IANA.considerations">IANA Considerations</a></li> 562 <li class="tocline0">18. <a href="p6-cache.html#security.considerations">Security Considerations</a></li> 563 <li class="tocline0">19. <a href="p6-cache.html#ack">Acknowledgments</a></li> 564 <li class="tocline0">20. <a href="p6-cache.html#rfc.references">References</a><ul class="toc"> 565 <li class="tocline1">20.1 <a href="p6-cache.html#rfc.references.1">Normative References</a></li> 566 <li class="tocline1">20.2 <a href="p6-cache.html#rfc.references.2">Informative References</a></li> 567 </ul> 568 </li> 569 <li class="tocline0"><a href="p6-cache.html#rfc.authors">Authors' Addresses</a></li> 570 <li class="tocline0">A. <a href="p6-cache.html#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 571 <li class="tocline1">A.1 <a href="p6-cache.html#changes.from.rfc.2068">Changes from RFC 2068</a></li> 572 <li class="tocline1">A.2 <a href="p6-cache.html#changes.from.rfc.2616">Changes from RFC 2616</a></li> 573 </ul> 574 </li> 575 <li class="tocline0">B. <a href="p6-cache.html#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> 576 <li class="tocline1">B.1 <a href="p6-cache.html#rfc.section.B.1">Since RFC2616</a></li> 577 <li class="tocline1">B.2 <a href="p6-cache.html#rfc.section.B.2">Since draft-ietf-httpbis-p6-cache-00</a></li> 578 <li class="tocline1">B.3 <a href="p6-cache.html#rfc.section.B.3">Since draft-ietf-httpbis-p6-cache-01</a></li> 579 </ul> 580 </li> 581 <li class="tocline0"><a href="p6-cache.html#rfc.ipr">Intellectual Property and Copyright Statements</a></li> 582 <li class="tocline0"><a href="p6-cache.html#rfc.index">Index</a></li> 583 </ul> 584 <h2><a href="p7-auth.html">HTTP/1.1, part 7: Authentication</a></h2> 585 <ul class="toc"> 586 <li class="tocline0">1. <a href="p7-auth.html#introduction">Introduction</a><ul class="toc"> 587 <li class="tocline1">1.1 <a href="p7-auth.html#intro.requirements">Requirements</a></li> 588 </ul> 589 </li> 590 <li class="tocline0">2. <a href="p7-auth.html#notation">Notational Conventions and Generic Grammar</a></li> 591 <li class="tocline0">3. <a href="p7-auth.html#rfc.section.3">Status Code Definitions</a><ul class="toc"> 592 <li class="tocline1">3.1 <a href="p7-auth.html#status.401">401 Unauthorized</a></li> 593 <li class="tocline1">3.2 <a href="p7-auth.html#status.407">407 Proxy Authentication Required</a></li> 594 </ul> 595 </li> 596 <li class="tocline0">4. <a href="p7-auth.html#header.fields">Header Field Definitions</a><ul class="toc"> 597 <li class="tocline1">4.1 <a href="p7-auth.html#header.authorization">Authorization</a></li> 598 <li class="tocline1">4.2 <a href="p7-auth.html#header.proxy-authenticate">Proxy-Authenticate</a></li> 599 <li class="tocline1">4.3 <a href="p7-auth.html#header.proxy-authorization">Proxy-Authorization</a></li> 600 <li class="tocline1">4.4 <a href="p7-auth.html#header.www-authenticate">WWW-Authenticate</a></li> 601 </ul> 602 </li> 603 <li class="tocline0">5. <a href="p7-auth.html#IANA.considerations">IANA Considerations</a></li> 604 <li class="tocline0">6. <a href="p7-auth.html#security.considerations">Security Considerations</a><ul class="toc"> 605 <li class="tocline1">6.1 <a href="p7-auth.html#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></li> 606 </ul> 607 </li> 608 <li class="tocline0">7. <a href="p7-auth.html#ack">Acknowledgments</a></li> 609 <li class="tocline0">8. <a href="p7-auth.html#rfc.references">References</a><ul class="toc"> 610 <li class="tocline1">8.1 <a href="p7-auth.html#rfc.references.1">Normative References</a></li> 611 <li class="tocline1">8.2 <a href="p7-auth.html#rfc.references.2">Informative References</a></li> 612 </ul> 613 </li> 614 <li class="tocline0"><a href="p7-auth.html#rfc.authors">Authors' Addresses</a></li> 615 <li class="tocline0">A. <a href="p7-auth.html#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 616 <li class="tocline1">A.1 <a href="p7-auth.html#changes.from.rfc.2616">Changes from RFC 2616</a></li> 617 </ul> 618 </li> 619 <li class="tocline0">B. <a href="p7-auth.html#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> 620 <li class="tocline1">B.1 <a href="p7-auth.html#rfc.section.B.1">Since RFC2616</a></li> 621 <li class="tocline1">B.2 <a href="p7-auth.html#rfc.section.B.2">Since draft-ietf-httpbis-p7-auth-00</a></li> 622 <li class="tocline1">B.3 <a href="p7-auth.html#rfc.section.B.3">Since draft-ietf-httpbis-p7-auth-01</a></li> 623 </ul> 624 </li> 625 <li class="tocline0"><a href="p7-auth.html#rfc.ipr">Intellectual Property and Copyright Statements</a></li> 626 <li class="tocline0"><a href="p7-auth.html#rfc.index">Index</a></li> 627 </ul> 628 </div> 51 629 </div> 52 </div>53 <div id="content">54 <h1>HTTP/1.1 Drafts: Combined Table of Contents</h1>55 <!-- ZZZZZZZ -->56 57 <h2><a href="p1-messaging.html">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a></h2>58 <ul class="toc">59 <li class="tocline0">1. <a href="p1-messaging.html#introduction">Introduction</a><ul class="toc">60 <li class="tocline1">1.1 <a href="p1-messaging.html#intro.purpose">Purpose</a></li>61 <li class="tocline1">1.2 <a href="p1-messaging.html#intro.requirements">Requirements</a></li>62 <li class="tocline1">1.3 <a href="p1-messaging.html#intro.terminology">Terminology</a></li>63 <li class="tocline1">1.4 <a href="p1-messaging.html#intro.overall.operation">Overall Operation</a></li>64 </ul>65 </li>66 <li class="tocline0">2. <a href="p1-messaging.html#notation">Notational Conventions and Generic Grammar</a><ul class="toc">67 <li class="tocline1">2.1 <a href="p1-messaging.html#notation.abnf">Augmented BNF</a></li>68 <li class="tocline1">2.2 <a href="p1-messaging.html#basic.rules">Basic Rules</a></li>69 </ul>70 </li>71 <li class="tocline0">3. <a href="p1-messaging.html#protocol.parameters">Protocol Parameters</a><ul class="toc">72 <li class="tocline1">3.1 <a href="p1-messaging.html#http.version">HTTP Version</a></li>73 <li class="tocline1">3.2 <a href="p1-messaging.html#uri">Uniform Resource Identifiers</a><ul class="toc">74 <li class="tocline1">3.2.1 <a href="p1-messaging.html#general.syntax">General Syntax</a></li>75 <li class="tocline1">3.2.2 <a href="p1-messaging.html#http.url">http URL</a></li>76 <li class="tocline1">3.2.3 <a href="p1-messaging.html#uri.comparison">URI Comparison</a></li>77 </ul>78 </li>79 <li class="tocline1">3.3 <a href="p1-messaging.html#date.time.formats">Date/Time Formats</a><ul class="toc">80 <li class="tocline1">3.3.1 <a href="p1-messaging.html#full.date">Full Date</a></li>81 </ul>82 </li>83 <li class="tocline1">3.4 <a href="p1-messaging.html#transfer.codings">Transfer Codings</a><ul class="toc">84 <li class="tocline1">3.4.1 <a href="p1-messaging.html#chunked.transfer.encoding">Chunked Transfer Coding</a></li>85 </ul>86 </li>87 <li class="tocline1">3.5 <a href="p1-messaging.html#product.tokens">Product Tokens</a></li>88 </ul>89 </li>90 <li class="tocline0">4. <a href="p1-messaging.html#http.message">HTTP Message</a><ul class="toc">91 <li class="tocline1">4.1 <a href="p1-messaging.html#message.types">Message Types</a></li>92 <li class="tocline1">4.2 <a href="p1-messaging.html#message.headers">Message Headers</a></li>93 <li class="tocline1">4.3 <a href="p1-messaging.html#message.body">Message Body</a></li>94 <li class="tocline1">4.4 <a href="p1-messaging.html#message.length">Message Length</a></li>95 <li class="tocline1">4.5 <a href="p1-messaging.html#general.header.fields">General Header Fields</a></li>96 </ul>97 </li>98 <li class="tocline0">5. <a href="p1-messaging.html#request">Request</a><ul class="toc">99 <li class="tocline1">5.1 <a href="p1-messaging.html#request-line">Request-Line</a><ul class="toc">100 <li class="tocline1">5.1.1 <a href="p1-messaging.html#method">Method</a></li>101 <li class="tocline1">5.1.2 <a href="p1-messaging.html#request-uri">Request-URI</a></li>102 </ul>103 </li>104 <li class="tocline1">5.2 <a href="p1-messaging.html#the.resource.identified.by.a.request">The Resource Identified by a Request</a></li>105 </ul>106 </li>107 <li class="tocline0">6. <a href="p1-messaging.html#response">Response</a><ul class="toc">108 <li class="tocline1">6.1 <a href="p1-messaging.html#status-line">Status-Line</a><ul class="toc">109 <li class="tocline1">6.1.1 <a href="p1-messaging.html#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li>110 </ul>111 </li>112 </ul>113 </li>114 <li class="tocline0">7. <a href="p1-messaging.html#connections">Connections</a><ul class="toc">115 <li class="tocline1">7.1 <a href="p1-messaging.html#persistent.connections">Persistent Connections</a><ul class="toc">116 <li class="tocline1">7.1.1 <a href="p1-messaging.html#persistent.purpose">Purpose</a></li>117 <li class="tocline1">7.1.2 <a href="p1-messaging.html#persistent.overall">Overall Operation</a><ul class="toc">118 <li class="tocline1">7.1.2.1 <a href="p1-messaging.html#persistent.negotiation">Negotiation</a></li>119 <li class="tocline1">7.1.2.2 <a href="p1-messaging.html#pipelining">Pipelining</a></li>120 </ul>121 </li>122 <li class="tocline1">7.1.3 <a href="p1-messaging.html#persistent.proxy">Proxy Servers</a></li>123 <li class="tocline1">7.1.4 <a href="p1-messaging.html#persistent.practical">Practical Considerations</a></li>124 </ul>125 </li>126 <li class="tocline1">7.2 <a href="p1-messaging.html#message.transmission.requirements">Message Transmission Requirements</a><ul class="toc">127 <li class="tocline1">7.2.1 <a href="p1-messaging.html#persistent.flow">Persistent Connections and Flow Control</a></li>128 <li class="tocline1">7.2.2 <a href="p1-messaging.html#persistent.monitor">Monitoring Connections for Error Status Messages</a></li>129 <li class="tocline1">7.2.3 <a href="p1-messaging.html#use.of.the.100.status">Use of the 100 (Continue) Status</a></li>130 <li class="tocline1">7.2.4 <a href="p1-messaging.html#connection.premature">Client Behavior if Server Prematurely Closes Connection</a></li>131 </ul>132 </li>133 </ul>134 </li>135 <li class="tocline0">8. <a href="p1-messaging.html#header.fields">Header Field Definitions</a><ul class="toc">136 <li class="tocline1">8.1 <a href="p1-messaging.html#header.connection">Connection</a></li>137 <li class="tocline1">8.2 <a href="p1-messaging.html#header.content-length">Content-Length</a></li>138 <li class="tocline1">8.3 <a href="p1-messaging.html#header.date">Date</a><ul class="toc">139 <li class="tocline1">8.3.1 <a href="p1-messaging.html#clockless.origin.server.operation">Clockless Origin Server Operation</a></li>140 </ul>141 </li>142 <li class="tocline1">8.4 <a href="p1-messaging.html#header.host">Host</a></li>143 <li class="tocline1">8.5 <a href="p1-messaging.html#header.te">TE</a></li>144 <li class="tocline1">8.6 <a href="p1-messaging.html#header.trailer">Trailer</a></li>145 <li class="tocline1">8.7 <a href="p1-messaging.html#header.transfer-encoding">Transfer-Encoding</a></li>146 <li class="tocline1">8.8 <a href="p1-messaging.html#header.upgrade">Upgrade</a></li>147 <li class="tocline1">8.9 <a href="p1-messaging.html#header.via">Via</a></li>148 </ul>149 </li>150 <li class="tocline0">9. <a href="p1-messaging.html#IANA.considerations">IANA Considerations</a></li>151 <li class="tocline0">10. <a href="p1-messaging.html#security.considerations">Security Considerations</a><ul class="toc">152 <li class="tocline1">10.1 <a href="p1-messaging.html#personal.information">Personal Information</a></li>153 <li class="tocline1">10.2 <a href="p1-messaging.html#abuse.of.server.log.information">Abuse of Server Log Information</a></li>154 <li class="tocline1">10.3 <a href="p1-messaging.html#attack.pathname">Attacks Based On File and Path Names</a></li>155 <li class="tocline1">10.4 <a href="p1-messaging.html#dns.spoofing">DNS Spoofing</a></li>156 <li class="tocline1">10.5 <a href="p1-messaging.html#attack.proxies">Proxies and Caching</a></li>157 <li class="tocline1">10.6 <a href="p1-messaging.html#attack.DoS">Denial of Service Attacks on Proxies</a></li>158 </ul>159 </li>160 <li class="tocline0">11. <a href="p1-messaging.html#ack">Acknowledgments</a></li>161 <li class="tocline0">12. <a href="p1-messaging.html#rfc.references">References</a><ul class="toc">162 <li class="tocline1">12.1 <a href="p1-messaging.html#rfc.references.1">Normative References</a></li>163 <li class="tocline1">12.2 <a href="p1-messaging.html#rfc.references.2">Informative References</a></li>164 </ul>165 </li>166 <li class="tocline0"><a href="p1-messaging.html#rfc.authors">Authors' Addresses</a></li>167 <li class="tocline0">A. <a href="p1-messaging.html#internet.media.type.http">Internet Media Types</a><ul class="toc">168 <li class="tocline1">A.1 <a href="p1-messaging.html#internet.media.type.message.http">Internet Media Type message/http</a></li>169 <li class="tocline1">A.2 <a href="p1-messaging.html#internet.media.type.application.http">Internet Media Type application/http</a></li>170 </ul>171 </li>172 <li class="tocline0">B. <a href="p1-messaging.html#tolerant.applications">Tolerant Applications</a></li>173 <li class="tocline0">C. <a href="p1-messaging.html#conversion.of.date.formats">Conversion of Date Formats</a></li>174 <li class="tocline0">D. <a href="p1-messaging.html#compatibility">Compatibility with Previous Versions</a><ul class="toc">175 <li class="tocline1">D.1 <a href="p1-messaging.html#changes.from.1.0">Changes from HTTP/1.0</a><ul class="toc">176 <li class="tocline1">D.1.1 <a href="p1-messaging.html#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses">Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses</a></li>177 </ul>178 </li>179 <li class="tocline1">D.2 <a href="p1-messaging.html#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li>180 <li class="tocline1">D.3 <a href="p1-messaging.html#changes.from.rfc.2068">Changes from RFC 2068</a></li>181 <li class="tocline1">D.4 <a href="p1-messaging.html#changes.from.rfc.2616">Changes from RFC 2616</a></li>182 </ul>183 </li>184 <li class="tocline0">E. <a href="p1-messaging.html#rfc.section.E">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">185 <li class="tocline1">E.1 <a href="p1-messaging.html#rfc.section.E.1">Since RFC2616</a></li>186 <li class="tocline1">E.2 <a href="p1-messaging.html#rfc.section.E.2">Since draft-ietf-httpbis-p1-messaging-00</a></li>187 <li class="tocline1">E.3 <a href="p1-messaging.html#rfc.section.E.3">Since draft-ietf-httpbis-p1-messaging-01</a></li>188 </ul>189 </li>190 <li class="tocline0"><a href="p1-messaging.html#rfc.ipr">Intellectual Property and Copyright Statements</a></li>191 <li class="tocline0"><a href="p1-messaging.html#rfc.index">Index</a></li>192 </ul>193 194 <h2><a href="p2-semantics.html">HTTP/1.1, part 2: Message Semantics</a></h2>195 <ul class="toc">196 <li class="tocline0">1. <a href="p2-semantics.html#introduction">Introduction</a><ul class="toc">197 <li class="tocline1">1.1 <a href="p2-semantics.html#intro.requirements">Requirements</a></li>198 </ul>199 </li>200 <li class="tocline0">2. <a href="p2-semantics.html#method">Method</a></li>201 <li class="tocline0">3. <a href="p2-semantics.html#request.header.fields">Request Header Fields</a></li>202 <li class="tocline0">4. <a href="p2-semantics.html#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li>203 <li class="tocline0">5. <a href="p2-semantics.html#response.header.fields">Response Header Fields</a></li>204 <li class="tocline0">6. <a href="p2-semantics.html#entity">Entity</a></li>205 <li class="tocline0">7. <a href="p2-semantics.html#method.definitions">Method Definitions</a><ul class="toc">206 <li class="tocline1">7.1 <a href="p2-semantics.html#safe.and.idempotent">Safe and Idempotent Methods</a><ul class="toc">207 <li class="tocline1">7.1.1 <a href="p2-semantics.html#safe.methods">Safe Methods</a></li>208 <li class="tocline1">7.1.2 <a href="p2-semantics.html#idempotent.methods">Idempotent Methods</a></li>209 </ul>210 </li>211 <li class="tocline1">7.2 <a href="p2-semantics.html#OPTIONS">OPTIONS</a></li>212 <li class="tocline1">7.3 <a href="p2-semantics.html#GET">GET</a></li>213 <li class="tocline1">7.4 <a href="p2-semantics.html#HEAD">HEAD</a></li>214 <li class="tocline1">7.5 <a href="p2-semantics.html#POST">POST</a></li>215 <li class="tocline1">7.6 <a href="p2-semantics.html#PUT">PUT</a></li>216 <li class="tocline1">7.7 <a href="p2-semantics.html#DELETE">DELETE</a></li>217 <li class="tocline1">7.8 <a href="p2-semantics.html#TRACE">TRACE</a></li>218 <li class="tocline1">7.9 <a href="p2-semantics.html#CONNECT">CONNECT</a></li>219 </ul>220 </li>221 <li class="tocline0">8. <a href="p2-semantics.html#status.codes">Status Code Definitions</a><ul class="toc">222 <li class="tocline1">8.1 <a href="p2-semantics.html#status.1xx">Informational 1xx</a><ul class="toc">223 <li class="tocline1">8.1.1 <a href="p2-semantics.html#status.100">100 Continue</a></li>224 <li class="tocline1">8.1.2 <a href="p2-semantics.html#status.101">101 Switching Protocols</a></li>225 </ul>226 </li>227 <li class="tocline1">8.2 <a href="p2-semantics.html#status.2xx">Successful 2xx</a><ul class="toc">228 <li class="tocline1">8.2.1 <a href="p2-semantics.html#status.200">200 OK</a></li>229 <li class="tocline1">8.2.2 <a href="p2-semantics.html#status.201">201 Created</a></li>230 <li class="tocline1">8.2.3 <a href="p2-semantics.html#status.202">202 Accepted</a></li>231 <li class="tocline1">8.2.4 <a href="p2-semantics.html#status.203">203 Non-Authoritative Information</a></li>232 <li class="tocline1">8.2.5 <a href="p2-semantics.html#status.204">204 No Content</a></li>233 <li class="tocline1">8.2.6 <a href="p2-semantics.html#status.205">205 Reset Content</a></li>234 <li class="tocline1">8.2.7 <a href="p2-semantics.html#status.206">206 Partial Content</a></li>235 </ul>236 </li>237 <li class="tocline1">8.3 <a href="p2-semantics.html#status.3xx">Redirection 3xx</a><ul class="toc">238 <li class="tocline1">8.3.1 <a href="p2-semantics.html#status.300">300 Multiple Choices</a></li>239 <li class="tocline1">8.3.2 <a href="p2-semantics.html#status.301">301 Moved Permanently</a></li>240 <li class="tocline1">8.3.3 <a href="p2-semantics.html#status.302">302 Found</a></li>241 <li class="tocline1">8.3.4 <a href="p2-semantics.html#status.303">303 See Other</a></li>242 <li class="tocline1">8.3.5 <a href="p2-semantics.html#status.304">304 Not Modified</a></li>243 <li class="tocline1">8.3.6 <a href="p2-semantics.html#status.305">305 Use Proxy</a></li>244 <li class="tocline1">8.3.7 <a href="p2-semantics.html#status.306">306 (Unused)</a></li>245 <li class="tocline1">8.3.8 <a href="p2-semantics.html#status.307">307 Temporary Redirect</a></li>246 </ul>247 </li>248 <li class="tocline1">8.4 <a href="p2-semantics.html#status.4xx">Client Error 4xx</a><ul class="toc">249 <li class="tocline1">8.4.1 <a href="p2-semantics.html#status.400">400 Bad Request</a></li>250 <li class="tocline1">8.4.2 <a href="p2-semantics.html#status.401">401 Unauthorized</a></li>251 <li class="tocline1">8.4.3 <a href="p2-semantics.html#status.402">402 Payment Required</a></li>252 <li class="tocline1">8.4.4 <a href="p2-semantics.html#status.403">403 Forbidden</a></li>253 <li class="tocline1">8.4.5 <a href="p2-semantics.html#status.404">404 Not Found</a></li>254 <li class="tocline1">8.4.6 <a href="p2-semantics.html#status.405">405 Method Not Allowed</a></li>255 <li class="tocline1">8.4.7 <a href="p2-semantics.html#status.406">406 Not Acceptable</a></li>256 <li class="tocline1">8.4.8 <a href="p2-semantics.html#status.407">407 Proxy Authentication Required</a></li>257 <li class="tocline1">8.4.9 <a href="p2-semantics.html#status.408">408 Request Timeout</a></li>258 <li class="tocline1">8.4.10 <a href="p2-semantics.html#status.409">409 Conflict</a></li>259 <li class="tocline1">8.4.11 <a href="p2-semantics.html#status.410">410 Gone</a></li>260 <li class="tocline1">8.4.12 <a href="p2-semantics.html#status.411">411 Length Required</a></li>261 <li class="tocline1">8.4.13 <a href="p2-semantics.html#status.412">412 Precondition Failed</a></li>262 <li class="tocline1">8.4.14 <a href="p2-semantics.html#status.413">413 Request Entity Too Large</a></li>263 <li class="tocline1">8.4.15 <a href="p2-semantics.html#status.414">414 Request-URI Too Long</a></li>264 <li class="tocline1">8.4.16 <a href="p2-semantics.html#status.415">415 Unsupported Media Type</a></li>265 <li class="tocline1">8.4.17 <a href="p2-semantics.html#status.416">416 Requested Range Not Satisfiable</a></li>266 <li class="tocline1">8.4.18 <a href="p2-semantics.html#status.417">417 Expectation Failed</a></li>267 </ul>268 </li>269 <li class="tocline1">8.5 <a href="p2-semantics.html#status.5xx">Server Error 5xx</a><ul class="toc">270 <li class="tocline1">8.5.1 <a href="p2-semantics.html#status.500">500 Internal Server Error</a></li>271 <li class="tocline1">8.5.2 <a href="p2-semantics.html#status.501">501 Not Implemented</a></li>272 <li class="tocline1">8.5.3 <a href="p2-semantics.html#status.502">502 Bad Gateway</a></li>273 <li class="tocline1">8.5.4 <a href="p2-semantics.html#status.503">503 Service Unavailable</a></li>274 <li class="tocline1">8.5.5 <a href="p2-semantics.html#status.504">504 Gateway Timeout</a></li>275 <li class="tocline1">8.5.6 <a href="p2-semantics.html#status.505">505 HTTP Version Not Supported</a></li>276 </ul>277 </li>278 </ul>279 </li>280 <li class="tocline0">9. <a href="p2-semantics.html#header.fields">Header Field Definitions</a><ul class="toc">281 <li class="tocline1">9.1 <a href="p2-semantics.html#header.allow">Allow</a></li>282 <li class="tocline1">9.2 <a href="p2-semantics.html#header.expect">Expect</a></li>283 <li class="tocline1">9.3 <a href="p2-semantics.html#header.from">From</a></li>284 <li class="tocline1">9.4 <a href="p2-semantics.html#header.location">Location</a></li>285 <li class="tocline1">9.5 <a href="p2-semantics.html#header.max-forwards">Max-Forwards</a></li>286 <li class="tocline1">9.6 <a href="p2-semantics.html#header.referer">Referer</a></li>287 <li class="tocline1">9.7 <a href="p2-semantics.html#header.retry-after">Retry-After</a></li>288 <li class="tocline1">9.8 <a href="p2-semantics.html#header.server">Server</a></li>289 <li class="tocline1">9.9 <a href="p2-semantics.html#header.user-agent">User-Agent</a></li>290 </ul>291 </li>292 <li class="tocline0">10. <a href="p2-semantics.html#IANA.considerations">IANA Considerations</a></li>293 <li class="tocline0">11. <a href="p2-semantics.html#security.considerations">Security Considerations</a><ul class="toc">294 <li class="tocline1">11.1 <a href="p2-semantics.html#security.sensitive">Transfer of Sensitive Information</a></li>295 <li class="tocline1">11.2 <a href="p2-semantics.html#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>296 <li class="tocline1">11.3 <a href="p2-semantics.html#location.spoofing">Location Headers and Spoofing</a></li>297 </ul>298 </li>299 <li class="tocline0">12. <a href="p2-semantics.html#ack">Acknowledgments</a></li>300 <li class="tocline0">13. <a href="p2-semantics.html#rfc.references">References</a><ul class="toc">301 <li class="tocline1">13.1 <a href="p2-semantics.html#rfc.references.1">Normative References</a></li>302 <li class="tocline1">13.2 <a href="p2-semantics.html#rfc.references.2">Informative References</a></li>303 </ul>304 </li>305 <li class="tocline0"><a href="p2-semantics.html#rfc.authors">Authors' Addresses</a></li>306 <li class="tocline0">A. <a href="p2-semantics.html#compatibility">Compatibility with Previous Versions</a><ul class="toc">307 <li class="tocline1">A.1 <a href="p2-semantics.html#changes.from.rfc.2068">Changes from RFC 2068</a></li>308 <li class="tocline1">A.2 <a href="p2-semantics.html#changes.from.rfc.2616">Changes from RFC 2616</a></li>309 </ul>310 </li>311 <li class="tocline0">B. <a href="p2-semantics.html#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">312 <li class="tocline1">B.1 <a href="p2-semantics.html#rfc.section.B.1">Since RFC2616</a></li>313 <li class="tocline1">B.2 <a href="p2-semantics.html#rfc.section.B.2">Since draft-ietf-httpbis-p2-semantics-00</a></li>314 <li class="tocline1">B.3 <a href="p2-semantics.html#rfc.section.B.3">Since draft-ietf-httpbis-p2-semantics-01</a></li>315 </ul>316 </li>317 <li class="tocline0"><a href="p2-semantics.html#rfc.ipr">Intellectual Property and Copyright Statements</a></li>318 <li class="tocline0"><a href="p2-semantics.html#rfc.index">Index</a></li>319 </ul>320 321 <h2><a href="p3-payload.html">HTTP/1.1, part 3: Message Payload and Content Negotiation</a></h2>322 <ul class="toc">323 <li class="tocline0">1. <a href="p3-payload.html#introduction">Introduction</a><ul class="toc">324 <li class="tocline1">1.1 <a href="p3-payload.html#intro.requirements">Requirements</a></li>325 </ul>326 </li>327 <li class="tocline0">2. <a href="p3-payload.html#protocol.parameters">Protocol Parameters</a><ul class="toc">328 <li class="tocline1">2.1 <a href="p3-payload.html#character.sets">Character Sets</a><ul class="toc">329 <li class="tocline1">2.1.1 <a href="p3-payload.html#missing.charset">Missing Charset</a></li>330 </ul>331 </li>332 <li class="tocline1">2.2 <a href="p3-payload.html#content.codings">Content Codings</a></li>333 <li class="tocline1">2.3 <a href="p3-payload.html#media.types">Media Types</a><ul class="toc">334 <li class="tocline1">2.3.1 <a href="p3-payload.html#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>335 <li class="tocline1">2.3.2 <a href="p3-payload.html#multipart.types">Multipart Types</a></li>336 </ul>337 </li>338 <li class="tocline1">2.4 <a href="p3-payload.html#quality.values">Quality Values</a></li>339 <li class="tocline1">2.5 <a href="p3-payload.html#language.tags">Language Tags</a></li>340 </ul>341 </li>342 <li class="tocline0">3. <a href="p3-payload.html#entity">Entity</a><ul class="toc">343 <li class="tocline1">3.1 <a href="p3-payload.html#entity.header.fields">Entity Header Fields</a></li>344 <li class="tocline1">3.2 <a href="p3-payload.html#entity.body">Entity Body</a><ul class="toc">345 <li class="tocline1">3.2.1 <a href="p3-payload.html#type">Type</a></li>346 <li class="tocline1">3.2.2 <a href="p3-payload.html#entity.length">Entity Length</a></li>347 </ul>348 </li>349 </ul>350 </li>351 <li class="tocline0">4. <a href="p3-payload.html#content.negotiation">Content Negotiation</a><ul class="toc">352 <li class="tocline1">4.1 <a href="p3-payload.html#server-driven.negotiation">Server-driven Negotiation</a></li>353 <li class="tocline1">4.2 <a href="p3-payload.html#agent-driven.negotiation">Agent-driven Negotiation</a></li>354 <li class="tocline1">4.3 <a href="p3-payload.html#transparent.negotiation">Transparent Negotiation</a></li>355 </ul>356 </li>357 <li class="tocline0">5. <a href="p3-payload.html#header.fields">Header Field Definitions</a><ul class="toc">358 <li class="tocline1">5.1 <a href="p3-payload.html#header.accept">Accept</a></li>359 <li class="tocline1">5.2 <a href="p3-payload.html#header.accept-charset">Accept-Charset</a></li>360 <li class="tocline1">5.3 <a href="p3-payload.html#header.accept-encoding">Accept-Encoding</a></li>361 <li class="tocline1">5.4 <a href="p3-payload.html#header.accept-language">Accept-Language</a></li>362 <li class="tocline1">5.5 <a href="p3-payload.html#header.content-encoding">Content-Encoding</a></li>363 <li class="tocline1">5.6 <a href="p3-payload.html#header.content-language">Content-Language</a></li>364 <li class="tocline1">5.7 <a href="p3-payload.html#header.content-location">Content-Location</a></li>365 <li class="tocline1">5.8 <a href="p3-payload.html#header.content-md5">Content-MD5</a></li>366 <li class="tocline1">5.9 <a href="p3-payload.html#header.content-type">Content-Type</a></li>367 </ul>368 </li>369 <li class="tocline0">6. <a href="p3-payload.html#IANA.considerations">IANA Considerations</a></li>370 <li class="tocline0">7. <a href="p3-payload.html#security.considerations">Security Considerations</a><ul class="toc">371 <li class="tocline1">7.1 <a href="p3-payload.html#privacy.issues.connected.to.accept.headers">Privacy Issues Connected to Accept Headers</a></li>372 <li class="tocline1">7.2 <a href="p3-payload.html#content-disposition.issues">Content-Disposition Issues</a></li>373 </ul>374 </li>375 <li class="tocline0">8. <a href="p3-payload.html#ack">Acknowledgments</a></li>376 <li class="tocline0">9. <a href="p3-payload.html#rfc.references">References</a><ul class="toc">377 <li class="tocline1">9.1 <a href="p3-payload.html#rfc.references.1">Normative References</a></li>378 <li class="tocline1">9.2 <a href="p3-payload.html#rfc.references.2">Informative References</a></li>379 </ul>380 </li>381 <li class="tocline0"><a href="p3-payload.html#rfc.authors">Authors' Addresses</a></li>382 <li class="tocline0">A. <a href="p3-payload.html#differences.between.http.entities.and.rfc.2045.entities">Differences Between HTTP Entities and RFC 2045 Entities</a><ul class="toc">383 <li class="tocline1">A.1 <a href="p3-payload.html#mime-version">MIME-Version</a></li>384 <li class="tocline1">A.2 <a href="p3-payload.html#conversion.to.canonical.form">Conversion to Canonical Form</a></li>385 <li class="tocline1">A.3 <a href="p3-payload.html#introduction.of.content-encoding">Introduction of Content-Encoding</a></li>386 <li class="tocline1">A.4 <a href="p3-payload.html#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li>387 <li class="tocline1">A.5 <a href="p3-payload.html#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li>388 <li class="tocline1">A.6 <a href="p3-payload.html#mhtml.line.length">MHTML and Line Length Limitations</a></li>389 </ul>390 </li>391 <li class="tocline0">B. <a href="p3-payload.html#additional.features">Additional Features</a><ul class="toc">392 <li class="tocline1">B.1 <a href="p3-payload.html#content-disposition">Content-Disposition</a></li>393 </ul>394 </li>395 <li class="tocline0">C. <a href="p3-payload.html#compatibility">Compatibility with Previous Versions</a><ul class="toc">396 <li class="tocline1">C.1 <a href="p3-payload.html#changes.from.rfc.2068">Changes from RFC 2068</a></li>397 <li class="tocline1">C.2 <a href="p3-payload.html#changes.from.rfc.2616">Changes from RFC 2616</a></li>398 </ul>399 </li>400 <li class="tocline0">D. <a href="p3-payload.html#rfc.section.D">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">401 <li class="tocline1">D.1 <a href="p3-payload.html#rfc.section.D.1">Since RFC2616</a></li>402 <li class="tocline1">D.2 <a href="p3-payload.html#rfc.section.D.2">Since draft-ietf-httpbis-p3-payload-00</a></li>403 <li class="tocline1">D.3 <a href="p3-payload.html#rfc.section.D.3">Since draft-ietf-httpbis-p3-payload-01</a></li>404 </ul>405 </li>406 <li class="tocline0"><a href="p3-payload.html#rfc.ipr">Intellectual Property and Copyright Statements</a></li>407 <li class="tocline0"><a href="p3-payload.html#rfc.index">Index</a></li>408 </ul>409 410 <h2><a href="p4-conditional.html">HTTP/1.1, part 4: Conditional Requests</a></h2>411 <ul class="toc">412 <li class="tocline0">1. <a href="p4-conditional.html#introduction">Introduction</a><ul class="toc">413 <li class="tocline1">1.1 <a href="p4-conditional.html#intro.requirements">Requirements</a></li>414 </ul>415 </li>416 <li class="tocline0">2. <a href="p4-conditional.html#entity.tags">Entity Tags</a></li>417 <li class="tocline0">3. <a href="p4-conditional.html#rfc.section.3">Status Code Definitions</a><ul class="toc">418 <li class="tocline1">3.1 <a href="p4-conditional.html#status.304">304 Not Modified</a></li>419 <li class="tocline1">3.2 <a href="p4-conditional.html#status.412">412 Precondition Failed</a></li>420 </ul>421 </li>422 <li class="tocline0">4. <a href="p4-conditional.html#weak.and.strong.validators">Weak and Strong Validators</a></li>423 <li class="tocline0">5. <a href="p4-conditional.html#rules.for.when.to.use.entity.tags.and.last-modified.dates">Rules for When to Use Entity Tags and Last-Modified Dates</a></li>424 <li class="tocline0">6. <a href="p4-conditional.html#header.fields">Header Field Definitions</a><ul class="toc">425 <li class="tocline1">6.1 <a href="p4-conditional.html#header.etag">ETag</a></li>426 <li class="tocline1">6.2 <a href="p4-conditional.html#header.if-match">If-Match</a></li>427 <li class="tocline1">6.3 <a href="p4-conditional.html#header.if-modified-since">If-Modified-Since</a></li>428 <li class="tocline1">6.4 <a href="p4-conditional.html#header.if-none-match">If-None-Match</a></li>429 <li class="tocline1">6.5 <a href="p4-conditional.html#header.if-unmodified-since">If-Unmodified-Since</a></li>430 <li class="tocline1">6.6 <a href="p4-conditional.html#header.last-modified">Last-Modified</a></li>431 </ul>432 </li>433 <li class="tocline0">7. <a href="p4-conditional.html#IANA.considerations">IANA Considerations</a></li>434 <li class="tocline0">8. <a href="p4-conditional.html#security.considerations">Security Considerations</a></li>435 <li class="tocline0">9. <a href="p4-conditional.html#ack">Acknowledgments</a></li>436 <li class="tocline0">10. <a href="p4-conditional.html#rfc.references">References</a><ul class="toc">437 <li class="tocline1">10.1 <a href="p4-conditional.html#rfc.references.1">Normative References</a></li>438 <li class="tocline1">10.2 <a href="p4-conditional.html#rfc.references.2">Informative References</a></li>439 </ul>440 </li>441 <li class="tocline0"><a href="p4-conditional.html#rfc.authors">Authors' Addresses</a></li>442 <li class="tocline0">A. <a href="p4-conditional.html#compatibility">Compatibility with Previous Versions</a><ul class="toc">443 <li class="tocline1">A.1 <a href="p4-conditional.html#changes.from.rfc.2616">Changes from RFC 2616</a></li>444 </ul>445 </li>446 <li class="tocline0">B. <a href="p4-conditional.html#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">447 <li class="tocline1">B.1 <a href="p4-conditional.html#rfc.section.B.1">Since RFC2616</a></li>448 <li class="tocline1">B.2 <a href="p4-conditional.html#rfc.section.B.2">Since draft-ietf-httpbis-p4-conditional-00</a></li>449 <li class="tocline1">B.3 <a href="p4-conditional.html#rfc.section.B.3">Since draft-ietf-httpbis-p4-conditional-01</a></li>450 </ul>451 </li>452 <li class="tocline0"><a href="p4-conditional.html#rfc.ipr">Intellectual Property and Copyright Statements</a></li>453 <li class="tocline0"><a href="p4-conditional.html#rfc.index">Index</a></li>454 </ul>455 456 <h2><a href="p5-range.html">HTTP/1.1, part 5: Range Requests and Partial Responses</a></h2>457 <ul class="toc">458 <li class="tocline0">1. <a href="p5-range.html#introduction">Introduction</a><ul class="toc">459 <li class="tocline1">1.1 <a href="p5-range.html#intro.requirements">Requirements</a></li>460 </ul>461 </li>462 <li class="tocline0">2. <a href="p5-range.html#range.units">Range Units</a></li>463 <li class="tocline0">3. <a href="p5-range.html#rfc.section.3">Status Code Definitions</a><ul class="toc">464 <li class="tocline1">3.1 <a href="p5-range.html#status.206">206 Partial Content</a></li>465 <li class="tocline1">3.2 <a href="p5-range.html#status.416">416 Requested Range Not Satisfiable</a></li>466 </ul>467 </li>468 <li class="tocline0">4. <a href="p5-range.html#combining.byte.ranges">Combining Byte Ranges</a></li>469 <li class="tocline0">5. <a href="p5-range.html#header.fields">Header Field Definitions</a><ul class="toc">470 <li class="tocline1">5.1 <a href="p5-range.html#header.accept-ranges">Accept-Ranges</a></li>471 <li class="tocline1">5.2 <a href="p5-range.html#header.content-range">Content-Range</a></li>472 <li class="tocline1">5.3 <a href="p5-range.html#header.if-range">If-Range</a></li>473 <li class="tocline1">5.4 <a href="p5-range.html#header.range">Range</a><ul class="toc">474 <li class="tocline1">5.4.1 <a href="p5-range.html#byte.ranges">Byte Ranges</a></li>475 <li class="tocline1">5.4.2 <a href="p5-range.html#range.retrieval.requests">Range Retrieval Requests</a></li>476 </ul>477 </li>478 </ul>479 </li>480 <li class="tocline0">6. <a href="p5-range.html#IANA.considerations">IANA Considerations</a></li>481 <li class="tocline0">7. <a href="p5-range.html#security.considerations">Security Considerations</a></li>482 <li class="tocline0">8. <a href="p5-range.html#ack">Acknowledgments</a></li>483 <li class="tocline0">9. <a href="p5-range.html#rfc.references">References</a><ul class="toc">484 <li class="tocline1">9.1 <a href="p5-range.html#rfc.references.1">Normative References</a></li>485 <li class="tocline1">9.2 <a href="p5-range.html#rfc.references.2">Informative References</a></li>486 </ul>487 </li>488 <li class="tocline0"><a href="p5-range.html#rfc.authors">Authors' Addresses</a></li>489 <li class="tocline0">A. <a href="p5-range.html#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li>490 <li class="tocline0">B. <a href="p5-range.html#compatibility">Compatibility with Previous Versions</a><ul class="toc">491 <li class="tocline1">B.1 <a href="p5-range.html#changes.from.rfc.2068">Changes from RFC 2068</a></li>492 <li class="tocline1">B.2 <a href="p5-range.html#changes.from.rfc.2616">Changes from RFC 2616</a></li>493 </ul>494 </li>495 <li class="tocline0">C. <a href="p5-range.html#rfc.section.C">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">496 <li class="tocline1">C.1 <a href="p5-range.html#rfc.section.C.1">Since RFC2616</a></li>497 <li class="tocline1">C.2 <a href="p5-range.html#rfc.section.C.2">Since draft-ietf-httpbis-p5-range-00</a></li>498 <li class="tocline1">C.3 <a href="p5-range.html#rfc.section.C.3">Since draft-ietf-httpbis-p5-range-01</a></li>499 </ul>500 </li>501 <li class="tocline0"><a href="p5-range.html#rfc.ipr">Intellectual Property and Copyright Statements</a></li>502 <li class="tocline0"><a href="p5-range.html#rfc.index">Index</a></li>503 </ul>504 505 <h2><a href="p6-cache.html">HTTP/1.1, part 6: Caching</a></h2>506 <ul class="toc">507 <li class="tocline0">1. <a href="p6-cache.html#caching">Introduction</a><ul class="toc">508 <li class="tocline1">1.1 <a href="p6-cache.html#intro.purpose">Purpose</a></li>509 <li class="tocline1">1.2 <a href="p6-cache.html#intro.terminology">Terminology</a></li>510 <li class="tocline1">1.3 <a href="p6-cache.html#intro.requirements">Requirements</a></li>511 </ul>512 </li>513 <li class="tocline0">2. <a href="p6-cache.html#caching.overview">Overview</a><ul class="toc">514 <li class="tocline1">2.1 <a href="p6-cache.html#cache.correctness">Cache Correctness</a></li>515 <li class="tocline1">2.2 <a href="p6-cache.html#warnings">Warnings</a></li>516 <li class="tocline1">2.3 <a href="p6-cache.html#cache-control.mechanisms">Cache-control Mechanisms</a></li>517 <li class="tocline1">2.4 <a href="p6-cache.html#explicit.ua.warnings">Explicit User Agent Warnings</a></li>518 <li class="tocline1">2.5 <a href="p6-cache.html#exceptions.to.the.rules.and.warnings">Exceptions to the Rules and Warnings</a></li>519 <li class="tocline1">2.6 <a href="p6-cache.html#client-controlled.behavior">Client-controlled Behavior</a></li>520 </ul>521 </li>522 <li class="tocline0">3. <a href="p6-cache.html#expiration.model">Expiration Model</a><ul class="toc">523 <li class="tocline1">3.1 <a href="p6-cache.html#server-specified.expiration">Server-Specified Expiration</a></li>524 <li class="tocline1">3.2 <a href="p6-cache.html#heuristic.expiration">Heuristic Expiration</a></li>525 <li class="tocline1">3.3 <a href="p6-cache.html#age.calculations">Age Calculations</a></li>526 <li class="tocline1">3.4 <a href="p6-cache.html#expiration.calculations">Expiration Calculations</a></li>527 <li class="tocline1">3.5 <a href="p6-cache.html#disambiguating.expiration.values">Disambiguating Expiration Values</a></li>528 <li class="tocline1">3.6 <a href="p6-cache.html#disambiguating.multiple.responses">Disambiguating Multiple Responses</a></li>529 </ul>530 </li>531 <li class="tocline0">4. <a href="p6-cache.html#validation.model">Validation Model</a></li>532 <li class="tocline0">5. <a href="p6-cache.html#response.cacheability">Response Cacheability</a></li>533 <li class="tocline0">6. <a href="p6-cache.html#constructing.responses.from.caches">Constructing Responses From Caches</a><ul class="toc">534 <li class="tocline1">6.1 <a href="p6-cache.html#end-to-end.and.hop-by-hop.headers">End-to-end and Hop-by-hop Headers</a></li>535 <li class="tocline1">6.2 <a href="p6-cache.html#non-modifiable.headers">Non-modifiable Headers</a></li>536 <li class="tocline1">6.3 <a href="p6-cache.html#combining.headers">Combining Headers</a></li>537 </ul>538 </li>539 <li class="tocline0">7. <a href="p6-cache.html#caching.negotiated.responses">Caching Negotiated Responses</a></li>540 <li class="tocline0">8. <a href="p6-cache.html#shared.and.non-shared.caches">Shared and Non-Shared Caches</a></li>541 <li class="tocline0">9. <a href="p6-cache.html#errors.or.incomplete.response.cache.behavior">Errors or Incomplete Response Cache Behavior</a></li>542 <li class="tocline0">10. <a href="p6-cache.html#side.effects.of.get.and.head">Side Effects of GET and HEAD</a></li>543 <li class="tocline0">11. <a href="p6-cache.html#invalidation.after.updates.or.deletions">Invalidation After Updates or Deletions</a></li>544 <li class="tocline0">12. <a href="p6-cache.html#write-through.mandatory">Write-Through Mandatory</a></li>545 <li class="tocline0">13. <a href="p6-cache.html#cache.replacement">Cache Replacement</a></li>546 <li class="tocline0">14. <a href="p6-cache.html#history.lists">History Lists</a></li>547 <li class="tocline0">15. <a href="p6-cache.html#header.fields">Header Field Definitions</a><ul class="toc">548 <li class="tocline1">15.1 <a href="p6-cache.html#header.age">Age</a></li>549 <li class="tocline1">15.2 <a href="p6-cache.html#header.cache-control">Cache-Control</a><ul class="toc">550 <li class="tocline1">15.2.1 <a href="p6-cache.html#what.is.cacheable">What is Cacheable</a></li>551 <li class="tocline1">15.2.2 <a href="p6-cache.html#what.may.be.stored.by.caches">What May be Stored by Caches</a></li>552 <li class="tocline1">15.2.3 <a href="p6-cache.html#modifications.of.the.basic.expiration.mechanism">Modifications of the Basic Expiration Mechanism</a></li>553 <li class="tocline1">15.2.4 <a href="p6-cache.html#cache.revalidation.and.reload.controls">Cache Revalidation and Reload Controls</a></li>554 <li class="tocline1">15.2.5 <a href="p6-cache.html#no-transform.directive">No-Transform Directive</a></li>555 <li class="tocline1">15.2.6 <a href="p6-cache.html#cache.control.extensions">Cache Control Extensions</a></li>556 </ul>557 </li>558 <li class="tocline1">15.3 <a href="p6-cache.html#header.expires">Expires</a></li>559 <li class="tocline1">15.4 <a href="p6-cache.html#header.pragma">Pragma</a></li>560 <li class="tocline1">15.5 <a href="p6-cache.html#header.vary">Vary</a></li>561 <li class="tocline1">15.6 <a href="p6-cache.html#header.warning">Warning</a></li>562 </ul>563 </li>564 <li class="tocline0">16. <a href="p6-cache.html#IANA.considerations">IANA Considerations</a></li>565 <li class="tocline0">17. <a href="p6-cache.html#security.considerations">Security Considerations</a></li>566 <li class="tocline0">18. <a href="p6-cache.html#ack">Acknowledgments</a></li>567 <li class="tocline0">19. <a href="p6-cache.html#rfc.references">References</a><ul class="toc">568 <li class="tocline1">19.1 <a href="p6-cache.html#rfc.references.1">Normative References</a></li>569 <li class="tocline1">19.2 <a href="p6-cache.html#rfc.references.2">Informative References</a></li>570 </ul>571 </li>572 <li class="tocline0"><a href="p6-cache.html#rfc.authors">Authors' Addresses</a></li>573 <li class="tocline0">A. <a href="p6-cache.html#compatibility">Compatibility with Previous Versions</a><ul class="toc">574 <li class="tocline1">A.1 <a href="p6-cache.html#changes.from.rfc.2068">Changes from RFC 2068</a></li>575 <li class="tocline1">A.2 <a href="p6-cache.html#changes.from.rfc.2616">Changes from RFC 2616</a></li>576 </ul>577 </li>578 <li class="tocline0">B. <a href="p6-cache.html#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">579 <li class="tocline1">B.1 <a href="p6-cache.html#rfc.section.B.1">Since RFC2616</a></li>580 <li class="tocline1">B.2 <a href="p6-cache.html#rfc.section.B.2">Since draft-ietf-httpbis-p6-cache-00</a></li>581 <li class="tocline1">B.3 <a href="p6-cache.html#rfc.section.B.3">Since draft-ietf-httpbis-p6-cache-01</a></li>582 </ul>583 </li>584 <li class="tocline0"><a href="p6-cache.html#rfc.ipr">Intellectual Property and Copyright Statements</a></li>585 <li class="tocline0"><a href="p6-cache.html#rfc.index">Index</a></li>586 </ul>587 588 <h2><a href="p7-auth.html">HTTP/1.1, part 7: Authentication</a></h2>589 <ul class="toc">590 <li class="tocline0">1. <a href="p7-auth.html#introduction">Introduction</a><ul class="toc">591 <li class="tocline1">1.1 <a href="p7-auth.html#intro.requirements">Requirements</a></li>592 </ul>593 </li>594 <li class="tocline0">2. <a href="p7-auth.html#rfc.section.2">Status Code Definitions</a><ul class="toc">595 <li class="tocline1">2.1 <a href="p7-auth.html#status.401">401 Unauthorized</a></li>596 <li class="tocline1">2.2 <a href="p7-auth.html#status.407">407 Proxy Authentication Required</a></li>597 </ul>598 </li>599 <li class="tocline0">3. <a href="p7-auth.html#header.fields">Header Field Definitions</a><ul class="toc">600 <li class="tocline1">3.1 <a href="p7-auth.html#header.authorization">Authorization</a></li>601 <li class="tocline1">3.2 <a href="p7-auth.html#header.proxy-authenticate">Proxy-Authenticate</a></li>602 <li class="tocline1">3.3 <a href="p7-auth.html#header.proxy-authorization">Proxy-Authorization</a></li>603 <li class="tocline1">3.4 <a href="p7-auth.html#header.www-authenticate">WWW-Authenticate</a></li>604 </ul>605 </li>606 <li class="tocline0">4. <a href="p7-auth.html#IANA.considerations">IANA Considerations</a></li>607 <li class="tocline0">5. <a href="p7-auth.html#security.considerations">Security Considerations</a><ul class="toc">608 <li class="tocline1">5.1 <a href="p7-auth.html#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></li>609 </ul>610 </li>611 <li class="tocline0">6. <a href="p7-auth.html#ack">Acknowledgments</a></li>612 <li class="tocline0">7. <a href="p7-auth.html#rfc.references">References</a><ul class="toc">613 <li class="tocline1">7.1 <a href="p7-auth.html#rfc.references.1">Normative References</a></li>614 <li class="tocline1">7.2 <a href="p7-auth.html#rfc.references.2">Informative References</a></li>615 </ul>616 </li>617 <li class="tocline0"><a href="p7-auth.html#rfc.authors">Authors' Addresses</a></li>618 <li class="tocline0">A. <a href="p7-auth.html#compatibility">Compatibility with Previous Versions</a><ul class="toc">619 <li class="tocline1">A.1 <a href="p7-auth.html#changes.from.rfc.2616">Changes from RFC 2616</a></li>620 </ul>621 </li>622 <li class="tocline0">B. <a href="p7-auth.html#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">623 <li class="tocline1">B.1 <a href="p7-auth.html#rfc.section.B.1">Since RFC2616</a></li>624 <li class="tocline1">B.2 <a href="p7-auth.html#rfc.section.B.2">Since draft-ietf-httpbis-p7-auth-00</a></li>625 <li class="tocline1">B.3 <a href="p7-auth.html#rfc.section.B.3">Since draft-ietf-httpbis-p7-auth-01</a></li>626 </ul>627 </li>628 <li class="tocline0"><a href="p7-auth.html#rfc.ipr">Intellectual Property and Copyright Statements</a></li>629 <li class="tocline0"><a href="p7-auth.html#rfc.index">Index</a></li>630 </ul>631 <!-- ZZZZZZZ -->632 </div>633 </div>634 630 </body> 635 631 </html> -
draft-ietf-httpbis/latest/p1-messaging.html
r204 r205 690 690 <dl class="empty"> 691 691 <dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of 692 entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 3</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.692 entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 693 693 </dd> 694 694 </dl> … … 696 696 </p> 697 697 <dl class="empty"> 698 <dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status.698 <dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status. 699 699 </dd> 700 700 </dl> … … 702 702 </p> 703 703 <dl class="empty"> 704 <dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses).704 <dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses). 705 705 </dd> 706 706 </dl> … … 949 949 ; US-ASCII double-quote mark (34) 950 950 </pre><p id="rfc.section.2.2.p.3">HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements except the entity-body (see <a href="#tolerant.applications" title="Tolerant Applications">Appendix B</a> for tolerant applications). The end-of-line marker within an entity-body is defined by its associated media type, as described 951 in <a href="p3-payload.html#media.types" title="Media Types">Section 2.3</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.951 in <a href="p3-payload.html#media.types" title="Media Types">Section 3.3</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 952 952 </p> 953 953 <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.12"></span> CRLF = CR LF … … 1033 1033 relativeURI = <relativeURI, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.7"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-5">Section 5</a>> 1034 1034 uri-host = <host, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.8"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-3.2.2">Section 3.2.2</a>> 1035 </pre><p id="rfc.section.3.2.1.p.3">HTTP does not place any a priori limit on the length of a URI. Servers <em class="bcp14">MUST</em> be able to handle the URI of any resource they serve, and <em class="bcp14">SHOULD</em> be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server <em class="bcp14">SHOULD</em> return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see <a href="p2-semantics.html#status.414" title="414 Request-URI Too Long">Section 8.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).1035 </pre><p id="rfc.section.3.2.1.p.3">HTTP does not place any a priori limit on the length of a URI. Servers <em class="bcp14">MUST</em> be able to handle the URI of any resource they serve, and <em class="bcp14">SHOULD</em> be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server <em class="bcp14">SHOULD</em> return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see <a href="p2-semantics.html#status.414" title="414 Request-URI Too Long">Section 9.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). 1036 1036 </p> 1037 1037 <p id="rfc.section.3.2.1.p.4"> </p> … … 1129 1129 </p> 1130 1130 <p id="rfc.section.3.4.p.8">The Internet Assigned Numbers Authority (IANA) acts as a registry for transfer-coding value tokens. Initially, the registry 1131 contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section 3.4.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).1132 </p> 1133 <p id="rfc.section.3.4.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).1131 contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section 3.4.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="Content Codings">Section 3.2</a> of <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). 1132 </p> 1133 <p id="rfc.section.3.4.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="Content Codings">Section 3.2</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). 1134 1134 </p> 1135 1135 <p id="rfc.section.3.4.p.10">A server which receives an entity-body with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> return 501 (Not Implemented), and close the connection. A server <em class="bcp14">MUST NOT</em> send transfer-codings to an HTTP/1.0 client. … … 1226 1226 </p> 1227 1227 <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a> <a id="message.headers" href="#message.headers">Message Headers</a></h2> 1228 <p id="rfc.section.4.2.p.1">HTTP header fields, which include general-header (<a href="#general.header.fields" title="General Header Fields">Section 4.5</a>), request-header (<a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), response-header (<a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 5</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), and entity-header (<a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a> of <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) fields, follow the same generic format as that given in <a href="http://tools.ietf.org/html/rfc2822#section-2.1">Section 2.1</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.3"><cite title="Internet Message Format">[RFC2822]</cite></a>. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The1228 <p id="rfc.section.4.2.p.1">HTTP header fields, which include general-header (<a href="#general.header.fields" title="General Header Fields">Section 4.5</a>), request-header (<a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), response-header (<a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), and entity-header (<a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</a> of <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) fields, follow the same generic format as that given in <a href="http://tools.ietf.org/html/rfc2822#section-2.1">Section 2.1</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.3"><cite title="Internet Message Format">[RFC2822]</cite></a>. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The 1229 1229 field value <em class="bcp14">MAY</em> be preceded by any amount of LWS, though a single SP is preferred. Header fields can be extended over multiple lines by preceding 1230 1230 each extra line with at least one SP or HTAB. Applications ought to follow "common form", where one is known or indicated, … … 1264 1264 <p id="rfc.section.4.3.p.4">The rules for when a message-body is allowed in a message differ for requests and responses.</p> 1265 1265 <p id="rfc.section.4.3.p.5">The presence of a message-body in a request is signaled by the inclusion of a Content-Length or Transfer-Encoding header field 1266 in the request's message-headers. A message-body <em class="bcp14">MUST NOT</em> be included in a request if the specification of the request method (<a href="p2-semantics.html#method" title="Method">Section 2</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) explicitly disallows an entity-body in requests. When a request message contains both a message-body of non-zero length1266 in the request's message-headers. A message-body <em class="bcp14">MUST NOT</em> be included in a request if the specification of the request method (<a href="p2-semantics.html#method" title="Method">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) explicitly disallows an entity-body in requests. When a request message contains both a message-body of non-zero length 1267 1267 and a method that does not define any semantics for that request message-body, then an origin server <em class="bcp14">SHOULD</em> either ignore the message-body or respond with an appropriate error message (e.g., 413). A proxy or gateway, when presented 1268 1268 the same request, <em class="bcp14">SHOULD</em> either forward the request inbound with the message-body or ignore the message-body when determining a response. … … 1324 1324 to the entity being transferred. These header fields apply only to the message being transmitted. 1325 1325 </p> 1326 <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.67"></span> general-header = Cache-Control ; <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 1 5.2</a>1326 <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.67"></span> general-header = Cache-Control ; <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 16.2</a> 1327 1327 | Connection ; <a href="#header.connection" id="rfc.xref.header.connection.1" title="Connection">Section 8.1</a> 1328 1328 | Date ; <a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section 8.3</a> 1329 | Pragma ; <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 1 5.4</a>1329 | Pragma ; <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 16.4</a> 1330 1330 | Trailer ; <a href="#header.trailer" id="rfc.xref.header.trailer.2" title="Trailer">Section 8.6</a> 1331 1331 | Transfer-Encoding ; <a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.4" title="Transfer-Encoding">Section 8.7</a> 1332 1332 | Upgrade ; <a href="#header.upgrade" id="rfc.xref.header.upgrade.1" title="Upgrade">Section 8.8</a> 1333 1333 | Via ; <a href="#header.via" id="rfc.xref.header.via.1" title="Via">Section 8.9</a> 1334 | Warning ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.warning" title="Warning">Section 1 5.6</a>1334 | Warning ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.warning" title="Warning">Section 16.6</a> 1335 1335 </pre><p id="rfc.section.4.5.p.3">General-header field names can be extended reliably only in combination with a change in the protocol version. However, new 1336 1336 or experimental header fields may be given the semantics of general header fields if all parties in the communication recognize … … 1343 1343 <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.68"></span> Request = Request-Line ; <a href="#request-line" title="Request-Line">Section 5.1</a> 1344 1344 *(( general-header ; <a href="#general.header.fields" title="General Header Fields">Section 4.5</a> 1345 | request-header ; <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 3</a>1346 | entity-header ) CRLF) ; <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>1345 | request-header ; <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a> 1346 | entity-header ) CRLF) ; <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</a> 1347 1347 CRLF 1348 1348 [ message-body ] ; <a href="#message.body" title="Message Body">Section 4.3</a> … … 1375 1375 </pre><p id="rfc.section.5.1.2.p.7">To allow for transition to absoluteURIs in all requests in future versions of HTTP, all HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absoluteURI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies. 1376 1376 </p> 1377 <p id="rfc.section.5.1.2.p.8">The authority form is only used by the CONNECT method (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 7.9</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).1377 <p id="rfc.section.5.1.2.p.8">The authority form is only used by the CONNECT method (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 8.9</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). 1378 1378 </p> 1379 1379 <p id="rfc.section.5.1.2.p.9">The most common form of Request-URI is that used to identify a resource on an origin server or gateway. In this case the absolute … … 1421 1421 <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.73"></span> Response = Status-Line ; <a href="#status-line" title="Status-Line">Section 6.1</a> 1422 1422 *(( general-header ; <a href="#general.header.fields" title="General Header Fields">Section 4.5</a> 1423 | response-header ; <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 5</a>1424 | entity-header ) CRLF) ; <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>1423 | response-header ; <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a> 1424 | entity-header ) CRLF) ; <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</a> 1425 1425 CRLF 1426 1426 [ message-body ] ; <a href="#message.body" title="Message Body">Section 4.3</a> … … 1433 1433 </pre><h3 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a> <a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h3> 1434 1434 <p id="rfc.section.6.1.1.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. These codes 1435 are fully defined in <a href="p2-semantics.html#status.codes" title="Status Code Definitions">Section 8</a> of <a href="#Part2" id="rfc.xref.Part2.8"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>. The Reason Phrase exists for the sole purpose of providing a textual description associated with the numeric status code,1435 are fully defined in <a href="p2-semantics.html#status.codes" title="Status Code Definitions">Section 9</a> of <a href="#Part2" id="rfc.xref.Part2.8"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>. The Reason Phrase exists for the sole purpose of providing a textual description associated with the numeric status code, 1436 1436 out of deference to earlier Internet application protocols that were more frequently used with interactive text clients. A 1437 1437 client <em class="bcp14">SHOULD</em> ignore the content of the Reason Phrase. … … 1503 1503 <p id="rfc.section.7.1.2.2.p.2">Clients which assume persistent connections and pipeline immediately after connection establishment <em class="bcp14">SHOULD</em> be prepared to retry their connection if the first pipelined attempt fails. If a client does such a retry, it <em class="bcp14">MUST NOT</em> pipeline before it knows the connection is persistent. Clients <em class="bcp14">MUST</em> also be prepared to resend their requests if the server closes the connection before sending all of the corresponding responses. 1504 1504 </p> 1505 <p id="rfc.section.7.1.2.2.p.3">Clients <em class="bcp14">SHOULD NOT</em> pipeline requests using non-idempotent methods or non-idempotent sequences of methods (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 7.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.9"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). Otherwise, a premature termination of the transport connection could lead to indeterminate results. A client wishing to1505 <p id="rfc.section.7.1.2.2.p.3">Clients <em class="bcp14">SHOULD NOT</em> pipeline requests using non-idempotent methods or non-idempotent sequences of methods (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 8.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.9"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). Otherwise, a premature termination of the transport connection could lead to indeterminate results. A client wishing to 1506 1506 send a non-idempotent request <em class="bcp14">SHOULD</em> wait to send that request until it has received the response status for the previous request. 1507 1507 </p> … … 1528 1528 </p> 1529 1529 <p id="rfc.section.7.1.4.p.4">This means that clients, servers, and proxies <em class="bcp14">MUST</em> be able to recover from asynchronous close events. Client software <em class="bcp14">SHOULD</em> reopen the transport connection and retransmit the aborted sequence of requests without user interaction so long as the request 1530 sequence is idempotent (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 7.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). Non-idempotent methods or sequences <em class="bcp14">MUST NOT</em> be automatically retried, although user agents <em class="bcp14">MAY</em> offer a human operator the choice of retrying the request(s). Confirmation by user-agent software with semantic understanding1530 sequence is idempotent (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 8.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). Non-idempotent methods or sequences <em class="bcp14">MUST NOT</em> be automatically retried, although user agents <em class="bcp14">MAY</em> offer a human operator the choice of retrying the request(s). Confirmation by user-agent software with semantic understanding 1531 1531 of the application <em class="bcp14">MAY</em> substitute for user confirmation. The automatic retry <em class="bcp14">SHOULD NOT</em> be repeated if the second sequence of requests fails. 1532 1532 </p> … … 1546 1546 </p> 1547 1547 <h3 id="rfc.section.7.2.3"><a href="#rfc.section.7.2.3">7.2.3</a> <a id="use.of.the.100.status" href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></h3> 1548 <p id="rfc.section.7.2.3.p.1">The purpose of the 100 (Continue) status (see <a href="p2-semantics.html#status.100" title="100 Continue">Section 8.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.11"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) is to allow a client that is sending a request message with a request body to determine if the origin server is willing1548 <p id="rfc.section.7.2.3.p.1">The purpose of the 100 (Continue) status (see <a href="p2-semantics.html#status.100" title="100 Continue">Section 9.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.11"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) is to allow a client that is sending a request message with a request body to determine if the origin server is willing 1549 1549 to accept the request (based on the request headers) before the client sends the request body. In some cases, it might either 1550 1550 be inappropriate or highly inefficient for the client to send the body if the server will reject the message without looking … … 1553 1553 <p id="rfc.section.7.2.3.p.2">Requirements for HTTP/1.1 clients: </p> 1554 1554 <ul> 1555 <li>If a client will wait for a 100 (Continue) response before sending the request body, it <em class="bcp14">MUST</em> send an Expect request-header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 9.2</a> of <a href="#Part2" id="rfc.xref.Part2.12"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation.1556 </li> 1557 <li>A client <em class="bcp14">MUST NOT</em> send an Expect request-header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 9.2</a> of <a href="#Part2" id="rfc.xref.Part2.13"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation if it does not intend to send a request body.1555 <li>If a client will wait for a 100 (Continue) response before sending the request body, it <em class="bcp14">MUST</em> send an Expect request-header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 10.2</a> of <a href="#Part2" id="rfc.xref.Part2.12"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation. 1556 </li> 1557 <li>A client <em class="bcp14">MUST NOT</em> send an Expect request-header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 10.2</a> of <a href="#Part2" id="rfc.xref.Part2.13"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation if it does not intend to send a request body. 1558 1558 </li> 1559 1559 </ul> … … 1599 1599 <li>A proxy <em class="bcp14">MUST NOT</em> forward a 100 (Continue) response if the request message was received from an HTTP/1.0 (or earlier) client and did not include 1600 1600 an Expect request-header field with the "100-continue" expectation. This requirement overrides the general rule for forwarding 1601 of 1xx responses (see <a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 8.1</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).1601 of 1xx responses (see <a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 9.1</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). 1602 1602 </li> 1603 1603 </ul> … … 1765 1765 <li> 1766 1766 <p>If the transfer-coding being tested is one of the transfer-codings listed in the TE field, then it is acceptable unless it 1767 is accompanied by a qvalue of 0. (As defined in <a href="p3-payload.html#quality.values" title="Quality Values">Section 2.4</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, a qvalue of 0 means "not acceptable.")1767 is accompanied by a qvalue of 0. (As defined in <a href="p3-payload.html#quality.values" title="Quality Values">Section 3.4</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, a qvalue of 0 means "not acceptable.") 1768 1768 </p> 1769 1769 </li> … … 2698 2698 <li class="indline1"><em>Pad1995</em> <a class="iref" href="#rfc.xref.Pad1995.1">7.1.1</a>, <a class="iref" href="#Pad1995"><b>12.2</b></a></li> 2699 2699 <li class="indline1"><em>Part2</em> <a class="iref" href="#rfc.xref.Part2.1">3.2.1</a>, <a class="iref" href="#rfc.xref.Part2.2">4.2</a>, <a class="iref" href="#rfc.xref.Part2.3">4.2</a>, <a class="iref" href="#rfc.xref.Part2.4">4.3</a>, <a class="iref" href="#rfc.xref.Part2.5">5</a>, <a class="iref" href="#rfc.xref.Part2.6">5.1.2</a>, <a class="iref" href="#rfc.xref.Part2.7">6</a>, <a class="iref" href="#rfc.xref.Part2.8">6.1.1</a>, <a class="iref" href="#rfc.xref.Part2.9">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.10">7.1.4</a>, <a class="iref" href="#rfc.xref.Part2.11">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.12">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.13">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.14">7.2.3</a>, <a class="iref" href="#Part2"><b>12.1</b></a><ul class="ind"> 2700 <li class="indline1"><em>Section 2</em> <a class="iref" href="#rfc.xref.Part2.4">4.3</a></li>2701 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.Part2.2">4.2</a>, <a class="iref" href="#rfc.xref.Part2.5">5</a></li>2702 <li class="indline1"><em>Section 5</em> <a class="iref" href="#rfc.xref.Part2.3">4.2</a>, <a class="iref" href="#rfc.xref.Part2.7">6</a></li>2703 <li class="indline1"><em>Section 7.1.2</em> <a class="iref" href="#rfc.xref.Part2.9">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.10">7.1.4</a></li>2704 <li class="indline1"><em>Section 7.9</em> <a class="iref" href="#rfc.xref.Part2.6">5.1.2</a></li>2705 <li class="indline1"><em>Section 8</em> <a class="iref" href="#rfc.xref.Part2.8">6.1.1</a></li>2706 <li class="indline1"><em>Section 8.1.1</em> <a class="iref" href="#rfc.xref.Part2.11">7.2.3</a></li>2707 <li class="indline1"><em>Section 8.1</em> <a class="iref" href="#rfc.xref.Part2.14">7.2.3</a></li>2708 <li class="indline1"><em>Section 8.4.15</em> <a class="iref" href="#rfc.xref.Part2.1">3.2.1</a></li>2709 <li class="indline1"><em>Section 9.2</em> <a class="iref" href="#rfc.xref.Part2.12">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.13">7.2.3</a></li>2700 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.Part2.4">4.3</a></li> 2701 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part2.2">4.2</a>, <a class="iref" href="#rfc.xref.Part2.5">5</a></li> 2702 <li class="indline1"><em>Section 6</em> <a class="iref" href="#rfc.xref.Part2.3">4.2</a>, <a class="iref" href="#rfc.xref.Part2.7">6</a></li> 2703 <li class="indline1"><em>Section 8.1.2</em> <a class="iref" href="#rfc.xref.Part2.9">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.10">7.1.4</a></li> 2704 <li class="indline1"><em>Section 8.9</em> <a class="iref" href="#rfc.xref.Part2.6">5.1.2</a></li> 2705 <li class="indline1"><em>Section 9</em> <a class="iref" href="#rfc.xref.Part2.8">6.1.1</a></li> 2706 <li class="indline1"><em>Section 9.1.1</em> <a class="iref" href="#rfc.xref.Part2.11">7.2.3</a></li> 2707 <li class="indline1"><em>Section 9.1</em> <a class="iref" href="#rfc.xref.Part2.14">7.2.3</a></li> 2708 <li class="indline1"><em>Section 9.4.15</em> <a class="iref" href="#rfc.xref.Part2.1">3.2.1</a></li> 2709 <li class="indline1"><em>Section 10.2</em> <a class="iref" href="#rfc.xref.Part2.12">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.13">7.2.3</a></li> 2710 2710 </ul> 2711 2711 </li> 2712 2712 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">1.3</a>, <a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.4</a>, <a class="iref" href="#rfc.xref.Part3.5">2.2</a>, <a class="iref" href="#rfc.xref.Part3.6">3.4</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a>, <a class="iref" href="#rfc.xref.Part3.8">4.2</a>, <a class="iref" href="#rfc.xref.Part3.9">5</a>, <a class="iref" href="#rfc.xref.Part3.10">6</a>, <a class="iref" href="#rfc.xref.Part3.11">8.5</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.12">B</a>, <a class="iref" href="#rfc.xref.Part3.13">D.3</a><ul class="ind"> 2713 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part3.6">3.4</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a></li>2714 <li class="indline1"><em>Section 2.3</em> <a class="iref" href="#rfc.xref.Part3.5">2.2</a></li>2715 <li class="indline1"><em>Section 2.4</em> <a class="iref" href="#rfc.xref.Part3.11">8.5</a></li>2716 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.Part3.1">1.3</a></li>2717 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part3.8">4.2</a>, <a class="iref" href="#rfc.xref.Part3.9">5</a>, <a class="iref" href="#rfc.xref.Part3.10">6</a></li>2718 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a></li>2713 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part3.6">3.4</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a></li> 2714 <li class="indline1"><em>Section 3.3</em> <a class="iref" href="#rfc.xref.Part3.5">2.2</a></li> 2715 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.Part3.11">8.5</a></li> 2716 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.1">1.3</a></li> 2717 <li class="indline1"><em>Section 4.1</em> <a class="iref" href="#rfc.xref.Part3.8">4.2</a>, <a class="iref" href="#rfc.xref.Part3.9">5</a>, <a class="iref" href="#rfc.xref.Part3.10">6</a></li> 2718 <li class="indline1"><em>Section 5</em> <a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a></li> 2719 2719 <li class="indline1"><em>Section A</em> <a class="iref" href="#rfc.xref.Part3.4">1.4</a></li> 2720 2720 </ul> … … 2723 2723 <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a>, <a class="iref" href="#rfc.xref.Part6.3">4.5</a>, <a class="iref" href="#rfc.xref.Part6.4">4.5</a>, <a class="iref" href="#rfc.xref.Part6.5">4.5</a>, <a class="iref" href="#Part6"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part6.6">D.3</a><ul class="ind"> 2724 2724 <li class="indline1"><em>Section 1</em> <a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a></li> 2725 <li class="indline1"><em>Section 1 5.2</em> <a class="iref" href="#rfc.xref.Part6.3">4.5</a></li>2726 <li class="indline1"><em>Section 1 5.4</em> <a class="iref" href="#rfc.xref.Part6.4">4.5</a></li>2727 <li class="indline1"><em>Section 1 5.6</em> <a class="iref" href="#rfc.xref.Part6.5">4.5</a></li>2725 <li class="indline1"><em>Section 16.2</em> <a class="iref" href="#rfc.xref.Part6.3">4.5</a></li> 2726 <li class="indline1"><em>Section 16.4</em> <a class="iref" href="#rfc.xref.Part6.4">4.5</a></li> 2727 <li class="indline1"><em>Section 16.6</em> <a class="iref" href="#rfc.xref.Part6.5">4.5</a></li> 2728 2728 </ul> 2729 2729 </li> -
draft-ietf-httpbis/latest/p2-semantics.html
r204 r205 333 333 <link rel="Index" href="#rfc.index"> 334 334 <link rel="Chapter" title="1 Introduction" href="#rfc.section.1"> 335 <link rel="Chapter" title="2 Method" href="#rfc.section.2"> 336 <link rel="Chapter" title="3 Request Header Fields" href="#rfc.section.3"> 337 <link rel="Chapter" title="4 Status Code and Reason Phrase" href="#rfc.section.4"> 338 <link rel="Chapter" title="5 Response Header Fields" href="#rfc.section.5"> 339 <link rel="Chapter" title="6 Entity" href="#rfc.section.6"> 340 <link rel="Chapter" title="7 Method Definitions" href="#rfc.section.7"> 341 <link rel="Chapter" title="8 Status Code Definitions" href="#rfc.section.8"> 342 <link rel="Chapter" title="9 Header Field Definitions" href="#rfc.section.9"> 343 <link rel="Chapter" title="10 IANA Considerations" href="#rfc.section.10"> 344 <link rel="Chapter" title="11 Security Considerations" href="#rfc.section.11"> 345 <link rel="Chapter" title="12 Acknowledgments" href="#rfc.section.12"> 346 <link rel="Chapter" href="#rfc.section.13" title="13 References"> 335 <link rel="Chapter" title="2 Notational Conventions and Generic Grammar" href="#rfc.section.2"> 336 <link rel="Chapter" title="3 Method" href="#rfc.section.3"> 337 <link rel="Chapter" title="4 Request Header Fields" href="#rfc.section.4"> 338 <link rel="Chapter" title="5 Status Code and Reason Phrase" href="#rfc.section.5"> 339 <link rel="Chapter" title="6 Response Header Fields" href="#rfc.section.6"> 340 <link rel="Chapter" title="7 Entity" href="#rfc.section.7"> 341 <link rel="Chapter" title="8 Method Definitions" href="#rfc.section.8"> 342 <link rel="Chapter" title="9 Status Code Definitions" href="#rfc.section.9"> 343 <link rel="Chapter" title="10 Header Field Definitions" href="#rfc.section.10"> 344 <link rel="Chapter" title="11 IANA Considerations" href="#rfc.section.11"> 345 <link rel="Chapter" title="12 Security Considerations" href="#rfc.section.12"> 346 <link rel="Chapter" title="13 Acknowledgments" href="#rfc.section.13"> 347 <link rel="Chapter" href="#rfc.section.14" title="14 References"> 347 348 <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A"> 348 349 <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B"> … … 486 487 </ul> 487 488 </li> 488 <li class="tocline0">2. <a href="#method">Method</a></li> 489 <li class="tocline0">3. <a href="#request.header.fields">Request Header Fields</a></li> 490 <li class="tocline0">4. <a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li> 491 <li class="tocline0">5. <a href="#response.header.fields">Response Header Fields</a></li> 492 <li class="tocline0">6. <a href="#entity">Entity</a></li> 493 <li class="tocline0">7. <a href="#method.definitions">Method Definitions</a><ul class="toc"> 494 <li class="tocline1">7.1 <a href="#safe.and.idempotent">Safe and Idempotent Methods</a><ul class="toc"> 495 <li class="tocline1">7.1.1 <a href="#safe.methods">Safe Methods</a></li> 496 <li class="tocline1">7.1.2 <a href="#idempotent.methods">Idempotent Methods</a></li> 489 <li class="tocline0">2. <a href="#notation">Notational Conventions and Generic Grammar</a></li> 490 <li class="tocline0">3. <a href="#method">Method</a></li> 491 <li class="tocline0">4. <a href="#request.header.fields">Request Header Fields</a></li> 492 <li class="tocline0">5. <a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li> 493 <li class="tocline0">6. <a href="#response.header.fields">Response Header Fields</a></li> 494 <li class="tocline0">7. <a href="#entity">Entity</a></li> 495 <li class="tocline0">8. <a href="#method.definitions">Method Definitions</a><ul class="toc"> 496 <li class="tocline1">8.1 <a href="#safe.and.idempotent">Safe and Idempotent Methods</a><ul class="toc"> 497 <li class="tocline1">8.1.1 <a href="#safe.methods">Safe Methods</a></li> 498 <li class="tocline1">8.1.2 <a href="#idempotent.methods">Idempotent Methods</a></li> 497 499 </ul> 498 500 </li> 499 <li class="tocline1"> 7.2 <a href="#OPTIONS">OPTIONS</a></li>500 <li class="tocline1"> 7.3 <a href="#GET">GET</a></li>501 <li class="tocline1"> 7.4 <a href="#HEAD">HEAD</a></li>502 <li class="tocline1"> 7.5 <a href="#POST">POST</a></li>503 <li class="tocline1"> 7.6 <a href="#PUT">PUT</a></li>504 <li class="tocline1"> 7.7 <a href="#DELETE">DELETE</a></li>505 <li class="tocline1"> 7.8 <a href="#TRACE">TRACE</a></li>506 <li class="tocline1"> 7.9 <a href="#CONNECT">CONNECT</a></li>501 <li class="tocline1">8.2 <a href="#OPTIONS">OPTIONS</a></li> 502 <li class="tocline1">8.3 <a href="#GET">GET</a></li> 503 <li class="tocline1">8.4 <a href="#HEAD">HEAD</a></li> 504 <li class="tocline1">8.5 <a href="#POST">POST</a></li> 505 <li class="tocline1">8.6 <a href="#PUT">PUT</a></li> 506 <li class="tocline1">8.7 <a href="#DELETE">DELETE</a></li> 507 <li class="tocline1">8.8 <a href="#TRACE">TRACE</a></li> 508 <li class="tocline1">8.9 <a href="#CONNECT">CONNECT</a></li> 507 509 </ul> 508 510 </li> 509 <li class="tocline0"> 8. <a href="#status.codes">Status Code Definitions</a><ul class="toc">510 <li class="tocline1"> 8.1 <a href="#status.1xx">Informational 1xx</a><ul class="toc">511 <li class="tocline1"> 8.1.1 <a href="#status.100">100 Continue</a></li>512 <li class="tocline1"> 8.1.2 <a href="#status.101">101 Switching Protocols</a></li>511 <li class="tocline0">9. <a href="#status.codes">Status Code Definitions</a><ul class="toc"> 512 <li class="tocline1">9.1 <a href="#status.1xx">Informational 1xx</a><ul class="toc"> 513 <li class="tocline1">9.1.1 <a href="#status.100">100 Continue</a></li> 514 <li class="tocline1">9.1.2 <a href="#status.101">101 Switching Protocols</a></li> 513 515 </ul> 514 516 </li> 515 <li class="tocline1"> 8.2 <a href="#status.2xx">Successful 2xx</a><ul class="toc">516 <li class="tocline1"> 8.2.1 <a href="#status.200">200 OK</a></li>517 <li class="tocline1"> 8.2.2 <a href="#status.201">201 Created</a></li>518 <li class="tocline1"> 8.2.3 <a href="#status.202">202 Accepted</a></li>519 <li class="tocline1"> 8.2.4 <a href="#status.203">203 Non-Authoritative Information</a></li>520 <li class="tocline1"> 8.2.5 <a href="#status.204">204 No Content</a></li>521 <li class="tocline1"> 8.2.6 <a href="#status.205">205 Reset Content</a></li>522 <li class="tocline1"> 8.2.7 <a href="#status.206">206 Partial Content</a></li>517 <li class="tocline1">9.2 <a href="#status.2xx">Successful 2xx</a><ul class="toc"> 518 <li class="tocline1">9.2.1 <a href="#status.200">200 OK</a></li> 519 <li class="tocline1">9.2.2 <a href="#status.201">201 Created</a></li> 520 <li class="tocline1">9.2.3 <a href="#status.202">202 Accepted</a></li> 521 <li class="tocline1">9.2.4 <a href="#status.203">203 Non-Authoritative Information</a></li> 522 <li class="tocline1">9.2.5 <a href="#status.204">204 No Content</a></li> 523 <li class="tocline1">9.2.6 <a href="#status.205">205 Reset Content</a></li> 524 <li class="tocline1">9.2.7 <a href="#status.206">206 Partial Content</a></li> 523 525 </ul> 524 526 </li> 525 <li class="tocline1"> 8.3 <a href="#status.3xx">Redirection 3xx</a><ul class="toc">526 <li class="tocline1"> 8.3.1 <a href="#status.300">300 Multiple Choices</a></li>527 <li class="tocline1"> 8.3.2 <a href="#status.301">301 Moved Permanently</a></li>528 <li class="tocline1"> 8.3.3 <a href="#status.302">302 Found</a></li>529 <li class="tocline1"> 8.3.4 <a href="#status.303">303 See Other</a></li>530 <li class="tocline1"> 8.3.5 <a href="#status.304">304 Not Modified</a></li>531 <li class="tocline1"> 8.3.6 <a href="#status.305">305 Use Proxy</a></li>532 <li class="tocline1"> 8.3.7 <a href="#status.306">306 (Unused)</a></li>533 <li class="tocline1"> 8.3.8 <a href="#status.307">307 Temporary Redirect</a></li>527 <li class="tocline1">9.3 <a href="#status.3xx">Redirection 3xx</a><ul class="toc"> 528 <li class="tocline1">9.3.1 <a href="#status.300">300 Multiple Choices</a></li> 529 <li class="tocline1">9.3.2 <a href="#status.301">301 Moved Permanently</a></li> 530 <li class="tocline1">9.3.3 <a href="#status.302">302 Found</a></li> 531 <li class="tocline1">9.3.4 <a href="#status.303">303 See Other</a></li> 532 <li class="tocline1">9.3.5 <a href="#status.304">304 Not Modified</a></li> 533 <li class="tocline1">9.3.6 <a href="#status.305">305 Use Proxy</a></li> 534 <li class="tocline1">9.3.7 <a href="#status.306">306 (Unused)</a></li> 535 <li class="tocline1">9.3.8 <a href="#status.307">307 Temporary Redirect</a></li> 534 536 </ul> 535 537 </li> 536 <li class="tocline1"> 8.4 <a href="#status.4xx">Client Error 4xx</a><ul class="toc">537 <li class="tocline1"> 8.4.1 <a href="#status.400">400 Bad Request</a></li>538 <li class="tocline1"> 8.4.2 <a href="#status.401">401 Unauthorized</a></li>539 <li class="tocline1"> 8.4.3 <a href="#status.402">402 Payment Required</a></li>540 <li class="tocline1"> 8.4.4 <a href="#status.403">403 Forbidden</a></li>541 <li class="tocline1"> 8.4.5 <a href="#status.404">404 Not Found</a></li>542 <li class="tocline1"> 8.4.6 <a href="#status.405">405 Method Not Allowed</a></li>543 <li class="tocline1"> 8.4.7 <a href="#status.406">406 Not Acceptable</a></li>544 <li class="tocline1"> 8.4.8 <a href="#status.407">407 Proxy Authentication Required</a></li>545 <li class="tocline1"> 8.4.9 <a href="#status.408">408 Request Timeout</a></li>546 <li class="tocline1"> 8.4.10 <a href="#status.409">409 Conflict</a></li>547 <li class="tocline1"> 8.4.11 <a href="#status.410">410 Gone</a></li>548 <li class="tocline1"> 8.4.12 <a href="#status.411">411 Length Required</a></li>549 <li class="tocline1"> 8.4.13 <a href="#status.412">412 Precondition Failed</a></li>550 <li class="tocline1"> 8.4.14 <a href="#status.413">413 Request Entity Too Large</a></li>551 <li class="tocline1"> 8.4.15 <a href="#status.414">414 Request-URI Too Long</a></li>552 <li class="tocline1"> 8.4.16 <a href="#status.415">415 Unsupported Media Type</a></li>553 <li class="tocline1"> 8.4.17 <a href="#status.416">416 Requested Range Not Satisfiable</a></li>554 <li class="tocline1"> 8.4.18 <a href="#status.417">417 Expectation Failed</a></li>538 <li class="tocline1">9.4 <a href="#status.4xx">Client Error 4xx</a><ul class="toc"> 539 <li class="tocline1">9.4.1 <a href="#status.400">400 Bad Request</a></li> 540 <li class="tocline1">9.4.2 <a href="#status.401">401 Unauthorized</a></li> 541 <li class="tocline1">9.4.3 <a href="#status.402">402 Payment Required</a></li> 542 <li class="tocline1">9.4.4 <a href="#status.403">403 Forbidden</a></li> 543 <li class="tocline1">9.4.5 <a href="#status.404">404 Not Found</a></li> 544 <li class="tocline1">9.4.6 <a href="#status.405">405 Method Not Allowed</a></li> 545 <li class="tocline1">9.4.7 <a href="#status.406">406 Not Acceptable</a></li> 546 <li class="tocline1">9.4.8 <a href="#status.407">407 Proxy Authentication Required</a></li> 547 <li class="tocline1">9.4.9 <a href="#status.408">408 Request Timeout</a></li> 548 <li class="tocline1">9.4.10 <a href="#status.409">409 Conflict</a></li> 549 <li class="tocline1">9.4.11 <a href="#status.410">410 Gone</a></li> 550 <li class="tocline1">9.4.12 <a href="#status.411">411 Length Required</a></li> 551 <li class="tocline1">9.4.13 <a href="#status.412">412 Precondition Failed</a></li> 552 <li class="tocline1">9.4.14 <a href="#status.413">413 Request Entity Too Large</a></li> 553 <li class="tocline1">9.4.15 <a href="#status.414">414 Request-URI Too Long</a></li> 554 <li class="tocline1">9.4.16 <a href="#status.415">415 Unsupported Media Type</a></li> 555 <li class="tocline1">9.4.17 <a href="#status.416">416 Requested Range Not Satisfiable</a></li> 556 <li class="tocline1">9.4.18 <a href="#status.417">417 Expectation Failed</a></li> 555 557 </ul> 556 558 </li> 557 <li class="tocline1"> 8.5 <a href="#status.5xx">Server Error 5xx</a><ul class="toc">558 <li class="tocline1"> 8.5.1 <a href="#status.500">500 Internal Server Error</a></li>559 <li class="tocline1"> 8.5.2 <a href="#status.501">501 Not Implemented</a></li>560 <li class="tocline1"> 8.5.3 <a href="#status.502">502 Bad Gateway</a></li>561 <li class="tocline1"> 8.5.4 <a href="#status.503">503 Service Unavailable</a></li>562 <li class="tocline1"> 8.5.5 <a href="#status.504">504 Gateway Timeout</a></li>563 <li class="tocline1"> 8.5.6 <a href="#status.505">505 HTTP Version Not Supported</a></li>559 <li class="tocline1">9.5 <a href="#status.5xx">Server Error 5xx</a><ul class="toc"> 560 <li class="tocline1">9.5.1 <a href="#status.500">500 Internal Server Error</a></li> 561 <li class="tocline1">9.5.2 <a href="#status.501">501 Not Implemented</a></li> 562 <li class="tocline1">9.5.3 <a href="#status.502">502 Bad Gateway</a></li> 563 <li class="tocline1">9.5.4 <a href="#status.503">503 Service Unavailable</a></li> 564 <li class="tocline1">9.5.5 <a href="#status.504">504 Gateway Timeout</a></li> 565 <li class="tocline1">9.5.6 <a href="#status.505">505 HTTP Version Not Supported</a></li> 564 566 </ul> 565 567 </li> 566 568 </ul> 567 569 </li> 568 <li class="tocline0"> 9. <a href="#header.fields">Header Field Definitions</a><ul class="toc">569 <li class="tocline1"> 9.1 <a href="#header.allow">Allow</a></li>570 <li class="tocline1"> 9.2 <a href="#header.expect">Expect</a></li>571 <li class="tocline1"> 9.3 <a href="#header.from">From</a></li>572 <li class="tocline1"> 9.4 <a href="#header.location">Location</a></li>573 <li class="tocline1"> 9.5 <a href="#header.max-forwards">Max-Forwards</a></li>574 <li class="tocline1"> 9.6 <a href="#header.referer">Referer</a></li>575 <li class="tocline1"> 9.7 <a href="#header.retry-after">Retry-After</a></li>576 <li class="tocline1"> 9.8 <a href="#header.server">Server</a></li>577 <li class="tocline1"> 9.9 <a href="#header.user-agent">User-Agent</a></li>570 <li class="tocline0">10. <a href="#header.fields">Header Field Definitions</a><ul class="toc"> 571 <li class="tocline1">10.1 <a href="#header.allow">Allow</a></li> 572 <li class="tocline1">10.2 <a href="#header.expect">Expect</a></li> 573 <li class="tocline1">10.3 <a href="#header.from">From</a></li> 574 <li class="tocline1">10.4 <a href="#header.location">Location</a></li> 575 <li class="tocline1">10.5 <a href="#header.max-forwards">Max-Forwards</a></li> 576 <li class="tocline1">10.6 <a href="#header.referer">Referer</a></li> 577 <li class="tocline1">10.7 <a href="#header.retry-after">Retry-After</a></li> 578 <li class="tocline1">10.8 <a href="#header.server">Server</a></li> 579 <li class="tocline1">10.9 <a href="#header.user-agent">User-Agent</a></li> 578 580 </ul> 579 581 </li> 580 <li class="tocline0">1 0. <a href="#IANA.considerations">IANA Considerations</a></li>581 <li class="tocline0">1 1. <a href="#security.considerations">Security Considerations</a><ul class="toc">582 <li class="tocline1">1 1.1 <a href="#security.sensitive">Transfer of Sensitive Information</a></li>583 <li class="tocline1">1 1.2 <a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>584 <li class="tocline1">1 1.3 <a href="#location.spoofing">Location Headers and Spoofing</a></li>582 <li class="tocline0">11. <a href="#IANA.considerations">IANA Considerations</a></li> 583 <li class="tocline0">12. <a href="#security.considerations">Security Considerations</a><ul class="toc"> 584 <li class="tocline1">12.1 <a href="#security.sensitive">Transfer of Sensitive Information</a></li> 585 <li class="tocline1">12.2 <a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li> 586 <li class="tocline1">12.3 <a href="#location.spoofing">Location Headers and Spoofing</a></li> 585 587 </ul> 586 588 </li> 587 <li class="tocline0">1 2. <a href="#ack">Acknowledgments</a></li>588 <li class="tocline0">1 3. <a href="#rfc.references">References</a><ul class="toc">589 <li class="tocline1">1 3.1 <a href="#rfc.references.1">Normative References</a></li>590 <li class="tocline1">1 3.2 <a href="#rfc.references.2">Informative References</a></li>589 <li class="tocline0">13. <a href="#ack">Acknowledgments</a></li> 590 <li class="tocline0">14. <a href="#rfc.references">References</a><ul class="toc"> 591 <li class="tocline1">14.1 <a href="#rfc.references.1">Normative References</a></li> 592 <li class="tocline1">14.2 <a href="#rfc.references.2">Informative References</a></li> 591 593 </ul> 592 594 </li> … … 624 626 <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant." 625 627 </p> 626 <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="method" href="#method">Method</a></h1> 627 <p id="rfc.section.2.p.1">The Method token indicates the method to be performed on the resource identified by the Request-URI. The method is case-sensitive.</p> 628 <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span> Method = "OPTIONS" ; <a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section 7.2</a> 629 | "GET" ; <a href="#GET" id="rfc.xref.GET.1" title="GET">Section 7.3</a> 630 | "HEAD" ; <a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">Section 7.4</a> 631 | "POST" ; <a href="#POST" id="rfc.xref.POST.1" title="POST">Section 7.5</a> 632 | "PUT" ; <a href="#PUT" id="rfc.xref.PUT.1" title="PUT">Section 7.6</a> 633 | "DELETE" ; <a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">Section 7.7</a> 634 | "TRACE" ; <a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">Section 7.8</a> 635 | "CONNECT" ; <a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">Section 7.9</a> 628 <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1> 629 <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="Augmented BNF">Section 2.1</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> and the core rules defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>: <span class="comment">[abnf.dep: ABNF syntax and basic rules will be adopted from RFC 5234, see <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>.]</span> 630 </p> 631 <div id="rfc.figure.u.1"></div><pre class="inline"> DIGIT = <DIGIT, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 632 </pre><div id="rfc.figure.u.2"></div><pre class="inline"> comment = <comment, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 633 quoted-string = <quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 634 token = <token, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 635 </pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="method" href="#method">Method</a></h1> 636 <p id="rfc.section.3.p.1">The Method token indicates the method to be performed on the resource identified by the Request-URI. The method is case-sensitive.</p> 637 <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span> Method = "OPTIONS" ; <a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section 8.2</a> 638 | "GET" ; <a href="#GET" id="rfc.xref.GET.1" title="GET">Section 8.3</a> 639 | "HEAD" ; <a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">Section 8.4</a> 640 | "POST" ; <a href="#POST" id="rfc.xref.POST.1" title="POST">Section 8.5</a> 641 | "PUT" ; <a href="#PUT" id="rfc.xref.PUT.1" title="PUT">Section 8.6</a> 642 | "DELETE" ; <a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">Section 8.7</a> 643 | "TRACE" ; <a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">Section 8.8</a> 644 | "CONNECT" ; <a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">Section 8.9</a> 636 645 | extension-method 637 646 extension-method = token 638 </pre><p id="rfc.section. 2.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section 9.1</a>). The return code of the response always notifies the client whether a method is currently allowed on a resource, since the647 </pre><p id="rfc.section.3.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section 10.1</a>). The return code of the response always notifies the client whether a method is currently allowed on a resource, since the 639 648 set of allowed methods can change dynamically. An origin server <em class="bcp14">SHOULD</em> return the status code 405 (Method Not Allowed) if the method is known by the origin server but not allowed for the requested 640 649 resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET 641 and HEAD <em class="bcp14">MUST</em> be supported by all general-purpose servers. All other methods are <em class="bcp14">OPTIONAL</em>; however, if the above methods are implemented, they <em class="bcp14">MUST</em> be implemented with the same semantics as those specified in <a href="#method.definitions" title="Method Definitions">Section 7</a>.642 </p> 643 <h1 id="rfc.section. 3"><a href="#rfc.section.3">3.</a> <a id="request.header.fields" href="#request.header.fields">Request Header Fields</a></h1>644 <p id="rfc.section. 3.p.1">The request-header fields allow the client to pass additional information about the request, and about the client itself,650 and HEAD <em class="bcp14">MUST</em> be supported by all general-purpose servers. All other methods are <em class="bcp14">OPTIONAL</em>; however, if the above methods are implemented, they <em class="bcp14">MUST</em> be implemented with the same semantics as those specified in <a href="#method.definitions" title="Method Definitions">Section 8</a>. 651 </p> 652 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="request.header.fields" href="#request.header.fields">Request Header Fields</a></h1> 653 <p id="rfc.section.4.p.1">The request-header fields allow the client to pass additional information about the request, and about the client itself, 645 654 to the server. These fields act as request modifiers, with semantics equivalent to the parameters on a programming language 646 655 method invocation. 647 656 </p> 648 <div id="rfc.figure.u. 2"></div><pre class="inline"><span id="rfc.iref.g.3"></span> request-header = Accept ; <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 5.1</a>649 | Accept-Charset ; <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 5.2</a>650 | Accept-Encoding ; <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 5.3</a>651 | Accept-Language ; <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 5.4</a>652 | Authorization ; <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 3.1</a>653 | Expect ; <a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section 9.2</a>654 | From ; <a href="#header.from" id="rfc.xref.header.from.1" title="From">Section 9.3</a>655 | Host ; <a href="#Part1" id="rfc.xref.Part1. 2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 8.4</a>656 | If-Match ; <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 6.2</a>657 | If-Modified-Since ; <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 6.3</a>658 | If-None-Match ; <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 6.4</a>659 | If-Range ; <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a>660 | If-Unmodified-Since ; <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 6.5</a>661 | Max-Forwards ; <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section 9.5</a>662 | Proxy-Authorization ; <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 3.3</a>663 | Range ; <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.range" title="Range">Section 5.4</a>664 | Referer ; <a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section 9.6</a>665 | TE ; <a href="#Part1" id="rfc.xref.Part1. 3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>666 | User-Agent ; <a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section 9.9</a>667 </pre><p id="rfc.section. 3.p.3">Request-header field names can be extended reliably only in combination with a change in the protocol version. However, new657 <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.3"></span> request-header = Accept ; <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 6.1</a> 658 | Accept-Charset ; <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 6.2</a> 659 | Accept-Encoding ; <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 6.3</a> 660 | Accept-Language ; <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 6.4</a> 661 | Authorization ; <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> 662 | Expect ; <a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section 10.2</a> 663 | From ; <a href="#header.from" id="rfc.xref.header.from.1" title="From">Section 10.3</a> 664 | Host ; <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 8.4</a> 665 | If-Match ; <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 7.2</a> 666 | If-Modified-Since ; <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 7.3</a> 667 | If-None-Match ; <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 7.4</a> 668 | If-Range ; <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.if-range" title="If-Range">Section 6.3</a> 669 | If-Unmodified-Since ; <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 7.5</a> 670 | Max-Forwards ; <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section 10.5</a> 671 | Proxy-Authorization ; <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a> 672 | Range ; <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.range" title="Range">Section 6.4</a> 673 | Referer ; <a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section 10.6</a> 674 | TE ; <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a> 675 | User-Agent ; <a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section 10.9</a> 676 </pre><p id="rfc.section.4.p.3">Request-header field names can be extended reliably only in combination with a change in the protocol version. However, new 668 677 or experimental header fields <em class="bcp14">MAY</em> be given the semantics of request-header fields if all parties in the communication recognize them to be request-header fields. 669 678 Unrecognized header fields are treated as entity-header fields. 670 679 </p> 671 <h1 id="rfc.section. 4"><a href="#rfc.section.4">4.</a> <a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h1>672 <p id="rfc.section. 4.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. The status673 codes listed below are defined in <a href="#status.codes" title="Status Code Definitions">Section 8</a>. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use680 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h1> 681 <p id="rfc.section.5.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. The status 682 codes listed below are defined in <a href="#status.codes" title="Status Code Definitions">Section 9</a>. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use 674 683 by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason-Phrase. 675 684 </p> 676 <p id="rfc.section. 4.p.2">The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase's,685 <p id="rfc.section.5.p.2">The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase's, 677 686 are presented below. The reason phrases listed here are only recommendations -- they <em class="bcp14">MAY</em> be replaced by local equivalents without affecting the protocol. 678 687 </p> 679 <div id="rfc.figure.u. 3"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span> Status-Code =680 "100" ; <a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section 8.1.1</a>: Continue681 | "101" ; <a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section 8.1.2</a>: Switching Protocols682 | "200" ; <a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section 8.2.1</a>: OK683 | "201" ; <a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section 8.2.2</a>: Created684 | "202" ; <a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section 8.2.3</a>: Accepted685 | "203" ; <a href="#status.203" id="rfc.xref.status.203.1" title="203 Non-Authoritative Information">Section 8.2.4</a>: Non-Authoritative Information686 | "204" ; <a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section 8.2.5</a>: No Content687 | "205" ; <a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section 8.2.6</a>: Reset Content688 | "206" ; <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section 8.2.7</a>: Partial Content689 | "300" ; <a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section 8.3.1</a>: Multiple Choices690 | "301" ; <a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section 8.3.2</a>: Moved Permanently691 | "302" ; <a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section 8.3.3</a>: Found692 | "303" ; <a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section 8.3.4</a>: See Other693 | "304" ; <a href="#status.304" id="rfc.xref.status.304.1" title="304 Not Modified">Section 8.3.5</a>: Not Modified694 | "305" ; <a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section 8.3.6</a>: Use Proxy695 | "307" ; <a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section 8.3.8</a>: Temporary Redirect696 | "400" ; <a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section 8.4.1</a>: Bad Request697 | "401" ; <a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section 8.4.2</a>: Unauthorized698 | "402" ; <a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section 8.4.3</a>: Payment Required699 | "403" ; <a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section 8.4.4</a>: Forbidden700 | "404" ; <a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section 8.4.5</a>: Not Found701 | "405" ; <a href="#status.405" id="rfc.xref.status.405.1" title="405 Method Not Allowed">Section 8.4.6</a>: Method Not Allowed702 | "406" ; <a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section 8.4.7</a>: Not Acceptable703 | "407" ; <a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section 8.4.8</a>: Proxy Authentication Required704 | "408" ; <a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section 8.4.9</a>: Request Time-out705 | "409" ; <a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section 8.4.10</a>: Conflict706 | "410" ; <a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section 8.4.11</a>: Gone707 | "411" ; <a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section 8.4.12</a>: Length Required708 | "412" ; <a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section 8.4.13</a>: Precondition Failed709 | "413" ; <a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Entity Too Large">Section 8.4.14</a>: Request Entity Too Large710 | "414" ; <a href="#status.414" id="rfc.xref.status.414.1" title="414 Request-URI Too Long">Section 8.4.15</a>: Request-URI Too Large711 | "415" ; <a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section 8.4.16</a>: Unsupported Media Type712 | "416" ; <a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section 8.4.17</a>: Requested range not satisfiable713 | "417" ; <a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section 8.4.18</a>: Expectation Failed714 | "500" ; <a href="#status.500" id="rfc.xref.status.500.1" title="500 Internal Server Error">Section 8.5.1</a>: Internal Server Error715 | "501" ; <a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section 8.5.2</a>: Not Implemented716 | "502" ; <a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section 8.5.3</a>: Bad Gateway717 | "503" ; <a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section 8.5.4</a>: Service Unavailable718 | "504" ; <a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section 8.5.5</a>: Gateway Time-out719 | "505" ; <a href="#status.505" id="rfc.xref.status.505.1" title="505 HTTP Version Not Supported">Section 8.5.6</a>: HTTP Version not supported688 <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span> Status-Code = 689 "100" ; <a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section 9.1.1</a>: Continue 690 | "101" ; <a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section 9.1.2</a>: Switching Protocols 691 | "200" ; <a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section 9.2.1</a>: OK 692 | "201" ; <a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section 9.2.2</a>: Created 693 | "202" ; <a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section 9.2.3</a>: Accepted 694 | "203" ; <a href="#status.203" id="rfc.xref.status.203.1" title="203 Non-Authoritative Information">Section 9.2.4</a>: Non-Authoritative Information 695 | "204" ; <a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section 9.2.5</a>: No Content 696 | "205" ; <a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section 9.2.6</a>: Reset Content 697 | "206" ; <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section 9.2.7</a>: Partial Content 698 | "300" ; <a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section 9.3.1</a>: Multiple Choices 699 | "301" ; <a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section 9.3.2</a>: Moved Permanently 700 | "302" ; <a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section 9.3.3</a>: Found 701 | "303" ; <a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section 9.3.4</a>: See Other 702 | "304" ; <a href="#status.304" id="rfc.xref.status.304.1" title="304 Not Modified">Section 9.3.5</a>: Not Modified 703 | "305" ; <a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section 9.3.6</a>: Use Proxy 704 | "307" ; <a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section 9.3.8</a>: Temporary Redirect 705 | "400" ; <a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section 9.4.1</a>: Bad Request 706 | "401" ; <a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section 9.4.2</a>: Unauthorized 707 | "402" ; <a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section 9.4.3</a>: Payment Required 708 | "403" ; <a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section 9.4.4</a>: Forbidden 709 | "404" ; <a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section 9.4.5</a>: Not Found 710 | "405" ; <a href="#status.405" id="rfc.xref.status.405.1" title="405 Method Not Allowed">Section 9.4.6</a>: Method Not Allowed 711 | "406" ; <a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section 9.4.7</a>: Not Acceptable 712 | "407" ; <a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section 9.4.8</a>: Proxy Authentication Required 713 | "408" ; <a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section 9.4.9</a>: Request Time-out 714 | "409" ; <a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section 9.4.10</a>: Conflict 715 | "410" ; <a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section 9.4.11</a>: Gone 716 | "411" ; <a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section 9.4.12</a>: Length Required 717 | "412" ; <a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section 9.4.13</a>: Precondition Failed 718 | "413" ; <a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Entity Too Large">Section 9.4.14</a>: Request Entity Too Large 719 | "414" ; <a href="#status.414" id="rfc.xref.status.414.1" title="414 Request-URI Too Long">Section 9.4.15</a>: Request-URI Too Large 720 | "415" ; <a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section 9.4.16</a>: Unsupported Media Type 721 | "416" ; <a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section 9.4.17</a>: Requested range not satisfiable 722 | "417" ; <a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section 9.4.18</a>: Expectation Failed 723 | "500" ; <a href="#status.500" id="rfc.xref.status.500.1" title="500 Internal Server Error">Section 9.5.1</a>: Internal Server Error 724 | "501" ; <a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section 9.5.2</a>: Not Implemented 725 | "502" ; <a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section 9.5.3</a>: Bad Gateway 726 | "503" ; <a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section 9.5.4</a>: Service Unavailable 727 | "504" ; <a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section 9.5.5</a>: Gateway Time-out 728 | "505" ; <a href="#status.505" id="rfc.xref.status.505.1" title="505 HTTP Version Not Supported">Section 9.5.6</a>: HTTP Version not supported 720 729 | extension-code 721 730 722 731 extension-code = 3DIGIT 723 732 Reason-Phrase = *<TEXT, excluding CR, LF> 724 </pre><p id="rfc.section. 4.p.4">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes,733 </pre><p id="rfc.section.5.p.4">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes, 725 734 though such understanding is obviously desirable. However, applications <em class="bcp14">MUST</em> understand the class of any status code, as indicated by the first digit, and treat any unrecognized response as being equivalent 726 735 to the x00 status code of that class, with the exception that an unrecognized response <em class="bcp14">MUST NOT</em> be cached. For example, if an unrecognized status code of 431 is received by the client, it can safely assume that there was … … 728 737 which will explain the unusual status. 729 738 </p> 730 <h1 id="rfc.section. 5"><a href="#rfc.section.5">5.</a> <a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h1>731 <p id="rfc.section. 5.p.1">The response-header fields allow the server to pass additional information about the response which cannot be placed in the739 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h1> 740 <p id="rfc.section.6.p.1">The response-header fields allow the server to pass additional information about the response which cannot be placed in the 732 741 Status-Line. These header fields give information about the server and about further access to the resource identified by 733 742 the Request-URI. 734 743 </p> 735 <div id="rfc.figure.u. 4"></div><pre class="inline"><span id="rfc.iref.g.7"></span> response-header = Accept-Ranges ; <a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 5.1</a>736 | Age ; <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 1 5.1</a>737 | ETag ; <a href="#Part4" id="rfc.xref.Part4.5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a>738 | Location ; <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section 9.4</a>739 | Proxy-Authenticate ; <a href="#Part7" id="rfc.xref.Part7.3"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 3.2</a>740 | Retry-After ; <a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section 9.7</a>741 | Server ; <a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section 9.8</a>742 | Vary ; <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.vary" title="Vary">Section 1 5.5</a>743 | WWW-Authenticate ; <a href="#Part7" id="rfc.xref.Part7.4"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 3.4</a>744 </pre><p id="rfc.section. 5.p.3">Response-header field names can be extended reliably only in combination with a change in the protocol version. However, new744 <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.7"></span> response-header = Accept-Ranges ; <a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 6.1</a> 745 | Age ; <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 16.1</a> 746 | ETag ; <a href="#Part4" id="rfc.xref.Part4.5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a> 747 | Location ; <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section 10.4</a> 748 | Proxy-Authenticate ; <a href="#Part7" id="rfc.xref.Part7.3"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a> 749 | Retry-After ; <a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section 10.7</a> 750 | Server ; <a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section 10.8</a> 751 | Vary ; <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.vary" title="Vary">Section 16.5</a> 752 | WWW-Authenticate ; <a href="#Part7" id="rfc.xref.Part7.4"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a> 753 </pre><p id="rfc.section.6.p.3">Response-header field names can be extended reliably only in combination with a change in the protocol version. However, new 745 754 or experimental header fields <em class="bcp14">MAY</em> be given the semantics of response-header fields if all parties in the communication recognize them to be response-header 746 755 fields. Unrecognized header fields are treated as entity-header fields. 747 756 </p> 748 <h1 id="rfc.section. 6"><a href="#rfc.section.6">6.</a> <a id="entity" href="#entity">Entity</a></h1>749 <p id="rfc.section. 6.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer an entity if not otherwise restricted by the request method or response status code. An entity consists of entity-header757 <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="entity" href="#entity">Entity</a></h1> 758 <p id="rfc.section.7.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer an entity if not otherwise restricted by the request method or response status code. An entity consists of entity-header 750 759 fields and an entity-body, although some responses will only include the entity-headers. HTTP entity-body and entity-header 751 760 fields are defined in <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 752 761 </p> 753 <p id="rfc.section. 6.p.2">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure762 <p id="rfc.section.7.p.2">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure 754 763 safe and proper transfer of the message. 755 764 </p> 756 <h1 id="rfc.section. 7"><a href="#rfc.section.7">7.</a> <a id="method.definitions" href="#method.definitions">Method Definitions</a></h1>757 <p id="rfc.section. 7.p.1">The set of common methods for HTTP/1.1 is defined below. Although this set can be expanded, additional methods cannot be assumed765 <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="method.definitions" href="#method.definitions">Method Definitions</a></h1> 766 <p id="rfc.section.8.p.1">The set of common methods for HTTP/1.1 is defined below. Although this set can be expanded, additional methods cannot be assumed 758 767 to share the same semantics for separately extended clients and servers. 759 768 </p> 760 <h2 id="rfc.section. 7.1"><a href="#rfc.section.7.1">7.1</a> <a id="safe.and.idempotent" href="#safe.and.idempotent">Safe and Idempotent Methods</a></h2>761 <h3 id="rfc.section. 7.1.1"><a href="#rfc.section.7.1.1">7.1.1</a> <a id="safe.methods" href="#safe.methods">Safe Methods</a></h3>762 <p id="rfc.section. 7.1.1.p.1">Implementors should be aware that the software represents the user in their interactions over the Internet, and should be769 <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a> <a id="safe.and.idempotent" href="#safe.and.idempotent">Safe and Idempotent Methods</a></h2> 770 <h3 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a> <a id="safe.methods" href="#safe.methods">Safe Methods</a></h3> 771 <p id="rfc.section.8.1.1.p.1">Implementors should be aware that the software represents the user in their interactions over the Internet, and should be 763 772 careful to allow the user to be aware of any actions they might take which may have an unexpected significance to themselves 764 773 or others. 765 774 </p> 766 <p id="rfc.section. 7.1.1.p.2">In particular, the convention has been established that the GET and HEAD methods <em class="bcp14">SHOULD NOT</em> have the significance of taking an action other than retrieval. These methods ought to be considered "safe". This allows user775 <p id="rfc.section.8.1.1.p.2">In particular, the convention has been established that the GET and HEAD methods <em class="bcp14">SHOULD NOT</em> have the significance of taking an action other than retrieval. These methods ought to be considered "safe". This allows user 767 776 agents to represent other methods, such as POST, PUT and DELETE, in a special way, so that the user is made aware of the fact 768 777 that a possibly unsafe action is being requested. 769 778 </p> 770 <p id="rfc.section. 7.1.1.p.3">Naturally, it is not possible to ensure that the server does not generate side-effects as a result of performing a GET request;779 <p id="rfc.section.8.1.1.p.3">Naturally, it is not possible to ensure that the server does not generate side-effects as a result of performing a GET request; 771 780 in fact, some dynamic resources consider that a feature. The important distinction here is that the user did not request the 772 781 side-effects, so therefore cannot be held accountable for them. 773 782 </p> 774 <h3 id="rfc.section. 7.1.2"><a href="#rfc.section.7.1.2">7.1.2</a> <a id="idempotent.methods" href="#idempotent.methods">Idempotent Methods</a></h3>775 <p id="rfc.section. 7.1.2.p.1">Methods can also have the property of "idempotence" in that (aside from error or expiration issues) the side-effects of N783 <h3 id="rfc.section.8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a> <a id="idempotent.methods" href="#idempotent.methods">Idempotent Methods</a></h3> 784 <p id="rfc.section.8.1.2.p.1">Methods can also have the property of "idempotence" in that (aside from error or expiration issues) the side-effects of N 776 785 > 0 identical requests is the same as for a single request. The methods GET, HEAD, PUT and DELETE share this property. Also, 777 786 the methods OPTIONS and TRACE <em class="bcp14">SHOULD NOT</em> have side effects, and so are inherently idempotent. 778 787 </p> 779 <p id="rfc.section. 7.1.2.p.2">However, it is possible that a sequence of several requests is non-idempotent, even if all of the methods executed in that788 <p id="rfc.section.8.1.2.p.2">However, it is possible that a sequence of several requests is non-idempotent, even if all of the methods executed in that 780 789 sequence are idempotent. (A sequence is idempotent if a single execution of the entire sequence always yields a result that 781 790 is not changed by a reexecution of all, or part, of that sequence.) For example, a sequence is non-idempotent if its result 782 791 depends on a value that is later modified in the same sequence. 783 792 </p> 784 <p id="rfc.section. 7.1.2.p.3">A sequence that never has side effects is idempotent, by definition (provided that no concurrent operations are being executed793 <p id="rfc.section.8.1.2.p.3">A sequence that never has side effects is idempotent, by definition (provided that no concurrent operations are being executed 785 794 on the same set of resources). 786 795 </p> 787 796 <div id="rfc.iref.o.1"></div> 788 797 <div id="rfc.iref.m.1"></div> 789 <h2 id="rfc.section. 7.2"><a href="#rfc.section.7.2">7.2</a> <a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h2>790 <p id="rfc.section. 7.2.p.1">The OPTIONS method represents a request for information about the communication options available on the request/response798 <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a> <a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h2> 799 <p id="rfc.section.8.2.p.1">The OPTIONS method represents a request for information about the communication options available on the request/response 791 800 chain identified by the Request-URI. This method allows the client to determine the options and/or requirements associated 792 801 with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval. 793 802 </p> 794 <p id="rfc.section. 7.2.p.2">Responses to this method are not cacheable.</p>795 <p id="rfc.section. 7.2.p.3">If the OPTIONS request includes an entity-body (as indicated by the presence of Content-Length or Transfer-Encoding), then803 <p id="rfc.section.8.2.p.2">Responses to this method are not cacheable.</p> 804 <p id="rfc.section.8.2.p.3">If the OPTIONS request includes an entity-body (as indicated by the presence of Content-Length or Transfer-Encoding), then 796 805 the media type <em class="bcp14">MUST</em> be indicated by a Content-Type field. Although this specification does not define any use for such a body, future extensions 797 806 to HTTP might use the OPTIONS body to make more detailed queries on the server. A server that does not support such an extension <em class="bcp14">MAY</em> discard the request body. 798 807 </p> 799 <p id="rfc.section. 7.2.p.4">If the Request-URI is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to808 <p id="rfc.section.8.2.p.4">If the Request-URI is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to 800 809 a specific resource. Since a server's communication options typically depend on the resource, the "*" request is only useful 801 810 as a "ping" or "no-op" type of method; it does nothing beyond allowing the client to test the capabilities of the server. 802 811 For example, this can be used to test a proxy for HTTP/1.1 compliance (or lack thereof). 803 812 </p> 804 <p id="rfc.section. 7.2.p.5">If the Request-URI is not an asterisk, the OPTIONS request applies only to the options that are available when communicating813 <p id="rfc.section.8.2.p.5">If the Request-URI is not an asterisk, the OPTIONS request applies only to the options that are available when communicating 805 814 with that resource. 806 815 </p> 807 <p id="rfc.section. 7.2.p.6">A 200 response <em class="bcp14">SHOULD</em> include any header fields that indicate optional features implemented by the server and applicable to that resource (e.g.,816 <p id="rfc.section.8.2.p.6">A 200 response <em class="bcp14">SHOULD</em> include any header fields that indicate optional features implemented by the server and applicable to that resource (e.g., 808 817 Allow), possibly including extensions not defined by this specification. The response body, if any, <em class="bcp14">SHOULD</em> also include information about the communication options. The format for such a body is not defined by this specification, 809 818 but might be defined by future extensions to HTTP. Content negotiation <em class="bcp14">MAY</em> be used to select the appropriate response format. If no response body is included, the response <em class="bcp14">MUST</em> include a Content-Length field with a field-value of "0". 810 819 </p> 811 <p id="rfc.section. 7.2.p.7">The Max-Forwards request-header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain. When a proxy receives an OPTIONS request on an absoluteURI for which820 <p id="rfc.section.8.2.p.7">The Max-Forwards request-header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain. When a proxy receives an OPTIONS request on an absoluteURI for which 812 821 request forwarding is permitted, the proxy <em class="bcp14">MUST</em> check for a Max-Forwards field. If the Max-Forwards field-value is zero ("0"), the proxy <em class="bcp14">MUST NOT</em> forward the message; instead, the proxy <em class="bcp14">SHOULD</em> respond with its own communication options. If the Max-Forwards field-value is an integer greater than zero, the proxy <em class="bcp14">MUST</em> decrement the field-value when it forwards the request. If no Max-Forwards field is present in the request, then the forwarded 813 822 request <em class="bcp14">MUST NOT</em> include a Max-Forwards field. … … 815 824 <div id="rfc.iref.g.8"></div> 816 825 <div id="rfc.iref.m.2"></div> 817 <h2 id="rfc.section. 7.3"><a href="#rfc.section.7.3">7.3</a> <a id="GET" href="#GET">GET</a></h2>818 <p id="rfc.section. 7.3.p.1">The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI. If the Request-URI826 <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a> <a id="GET" href="#GET">GET</a></h2> 827 <p id="rfc.section.8.3.p.1">The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI. If the Request-URI 819 828 refers to a data-producing process, it is the produced data which shall be returned as the entity in the response and not 820 829 the source text of the process, unless that text happens to be the output of the process. 821 830 </p> 822 <p id="rfc.section. 7.3.p.2">The semantics of the GET method change to a "conditional GET" if the request message includes an If-Modified-Since, If-Unmodified-Since,831 <p id="rfc.section.8.3.p.2">The semantics of the GET method change to a "conditional GET" if the request message includes an If-Modified-Since, If-Unmodified-Since, 823 832 If-Match, If-None-Match, or If-Range header field. A conditional GET method requests that the entity be transferred only under 824 833 the circumstances described by the conditional header field(s). The conditional GET method is intended to reduce unnecessary … … 826 835 held by the client. 827 836 </p> 828 <p id="rfc.section. 7.3.p.3">The semantics of the GET method change to a "partial GET" if the request message includes a Range header field. A partial829 GET requests that only part of the entity be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The partial GET method is intended to reduce unnecessary network usage by allowing partially-retrieved entities to be completed837 <p id="rfc.section.8.3.p.3">The semantics of the GET method change to a "partial GET" if the request message includes a Range header field. A partial 838 GET requests that only part of the entity be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 6.4</a> of <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The partial GET method is intended to reduce unnecessary network usage by allowing partially-retrieved entities to be completed 830 839 without transferring data already held by the client. 831 840 </p> 832 <p id="rfc.section. 7.3.p.4">The response to a GET request is cacheable if and only if it meets the requirements for HTTP caching described in <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.833 </p> 834 <p id="rfc.section. 7.3.p.5">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section 11.2</a> for security considerations when used for forms.841 <p id="rfc.section.8.3.p.4">The response to a GET request is cacheable if and only if it meets the requirements for HTTP caching described in <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. 842 </p> 843 <p id="rfc.section.8.3.p.5">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section 12.2</a> for security considerations when used for forms. 835 844 </p> 836 845 <div id="rfc.iref.h.1"></div> 837 846 <div id="rfc.iref.m.3"></div> 838 <h2 id="rfc.section. 7.4"><a href="#rfc.section.7.4">7.4</a> <a id="HEAD" href="#HEAD">HEAD</a></h2>839 <p id="rfc.section. 7.4.p.1">The HEAD method is identical to GET except that the server <em class="bcp14">MUST NOT</em> return a message-body in the response. The metainformation contained in the HTTP headers in response to a HEAD request <em class="bcp14">SHOULD</em> be identical to the information sent in response to a GET request. This method can be used for obtaining metainformation about847 <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a> <a id="HEAD" href="#HEAD">HEAD</a></h2> 848 <p id="rfc.section.8.4.p.1">The HEAD method is identical to GET except that the server <em class="bcp14">MUST NOT</em> return a message-body in the response. The metainformation contained in the HTTP headers in response to a HEAD request <em class="bcp14">SHOULD</em> be identical to the information sent in response to a GET request. This method can be used for obtaining metainformation about 840 849 the entity implied by the request without transferring the entity-body itself. This method is often used for testing hypertext 841 850 links for validity, accessibility, and recent modification. 842 851 </p> 843 <p id="rfc.section. 7.4.p.2">The response to a HEAD request <em class="bcp14">MAY</em> be cacheable in the sense that the information contained in the response <em class="bcp14">MAY</em> be used to update a previously cached entity from that resource. If the new field values indicate that the cached entity differs852 <p id="rfc.section.8.4.p.2">The response to a HEAD request <em class="bcp14">MAY</em> be cacheable in the sense that the information contained in the response <em class="bcp14">MAY</em> be used to update a previously cached entity from that resource. If the new field values indicate that the cached entity differs 844 853 from the current entity (as would be indicated by a change in Content-Length, Content-MD5, ETag or Last-Modified), then the 845 854 cache <em class="bcp14">MUST</em> treat the cache entry as stale. … … 847 856 <div id="rfc.iref.p.1"></div> 848 857 <div id="rfc.iref.m.4"></div> 849 <h2 id="rfc.section. 7.5"><a href="#rfc.section.7.5">7.5</a> <a id="POST" href="#POST">POST</a></h2>850 <p id="rfc.section. 7.5.p.1">The POST method is used to request that the origin server accept the entity enclosed in the request as data to be processed858 <h2 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a> <a id="POST" href="#POST">POST</a></h2> 859 <p id="rfc.section.8.5.p.1">The POST method is used to request that the origin server accept the entity enclosed in the request as data to be processed 851 860 by the resource identified by the Request-URI in the Request-Line. POST is designed to allow a uniform method to cover the 852 861 following functions: … … 858 867 <li>Extending a database through an append operation.</li> 859 868 </ul> 860 <p id="rfc.section. 7.5.p.2">The actual function performed by the POST method is determined by the server and is usually dependent on the Request-URI.</p>861 <p id="rfc.section. 7.5.p.3">The action performed by the POST method might not result in a resource that can be identified by a URI. In this case, either869 <p id="rfc.section.8.5.p.2">The actual function performed by the POST method is determined by the server and is usually dependent on the Request-URI.</p> 870 <p id="rfc.section.8.5.p.3">The action performed by the POST method might not result in a resource that can be identified by a URI. In this case, either 862 871 200 (OK) or 204 (No Content) is the appropriate response status, depending on whether or not the response includes an entity 863 872 that describes the result. 864 873 </p> 865 <p id="rfc.section. 7.5.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be 201 (Created) and contain an entity which describes the status of the request and refers to the new resource, and a Location866 header (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section 9.4</a>).867 </p> 868 <p id="rfc.section. 7.5.p.5">Responses to this method are not cacheable, unless the response includes appropriate Cache-Control or Expires header fields.874 <p id="rfc.section.8.5.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be 201 (Created) and contain an entity which describes the status of the request and refers to the new resource, and a Location 875 header (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section 10.4</a>). 876 </p> 877 <p id="rfc.section.8.5.p.5">Responses to this method are not cacheable, unless the response includes appropriate Cache-Control or Expires header fields. 869 878 However, the 303 (See Other) response can be used to direct the user agent to retrieve a cacheable resource. 870 879 </p> 871 880 <div id="rfc.iref.p.2"></div> 872 881 <div id="rfc.iref.m.5"></div> 873 <h2 id="rfc.section. 7.6"><a href="#rfc.section.7.6">7.6</a> <a id="PUT" href="#PUT">PUT</a></h2>874 <p id="rfc.section. 7.6.p.1">The PUT method requests that the enclosed entity be stored under the supplied Request-URI. If the Request-URI refers to an882 <h2 id="rfc.section.8.6"><a href="#rfc.section.8.6">8.6</a> <a id="PUT" href="#PUT">PUT</a></h2> 883 <p id="rfc.section.8.6.p.1">The PUT method requests that the enclosed entity be stored under the supplied Request-URI. If the Request-URI refers to an 875 884 already existing resource, the enclosed entity <em class="bcp14">SHOULD</em> be considered as a modified version of the one residing on the origin server. If the Request-URI does not point to an existing 876 885 resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create … … 879 888 an appropriate error response <em class="bcp14">SHOULD</em> be given that reflects the nature of the problem. The recipient of the entity <em class="bcp14">MUST NOT</em> ignore any Content-* (e.g. Content-Range) headers that it does not understand or implement and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases. 880 889 </p> 881 <p id="rfc.section. 7.6.p.2">If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.882 </p> 883 <p id="rfc.section. 7.6.p.3">The fundamental difference between the POST and PUT requests is reflected in the different meaning of the Request-URI. The890 <p id="rfc.section.8.6.p.2">If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable. 891 </p> 892 <p id="rfc.section.8.6.p.3">The fundamental difference between the POST and PUT requests is reflected in the different meaning of the Request-URI. The 884 893 URI in a POST request identifies the resource that will handle the enclosed entity. That resource might be a data-accepting 885 894 process, a gateway to some other protocol, or a separate entity that accepts annotations. In contrast, the URI in a PUT request … … 887 896 it <em class="bcp14">MUST</em> send a 301 (Moved Permanently) response; the user agent <em class="bcp14">MAY</em> then make its own decision regarding whether or not to redirect the request. 888 897 </p> 889 <p id="rfc.section. 7.6.p.4">A single resource <em class="bcp14">MAY</em> be identified by many different URIs. For example, an article might have a URI for identifying "the current version" which898 <p id="rfc.section.8.6.p.4">A single resource <em class="bcp14">MAY</em> be identified by many different URIs. For example, an article might have a URI for identifying "the current version" which 890 899 is separate from the URI identifying each particular version. In this case, a PUT request on a general URI might result in 891 900 several other URIs being defined by the origin server. 892 901 </p> 893 <p id="rfc.section. 7.6.p.5">HTTP/1.1 does not define how a PUT method affects the state of an origin server.</p>894 <p id="rfc.section. 7.6.p.6">Unless otherwise specified for a particular entity-header, the entity-headers in the PUT request <em class="bcp14">SHOULD</em> be applied to the resource created or modified by the PUT.902 <p id="rfc.section.8.6.p.5">HTTP/1.1 does not define how a PUT method affects the state of an origin server.</p> 903 <p id="rfc.section.8.6.p.6">Unless otherwise specified for a particular entity-header, the entity-headers in the PUT request <em class="bcp14">SHOULD</em> be applied to the resource created or modified by the PUT. 895 904 </p> 896 905 <div id="rfc.iref.d.1"></div> 897 906 <div id="rfc.iref.m.6"></div> 898 <h2 id="rfc.section. 7.7"><a href="#rfc.section.7.7">7.7</a> <a id="DELETE" href="#DELETE">DELETE</a></h2>899 <p id="rfc.section. 7.7.p.1">The DELETE method requests that the origin server delete the resource identified by the Request-URI. This method <em class="bcp14">MAY</em> be overridden by human intervention (or other means) on the origin server. The client cannot be guaranteed that the operation907 <h2 id="rfc.section.8.7"><a href="#rfc.section.8.7">8.7</a> <a id="DELETE" href="#DELETE">DELETE</a></h2> 908 <p id="rfc.section.8.7.p.1">The DELETE method requests that the origin server delete the resource identified by the Request-URI. This method <em class="bcp14">MAY</em> be overridden by human intervention (or other means) on the origin server. The client cannot be guaranteed that the operation 900 909 has been carried out, even if the status code returned from the origin server indicates that the action has been completed 901 910 successfully. However, the server <em class="bcp14">SHOULD NOT</em> indicate success unless, at the time the response is given, it intends to delete the resource or move it to an inaccessible 902 911 location. 903 912 </p> 904 <p id="rfc.section. 7.7.p.2">A successful response <em class="bcp14">SHOULD</em> be 200 (OK) if the response includes an entity describing the status, 202 (Accepted) if the action has not yet been enacted,913 <p id="rfc.section.8.7.p.2">A successful response <em class="bcp14">SHOULD</em> be 200 (OK) if the response includes an entity describing the status, 202 (Accepted) if the action has not yet been enacted, 905 914 or 204 (No Content) if the action has been enacted but the response does not include an entity. 906 915 </p> 907 <p id="rfc.section. 7.7.p.3">If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.916 <p id="rfc.section.8.7.p.3">If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable. 908 917 </p> 909 918 <div id="rfc.iref.t.1"></div> 910 919 <div id="rfc.iref.m.7"></div> 911 <h2 id="rfc.section. 7.8"><a href="#rfc.section.7.8">7.8</a> <a id="TRACE" href="#TRACE">TRACE</a></h2>912 <p id="rfc.section. 7.8.p.1">The TRACE method is used to invoke a remote, application-layer loop-back of the request message. The final recipient of the920 <h2 id="rfc.section.8.8"><a href="#rfc.section.8.8">8.8</a> <a id="TRACE" href="#TRACE">TRACE</a></h2> 921 <p id="rfc.section.8.8.p.1">The TRACE method is used to invoke a remote, application-layer loop-back of the request message. The final recipient of the 913 922 request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the entity-body of a 200 (OK) response. The final recipient is either the 914 origin server or the first proxy or gateway to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section 9.5</a>). A TRACE request <em class="bcp14">MUST NOT</em> include an entity.915 </p> 916 <p id="rfc.section. 7.8.p.2">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing917 or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1. 5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the923 origin server or the first proxy or gateway to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section 10.5</a>). A TRACE request <em class="bcp14">MUST NOT</em> include an entity. 924 </p> 925 <p id="rfc.section.8.8.p.2">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing 926 or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the 918 927 client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an 919 928 infinite loop. 920 929 </p> 921 <p id="rfc.section. 7.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> contain the entire request message in the entity-body, with a Content-Type of "message/http". Responses to this method <em class="bcp14">MUST NOT</em> be cached.930 <p id="rfc.section.8.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> contain the entire request message in the entity-body, with a Content-Type of "message/http". Responses to this method <em class="bcp14">MUST NOT</em> be cached. 922 931 </p> 923 932 <div id="rfc.iref.c.1"></div> 924 933 <div id="rfc.iref.m.8"></div> 925 <h2 id="rfc.section. 7.9"><a href="#rfc.section.7.9">7.9</a> <a id="CONNECT" href="#CONNECT">CONNECT</a></h2>926 <p id="rfc.section. 7.9.p.1">This specification reserves the method name CONNECT for use with a proxy that can dynamically switch to being a tunnel (e.g.934 <h2 id="rfc.section.8.9"><a href="#rfc.section.8.9">8.9</a> <a id="CONNECT" href="#CONNECT">CONNECT</a></h2> 935 <p id="rfc.section.8.9.p.1">This specification reserves the method name CONNECT for use with a proxy that can dynamically switch to being a tunnel (e.g. 927 936 SSL tunneling <a href="#Luo1998" id="rfc.xref.Luo1998.1"><cite title="Tunneling TCP based protocols through Web proxy servers">[Luo1998]</cite></a>). 928 937 </p> 929 <h1 id="rfc.section. 8"><a href="#rfc.section.8">8.</a> <a id="status.codes" href="#status.codes">Status Code Definitions</a></h1>930 <p id="rfc.section. 8.p.1">Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required938 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="status.codes" href="#status.codes">Status Code Definitions</a></h1> 939 <p id="rfc.section.9.p.1">Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required 931 940 in the response. 932 941 </p> 933 <h2 id="rfc.section. 8.1"><a href="#rfc.section.8.1">8.1</a> <a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>934 <p id="rfc.section. 8.1.p.1">This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is942 <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a> <a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2> 943 <p id="rfc.section.9.1.p.1">This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is 935 944 terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any 936 945 1xx status codes, servers <em class="bcp14">MUST NOT</em> send a 1xx response to an HTTP/1.0 client except under experimental conditions. 937 946 </p> 938 <p id="rfc.section. 8.1.p.2">A client <em class="bcp14">MUST</em> be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100947 <p id="rfc.section.9.1.p.2">A client <em class="bcp14">MUST</em> be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 939 948 (Continue) status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent. 940 949 </p> 941 <p id="rfc.section. 8.1.p.3">Proxies <em class="bcp14">MUST</em> forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself950 <p id="rfc.section.9.1.p.3">Proxies <em class="bcp14">MUST</em> forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself 942 951 requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards 943 952 a request, then it need not forward the corresponding 100 (Continue) response(s).) … … 945 954 <div id="rfc.iref.23"></div> 946 955 <div id="rfc.iref.s.1"></div> 947 <h3 id="rfc.section. 8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a> <a id="status.100" href="#status.100">100 Continue</a></h3>948 <p id="rfc.section. 8.1.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been956 <h3 id="rfc.section.9.1.1"><a href="#rfc.section.9.1.1">9.1.1</a> <a id="status.100" href="#status.100">100 Continue</a></h3> 957 <p id="rfc.section.9.1.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been 949 958 received and has not yet been rejected by the server. The client <em class="bcp14">SHOULD</em> continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The 950 server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1. 6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.959 server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code. 951 960 </p> 952 961 <div id="rfc.iref.24"></div> 953 962 <div id="rfc.iref.s.2"></div> 954 <h3 id="rfc.section. 8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a> <a id="status.101" href="#status.101">101 Switching Protocols</a></h3>955 <p id="rfc.section. 8.1.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined963 <h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a> <a id="status.101" href="#status.101">101 Switching Protocols</a></h3> 964 <p id="rfc.section.9.1.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p5-range.html#header.range" title="Range">Section 6.4</a> of <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined 956 965 by the response's Upgrade header field immediately after the empty line which terminates the 101 response. 957 966 </p> 958 <p id="rfc.section. 8.1.2.p.2">The protocol <em class="bcp14">SHOULD</em> be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over967 <p id="rfc.section.9.1.2.p.2">The protocol <em class="bcp14">SHOULD</em> be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over 959 968 older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use 960 969 such features. 961 970 </p> 962 <h2 id="rfc.section. 8.2"><a href="#rfc.section.8.2">8.2</a> <a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>963 <p id="rfc.section. 8.2.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>971 <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a> <a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2> 972 <p id="rfc.section.9.2.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p> 964 973 <div id="rfc.iref.25"></div> 965 974 <div id="rfc.iref.s.3"></div> 966 <h3 id="rfc.section. 8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a> <a id="status.200" href="#status.200">200 OK</a></h3>967 <p id="rfc.section. 8.2.1.p.1">The request has succeeded. The information returned with the response is dependent on the method used in the request, for975 <h3 id="rfc.section.9.2.1"><a href="#rfc.section.9.2.1">9.2.1</a> <a id="status.200" href="#status.200">200 OK</a></h3> 976 <p id="rfc.section.9.2.1.p.1">The request has succeeded. The information returned with the response is dependent on the method used in the request, for 968 977 example: 969 978 </p> … … 980 989 <div id="rfc.iref.26"></div> 981 990 <div id="rfc.iref.s.4"></div> 982 <h3 id="rfc.section. 8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a> <a id="status.201" href="#status.201">201 Created</a></h3>983 <p id="rfc.section. 8.2.2.p.1">The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced991 <h3 id="rfc.section.9.2.2"><a href="#rfc.section.9.2.2">9.2.2</a> <a id="status.201" href="#status.201">201 Created</a></h3> 992 <p id="rfc.section.9.2.2.p.1">The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced 984 993 by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header 985 994 field. The response <em class="bcp14">SHOULD</em> include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose … … 987 996 server <em class="bcp14">MUST</em> create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server <em class="bcp14">SHOULD</em> respond with 202 (Accepted) response instead. 988 997 </p> 989 <p id="rfc.section. 8.2.2.p.2">A 201 response <em class="bcp14">MAY</em> contain an ETag response header field indicating the current value of the entity tag for the requested variant just created,990 see <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a> of <a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.998 <p id="rfc.section.9.2.2.p.2">A 201 response <em class="bcp14">MAY</em> contain an ETag response header field indicating the current value of the entity tag for the requested variant just created, 999 see <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a> of <a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. 991 1000 </p> 992 1001 <div id="rfc.iref.27"></div> 993 1002 <div id="rfc.iref.s.5"></div> 994 <h3 id="rfc.section. 8.2.3"><a href="#rfc.section.8.2.3">8.2.3</a> <a id="status.202" href="#status.202">202 Accepted</a></h3>995 <p id="rfc.section. 8.2.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually1003 <h3 id="rfc.section.9.2.3"><a href="#rfc.section.9.2.3">9.2.3</a> <a id="status.202" href="#status.202">202 Accepted</a></h3> 1004 <p id="rfc.section.9.2.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually 996 1005 be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status 997 1006 code from an asynchronous operation such as this. 998 1007 </p> 999 <p id="rfc.section. 8.2.3.p.2">The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process1008 <p id="rfc.section.9.2.3.p.2">The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process 1000 1009 (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the 1001 1010 server persist until the process is completed. The entity returned with this response <em class="bcp14">SHOULD</em> include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the … … 1004 1013 <div id="rfc.iref.28"></div> 1005 1014 <div id="rfc.iref.s.6"></div> 1006 <h3 id="rfc.section. 8.2.4"><a href="#rfc.section.8.2.4">8.2.4</a> <a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>1007 <p id="rfc.section. 8.2.4.p.1">The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered1015 <h3 id="rfc.section.9.2.4"><a href="#rfc.section.9.2.4">9.2.4</a> <a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3> 1016 <p id="rfc.section.9.2.4.p.1">The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered 1008 1017 from a local or a third-party copy. The set presented <em class="bcp14">MAY</em> be a subset or superset of the original version. For example, including local annotation information about the resource might 1009 1018 result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only … … 1012 1021 <div id="rfc.iref.29"></div> 1013 1022 <div id="rfc.iref.s.7"></div> 1014 <h3 id="rfc.section. 8.2.5"><a href="#rfc.section.8.2.5">8.2.5</a> <a id="status.204" href="#status.204">204 No Content</a></h3>1015 <p id="rfc.section. 8.2.5.p.1">The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation.1023 <h3 id="rfc.section.9.2.5"><a href="#rfc.section.9.2.5">9.2.5</a> <a id="status.204" href="#status.204">204 No Content</a></h3> 1024 <p id="rfc.section.9.2.5.p.1">The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. 1016 1025 The response <em class="bcp14">MAY</em> include new or updated metainformation in the form of entity-headers, which if present <em class="bcp14">SHOULD</em> be associated with the requested variant. 1017 1026 </p> 1018 <p id="rfc.section. 8.2.5.p.2">If the client is a user agent, it <em class="bcp14">SHOULD NOT</em> change its document view from that which caused the request to be sent. This response is primarily intended to allow input1027 <p id="rfc.section.9.2.5.p.2">If the client is a user agent, it <em class="bcp14">SHOULD NOT</em> change its document view from that which caused the request to be sent. This response is primarily intended to allow input 1019 1028 for actions to take place without causing a change to the user agent's active document view, although any new or updated metainformation <em class="bcp14">SHOULD</em> be applied to the document currently in the user agent's active view. 1020 1029 </p> 1021 <p id="rfc.section. 8.2.5.p.3">The 204 response <em class="bcp14">MUST NOT</em> include a message-body, and thus is always terminated by the first empty line after the header fields.1030 <p id="rfc.section.9.2.5.p.3">The 204 response <em class="bcp14">MUST NOT</em> include a message-body, and thus is always terminated by the first empty line after the header fields. 1022 1031 </p> 1023 1032 <div id="rfc.iref.30"></div> 1024 1033 <div id="rfc.iref.s.8"></div> 1025 <h3 id="rfc.section. 8.2.6"><a href="#rfc.section.8.2.6">8.2.6</a> <a id="status.205" href="#status.205">205 Reset Content</a></h3>1026 <p id="rfc.section. 8.2.6.p.1">The server has fulfilled the request and the user agent <em class="bcp14">SHOULD</em> reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions1034 <h3 id="rfc.section.9.2.6"><a href="#rfc.section.9.2.6">9.2.6</a> <a id="status.205" href="#status.205">205 Reset Content</a></h3> 1035 <p id="rfc.section.9.2.6.p.1">The server has fulfilled the request and the user agent <em class="bcp14">SHOULD</em> reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions 1027 1036 to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate 1028 1037 another input action. The response <em class="bcp14">MUST NOT</em> include an entity. … … 1030 1039 <div id="rfc.iref.31"></div> 1031 1040 <div id="rfc.iref.s.9"></div> 1032 <h3 id="rfc.section. 8.2.7"><a href="#rfc.section.8.2.7">8.2.7</a> <a id="status.206" href="#status.206">206 Partial Content</a></h3>1033 <p id="rfc.section. 8.2.7.p.1">The server has fulfilled the partial GET request for the resource and the enclosed entity is a partial representation as defined1041 <h3 id="rfc.section.9.2.7"><a href="#rfc.section.9.2.7">9.2.7</a> <a id="status.206" href="#status.206">206 Partial Content</a></h3> 1042 <p id="rfc.section.9.2.7.p.1">The server has fulfilled the partial GET request for the resource and the enclosed entity is a partial representation as defined 1034 1043 in <a href="#Part5" id="rfc.xref.Part5.6"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. 1035 1044 </p> 1036 <h2 id="rfc.section. 8.3"><a href="#rfc.section.8.3">8.3</a> <a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>1037 <p id="rfc.section. 8.3.p.1">This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request.1045 <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a> <a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2> 1046 <p id="rfc.section.9.3.p.1">This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. 1038 1047 The action required <em class="bcp14">MAY</em> be carried out by the user agent without interaction with the user if and only if the method used in the second request is 1039 1048 GET or HEAD. A client <em class="bcp14">SHOULD</em> detect infinite redirection loops, since such loops generate network traffic for each redirection. … … 1046 1055 <div id="rfc.iref.32"></div> 1047 1056 <div id="rfc.iref.s.10"></div> 1048 <h3 id="rfc.section. 8.3.1"><a href="#rfc.section.8.3.1">8.3.1</a> <a id="status.300" href="#status.300">300 Multiple Choices</a></h3>1049 <p id="rfc.section. 8.3.1.p.1">The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven1050 negotiation information (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that1057 <h3 id="rfc.section.9.3.1"><a href="#rfc.section.9.3.1">9.3.1</a> <a id="status.300" href="#status.300">300 Multiple Choices</a></h3> 1058 <p id="rfc.section.9.3.1.p.1">The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven 1059 negotiation information (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that 1051 1060 location. 1052 1061 </p> 1053 <p id="rfc.section. 8.3.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose1062 <p id="rfc.section.9.3.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose 1054 1063 the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending 1055 1064 upon the format and the capabilities of the user agent, selection of the most appropriate choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection. 1056 1065 </p> 1057 <p id="rfc.section. 8.3.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the Location field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection. This response is cacheable unless indicated otherwise.1066 <p id="rfc.section.9.3.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the Location field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection. This response is cacheable unless indicated otherwise. 1058 1067 </p> 1059 1068 <div id="rfc.iref.33"></div> 1060 1069 <div id="rfc.iref.s.11"></div> 1061 <h3 id="rfc.section. 8.3.2"><a href="#rfc.section.8.3.2">8.3.2</a> <a id="status.301" href="#status.301">301 Moved Permanently</a></h3>1062 <p id="rfc.section. 8.3.2.p.1">The requested resource has been assigned a new permanent URI and any future references to this resource <em class="bcp14">SHOULD</em> use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI1070 <h3 id="rfc.section.9.3.2"><a href="#rfc.section.9.3.2">9.3.2</a> <a id="status.301" href="#status.301">301 Moved Permanently</a></h3> 1071 <p id="rfc.section.9.3.2.p.1">The requested resource has been assigned a new permanent URI and any future references to this resource <em class="bcp14">SHOULD</em> use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI 1063 1072 to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise. 1064 1073 </p> 1065 <p id="rfc.section. 8.3.2.p.2">The new permanent URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).1066 </p> 1067 <p id="rfc.section. 8.3.2.p.3">If the 301 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 7.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which1074 <p id="rfc.section.9.3.2.p.2">The new permanent URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s). 1075 </p> 1076 <p id="rfc.section.9.3.2.p.3">If the 301 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 8.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which 1068 1077 the request was issued. 1069 1078 </p> … … 1075 1084 <div id="rfc.iref.34"></div> 1076 1085 <div id="rfc.iref.s.12"></div> 1077 <h3 id="rfc.section. 8.3.3"><a href="#rfc.section.8.3.3">8.3.3</a> <a id="status.302" href="#status.302">302 Found</a></h3>1078 <p id="rfc.section. 8.3.3.p.1">The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the1086 <h3 id="rfc.section.9.3.3"><a href="#rfc.section.9.3.3">9.3.3</a> <a id="status.302" href="#status.302">302 Found</a></h3> 1087 <p id="rfc.section.9.3.3.p.1">The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the 1079 1088 client <em class="bcp14">SHOULD</em> continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires 1080 1089 header field. 1081 1090 </p> 1082 <p id="rfc.section. 8.3.3.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).1083 </p> 1084 <p id="rfc.section. 8.3.3.p.3">If the 302 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 7.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which1091 <p id="rfc.section.9.3.3.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s). 1092 </p> 1093 <p id="rfc.section.9.3.3.p.3">If the 302 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 8.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which 1085 1094 the request was issued. 1086 1095 </p> … … 1094 1103 <div id="rfc.iref.35"></div> 1095 1104 <div id="rfc.iref.s.13"></div> 1096 <h3 id="rfc.section. 8.3.4"><a href="#rfc.section.8.3.4">8.3.4</a> <a id="status.303" href="#status.303">303 See Other</a></h3>1097 <p id="rfc.section. 8.3.4.p.1">The response to the request can be found under a different URI and <em class="bcp14">SHOULD</em> be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script1105 <h3 id="rfc.section.9.3.4"><a href="#rfc.section.9.3.4">9.3.4</a> <a id="status.303" href="#status.303">303 See Other</a></h3> 1106 <p id="rfc.section.9.3.4.p.1">The response to the request can be found under a different URI and <em class="bcp14">SHOULD</em> be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script 1098 1107 to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested 1099 1108 resource. The 303 response <em class="bcp14">MUST NOT</em> be cached, but the response to the second (redirected) request might be cacheable. 1100 1109 </p> 1101 <p id="rfc.section. 8.3.4.p.2">The different URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).1110 <p id="rfc.section.9.3.4.p.2">The different URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s). 1102 1111 </p> 1103 1112 <dl class="empty"> … … 1108 1117 <div id="rfc.iref.36"></div> 1109 1118 <div id="rfc.iref.s.14"></div> 1110 <h3 id="rfc.section. 8.3.5"><a href="#rfc.section.8.3.5">8.3.5</a> <a id="status.304" href="#status.304">304 Not Modified</a></h3>1111 <p id="rfc.section. 8.3.5.p.1">The response to the request has not been modified since the conditions indicated by the client's conditional GET request,1119 <h3 id="rfc.section.9.3.5"><a href="#rfc.section.9.3.5">9.3.5</a> <a id="status.304" href="#status.304">304 Not Modified</a></h3> 1120 <p id="rfc.section.9.3.5.p.1">The response to the request has not been modified since the conditions indicated by the client's conditional GET request, 1112 1121 as defined in <a href="#Part4" id="rfc.xref.Part4.7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. 1113 1122 </p> 1114 1123 <div id="rfc.iref.37"></div> 1115 1124 <div id="rfc.iref.s.15"></div> 1116 <h3 id="rfc.section. 8.3.6"><a href="#rfc.section.8.3.6">8.3.6</a> <a id="status.305" href="#status.305">305 Use Proxy</a></h3>1117 <p id="rfc.section. 8.3.6.p.1">The requested resource <em class="bcp14">MUST</em> be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is1125 <h3 id="rfc.section.9.3.6"><a href="#rfc.section.9.3.6">9.3.6</a> <a id="status.305" href="#status.305">305 Use Proxy</a></h3> 1126 <p id="rfc.section.9.3.6.p.1">The requested resource <em class="bcp14">MUST</em> be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is 1118 1127 expected to repeat this single request via the proxy. 305 responses <em class="bcp14">MUST</em> only be generated by origin servers. 1119 1128 </p> … … 1125 1134 <div id="rfc.iref.38"></div> 1126 1135 <div id="rfc.iref.s.16"></div> 1127 <h3 id="rfc.section. 8.3.7"><a href="#rfc.section.8.3.7">8.3.7</a> <a id="status.306" href="#status.306">306 (Unused)</a></h3>1128 <p id="rfc.section. 8.3.7.p.1">The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.</p>1136 <h3 id="rfc.section.9.3.7"><a href="#rfc.section.9.3.7">9.3.7</a> <a id="status.306" href="#status.306">306 (Unused)</a></h3> 1137 <p id="rfc.section.9.3.7.p.1">The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.</p> 1129 1138 <div id="rfc.iref.39"></div> 1130 1139 <div id="rfc.iref.s.17"></div> 1131 <h3 id="rfc.section. 8.3.8"><a href="#rfc.section.8.3.8">8.3.8</a> <a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>1132 <p id="rfc.section. 8.3.8.p.1">The requested resource resides temporarily under a different URI. Since the redirection <em class="bcp14">MAY</em> be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires1140 <h3 id="rfc.section.9.3.8"><a href="#rfc.section.9.3.8">9.3.8</a> <a id="status.307" href="#status.307">307 Temporary Redirect</a></h3> 1141 <p id="rfc.section.9.3.8.p.1">The requested resource resides temporarily under a different URI. Since the redirection <em class="bcp14">MAY</em> be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires 1133 1142 header field. 1134 1143 </p> 1135 <p id="rfc.section. 8.3.8.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand1144 <p id="rfc.section.9.3.8.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand 1136 1145 the 307 status. Therefore, the note <em class="bcp14">SHOULD</em> contain the information necessary for a user to repeat the original request on the new URI. 1137 1146 </p> 1138 <p id="rfc.section. 8.3.8.p.3">If the 307 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 7.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which1147 <p id="rfc.section.9.3.8.p.3">If the 307 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section 8.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which 1139 1148 the request was issued. 1140 1149 </p> 1141 <h2 id="rfc.section. 8.4"><a href="#rfc.section.8.4">8.4</a> <a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2>1142 <p id="rfc.section. 8.4.p.1">The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD1150 <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a> <a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2> 1151 <p id="rfc.section.9.4.p.1">The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD 1143 1152 request, the server <em class="bcp14">SHOULD</em> include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. 1144 1153 These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included entity to the user. 1145 1154 </p> 1146 <p id="rfc.section. 8.4.p.2">If the client is sending data, a server implementation using TCP <em class="bcp14">SHOULD</em> be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes1155 <p id="rfc.section.9.4.p.2">If the client is sending data, a server implementation using TCP <em class="bcp14">SHOULD</em> be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes 1147 1156 the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send 1148 1157 a reset packet to the client, which may erase the client's unacknowledged input buffers before they can be read and interpreted … … 1151 1160 <div id="rfc.iref.40"></div> 1152 1161 <div id="rfc.iref.s.18"></div> 1153 <h3 id="rfc.section. 8.4.1"><a href="#rfc.section.8.4.1">8.4.1</a> <a id="status.400" href="#status.400">400 Bad Request</a></h3>1154 <p id="rfc.section. 8.4.1.p.1">The request could not be understood by the server due to malformed syntax. The client <em class="bcp14">SHOULD NOT</em> repeat the request without modifications.1162 <h3 id="rfc.section.9.4.1"><a href="#rfc.section.9.4.1">9.4.1</a> <a id="status.400" href="#status.400">400 Bad Request</a></h3> 1163 <p id="rfc.section.9.4.1.p.1">The request could not be understood by the server due to malformed syntax. The client <em class="bcp14">SHOULD NOT</em> repeat the request without modifications. 1155 1164 </p> 1156 1165 <div id="rfc.iref.41"></div> 1157 1166 <div id="rfc.iref.s.19"></div> 1158 <h3 id="rfc.section. 8.4.2"><a href="#rfc.section.8.4.2">8.4.2</a> <a id="status.401" href="#status.401">401 Unauthorized</a></h3>1159 <p id="rfc.section. 8.4.2.p.1">The request requires user authentication (see <a href="#Part7" id="rfc.xref.Part7.5"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).1167 <h3 id="rfc.section.9.4.2"><a href="#rfc.section.9.4.2">9.4.2</a> <a id="status.401" href="#status.401">401 Unauthorized</a></h3> 1168 <p id="rfc.section.9.4.2.p.1">The request requires user authentication (see <a href="#Part7" id="rfc.xref.Part7.5"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>). 1160 1169 </p> 1161 1170 <div id="rfc.iref.42"></div> 1162 1171 <div id="rfc.iref.s.20"></div> 1163 <h3 id="rfc.section. 8.4.3"><a href="#rfc.section.8.4.3">8.4.3</a> <a id="status.402" href="#status.402">402 Payment Required</a></h3>1164 <p id="rfc.section. 8.4.3.p.1">This code is reserved for future use.</p>1172 <h3 id="rfc.section.9.4.3"><a href="#rfc.section.9.4.3">9.4.3</a> <a id="status.402" href="#status.402">402 Payment Required</a></h3> 1173 <p id="rfc.section.9.4.3.p.1">This code is reserved for future use.</p> 1165 1174 <div id="rfc.iref.43"></div> 1166 1175 <div id="rfc.iref.s.21"></div> 1167 <h3 id="rfc.section. 8.4.4"><a href="#rfc.section.8.4.4">8.4.4</a> <a id="status.403" href="#status.403">403 Forbidden</a></h3>1168 <p id="rfc.section. 8.4.4.p.1">The server understood the request, but is refusing to fulfill it. Authorization will not help and the request <em class="bcp14">SHOULD NOT</em> be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled,1176 <h3 id="rfc.section.9.4.4"><a href="#rfc.section.9.4.4">9.4.4</a> <a id="status.403" href="#status.403">403 Forbidden</a></h3> 1177 <p id="rfc.section.9.4.4.p.1">The server understood the request, but is refusing to fulfill it. Authorization will not help and the request <em class="bcp14">SHOULD NOT</em> be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, 1169 1178 it <em class="bcp14">SHOULD</em> describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, 1170 1179 the status code 404 (Not Found) can be used instead. … … 1172 1181 <div id="rfc.iref.44"></div> 1173 1182 <div id="rfc.iref.s.22"></div> 1174 <h3 id="rfc.section. 8.4.5"><a href="#rfc.section.8.4.5">8.4.5</a> <a id="status.404" href="#status.404">404 Not Found</a></h3>1175 <p id="rfc.section. 8.4.5.p.1">The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or1183 <h3 id="rfc.section.9.4.5"><a href="#rfc.section.9.4.5">9.4.5</a> <a id="status.404" href="#status.404">404 Not Found</a></h3> 1184 <p id="rfc.section.9.4.5.p.1">The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or 1176 1185 permanent. The 410 (Gone) status code <em class="bcp14">SHOULD</em> be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable 1177 1186 and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request … … 1180 1189 <div id="rfc.iref.45"></div> 1181 1190 <div id="rfc.iref.s.23"></div> 1182 <h3 id="rfc.section. 8.4.6"><a href="#rfc.section.8.4.6">8.4.6</a> <a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>1183 <p id="rfc.section. 8.4.6.p.1">The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response <em class="bcp14">MUST</em> include an Allow header containing a list of valid methods for the requested resource.1191 <h3 id="rfc.section.9.4.6"><a href="#rfc.section.9.4.6">9.4.6</a> <a id="status.405" href="#status.405">405 Method Not Allowed</a></h3> 1192 <p id="rfc.section.9.4.6.p.1">The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response <em class="bcp14">MUST</em> include an Allow header containing a list of valid methods for the requested resource. 1184 1193 </p> 1185 1194 <div id="rfc.iref.46"></div> 1186 1195 <div id="rfc.iref.s.24"></div> 1187 <h3 id="rfc.section. 8.4.7"><a href="#rfc.section.8.4.7">8.4.7</a> <a id="status.406" href="#status.406">406 Not Acceptable</a></h3>1188 <p id="rfc.section. 8.4.7.p.1">The resource identified by the request is only capable of generating response entities which have content characteristics1196 <h3 id="rfc.section.9.4.7"><a href="#rfc.section.9.4.7">9.4.7</a> <a id="status.406" href="#status.406">406 Not Acceptable</a></h3> 1197 <p id="rfc.section.9.4.7.p.1">The resource identified by the request is only capable of generating response entities which have content characteristics 1189 1198 not acceptable according to the accept headers sent in the request. 1190 1199 </p> 1191 <p id="rfc.section. 8.4.7.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include an entity containing a list of available entity characteristics and location(s) from which the user or user agent1200 <p id="rfc.section.9.4.7.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include an entity containing a list of available entity characteristics and location(s) from which the user or user agent 1192 1201 can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. 1193 1202 Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection. … … 1199 1208 </dd> 1200 1209 </dl> 1201 <p id="rfc.section. 8.4.7.p.3">If the response could be unacceptable, a user agent <em class="bcp14">SHOULD</em> temporarily stop receipt of more data and query the user for a decision on further actions.1210 <p id="rfc.section.9.4.7.p.3">If the response could be unacceptable, a user agent <em class="bcp14">SHOULD</em> temporarily stop receipt of more data and query the user for a decision on further actions. 1202 1211 </p> 1203 1212 <div id="rfc.iref.47"></div> 1204 1213 <div id="rfc.iref.s.25"></div> 1205 <h3 id="rfc.section. 8.4.8"><a href="#rfc.section.8.4.8">8.4.8</a> <a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h3>1206 <p id="rfc.section. 8.4.8.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy (see <a href="#Part7" id="rfc.xref.Part7.6"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).1214 <h3 id="rfc.section.9.4.8"><a href="#rfc.section.9.4.8">9.4.8</a> <a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h3> 1215 <p id="rfc.section.9.4.8.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy (see <a href="#Part7" id="rfc.xref.Part7.6"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>). 1207 1216 </p> 1208 1217 <div id="rfc.iref.48"></div> 1209 1218 <div id="rfc.iref.s.26"></div> 1210 <h3 id="rfc.section. 8.4.9"><a href="#rfc.section.8.4.9">8.4.9</a> <a id="status.408" href="#status.408">408 Request Timeout</a></h3>1211 <p id="rfc.section. 8.4.9.p.1">The client did not produce a request within the time that the server was prepared to wait. The client <em class="bcp14">MAY</em> repeat the request without modifications at any later time.1219 <h3 id="rfc.section.9.4.9"><a href="#rfc.section.9.4.9">9.4.9</a> <a id="status.408" href="#status.408">408 Request Timeout</a></h3> 1220 <p id="rfc.section.9.4.9.p.1">The client did not produce a request within the time that the server was prepared to wait. The client <em class="bcp14">MAY</em> repeat the request without modifications at any later time. 1212 1221 </p> 1213 1222 <div id="rfc.iref.49"></div> 1214 1223 <div id="rfc.iref.s.27"></div> 1215 <h3 id="rfc.section. 8.4.10"><a href="#rfc.section.8.4.10">8.4.10</a> <a id="status.409" href="#status.409">409 Conflict</a></h3>1216 <p id="rfc.section. 8.4.10.p.1">The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in1224 <h3 id="rfc.section.9.4.10"><a href="#rfc.section.9.4.10">9.4.10</a> <a id="status.409" href="#status.409">409 Conflict</a></h3> 1225 <p id="rfc.section.9.4.10.p.1">The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in 1217 1226 situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response 1218 1227 body <em class="bcp14">SHOULD</em> include enough information for the user to recognize the source of the conflict. Ideally, the response entity would include 1219 1228 enough information for the user or user agent to fix the problem; however, that might not be possible and is not required. 1220 1229 </p> 1221 <p id="rfc.section. 8.4.10.p.2">Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity1230 <p id="rfc.section.9.4.10.p.2">Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity 1222 1231 being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might 1223 1232 use the 409 response to indicate that it can't complete the request. In this case, the response entity would likely contain … … 1226 1235 <div id="rfc.iref.50"></div> 1227 1236 <div id="rfc.iref.s.28"></div> 1228 <h3 id="rfc.section. 8.4.11"><a href="#rfc.section.8.4.11">8.4.11</a> <a id="status.410" href="#status.410">410 Gone</a></h3>1229 <p id="rfc.section. 8.4.11.p.1">The requested resource is no longer available at the server and no forwarding address is known. This condition is expected1237 <h3 id="rfc.section.9.4.11"><a href="#rfc.section.9.4.11">9.4.11</a> <a id="status.410" href="#status.410">410 Gone</a></h3> 1238 <p id="rfc.section.9.4.11.p.1">The requested resource is no longer available at the server and no forwarding address is known. This condition is expected 1230 1239 to be considered permanent. Clients with link editing capabilities <em class="bcp14">SHOULD</em> delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether 1231 1240 or not the condition is permanent, the status code 404 (Not Found) <em class="bcp14">SHOULD</em> be used instead. This response is cacheable unless indicated otherwise. 1232 1241 </p> 1233 <p id="rfc.section. 8.4.11.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource1242 <p id="rfc.section.9.4.11.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource 1234 1243 is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event 1235 1244 is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's … … 1239 1248 <div id="rfc.iref.51"></div> 1240 1249 <div id="rfc.iref.s.29"></div> 1241 <h3 id="rfc.section. 8.4.12"><a href="#rfc.section.8.4.12">8.4.12</a> <a id="status.411" href="#status.411">411 Length Required</a></h3>1242 <p id="rfc.section. 8.4.12.p.1">The server refuses to accept the request without a defined Content-Length. The client <em class="bcp14">MAY</em> repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request1250 <h3 id="rfc.section.9.4.12"><a href="#rfc.section.9.4.12">9.4.12</a> <a id="status.411" href="#status.411">411 Length Required</a></h3> 1251 <p id="rfc.section.9.4.12.p.1">The server refuses to accept the request without a defined Content-Length. The client <em class="bcp14">MAY</em> repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request 1243 1252 message. 1244 1253 </p> 1245 1254 <div id="rfc.iref.52"></div> 1246 1255 <div id="rfc.iref.s.30"></div> 1247 <h3 id="rfc.section. 8.4.13"><a href="#rfc.section.8.4.13">8.4.13</a> <a id="status.412" href="#status.412">412 Precondition Failed</a></h3>1248 <p id="rfc.section. 8.4.13.p.1">The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server, as1256 <h3 id="rfc.section.9.4.13"><a href="#rfc.section.9.4.13">9.4.13</a> <a id="status.412" href="#status.412">412 Precondition Failed</a></h3> 1257 <p id="rfc.section.9.4.13.p.1">The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server, as 1249 1258 defined in <a href="#Part4" id="rfc.xref.Part4.8"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. 1250 1259 </p> 1251 1260 <div id="rfc.iref.53"></div> 1252 1261 <div id="rfc.iref.s.31"></div> 1253 <h3 id="rfc.section. 8.4.14"><a href="#rfc.section.8.4.14">8.4.14</a> <a id="status.413" href="#status.413">413 Request Entity Too Large</a></h3>1254 <p id="rfc.section. 8.4.14.p.1">The server is refusing to process a request because the request entity is larger than the server is willing or able to process.1262 <h3 id="rfc.section.9.4.14"><a href="#rfc.section.9.4.14">9.4.14</a> <a id="status.413" href="#status.413">413 Request Entity Too Large</a></h3> 1263 <p id="rfc.section.9.4.14.p.1">The server is refusing to process a request because the request entity is larger than the server is willing or able to process. 1255 1264 The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request. 1256 1265 </p> 1257 <p id="rfc.section. 8.4.14.p.2">If the condition is temporary, the server <em class="bcp14">SHOULD</em> include a Retry-After header field to indicate that it is temporary and after what time the client <em class="bcp14">MAY</em> try again.1266 <p id="rfc.section.9.4.14.p.2">If the condition is temporary, the server <em class="bcp14">SHOULD</em> include a Retry-After header field to indicate that it is temporary and after what time the client <em class="bcp14">MAY</em> try again. 1258 1267 </p> 1259 1268 <div id="rfc.iref.54"></div> 1260 1269 <div id="rfc.iref.s.32"></div> 1261 <h3 id="rfc.section. 8.4.15"><a href="#rfc.section.8.4.15">8.4.15</a> <a id="status.414" href="#status.414">414 Request-URI Too Long</a></h3>1262 <p id="rfc.section. 8.4.15.p.1">The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This1270 <h3 id="rfc.section.9.4.15"><a href="#rfc.section.9.4.15">9.4.15</a> <a id="status.414" href="#status.414">414 Request-URI Too Long</a></h3> 1271 <p id="rfc.section.9.4.15.p.1">The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This 1263 1272 rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query 1264 1273 information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points … … 1268 1277 <div id="rfc.iref.55"></div> 1269 1278 <div id="rfc.iref.s.33"></div> 1270 <h3 id="rfc.section. 8.4.16"><a href="#rfc.section.8.4.16">8.4.16</a> <a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>1271 <p id="rfc.section. 8.4.16.p.1">The server is refusing to service the request because the entity of the request is in a format not supported by the requested1279 <h3 id="rfc.section.9.4.16"><a href="#rfc.section.9.4.16">9.4.16</a> <a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3> 1280 <p id="rfc.section.9.4.16.p.1">The server is refusing to service the request because the entity of the request is in a format not supported by the requested 1272 1281 resource for the requested method. 1273 1282 </p> 1274 1283 <div id="rfc.iref.56"></div> 1275 1284 <div id="rfc.iref.s.34"></div> 1276 <h3 id="rfc.section. 8.4.17"><a href="#rfc.section.8.4.17">8.4.17</a> <a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h3>1277 <p id="rfc.section. 8.4.17.p.1">The request included a Range request-header field (<a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.7"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and none of the range-specifier values in this field overlap the current extent of the selected resource.1285 <h3 id="rfc.section.9.4.17"><a href="#rfc.section.9.4.17">9.4.17</a> <a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h3> 1286 <p id="rfc.section.9.4.17.p.1">The request included a Range request-header field (<a href="p5-range.html#header.range" title="Range">Section 6.4</a> of <a href="#Part5" id="rfc.xref.Part5.7"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and none of the range-specifier values in this field overlap the current extent of the selected resource. 1278 1287 </p> 1279 1288 <div id="rfc.iref.57"></div> 1280 1289 <div id="rfc.iref.s.35"></div> 1281 <h3 id="rfc.section. 8.4.18"><a href="#rfc.section.8.4.18">8.4.18</a> <a id="status.417" href="#status.417">417 Expectation Failed</a></h3>1282 <p id="rfc.section. 8.4.18.p.1">The expectation given in an Expect request-header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section 9.2</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could1290 <h3 id="rfc.section.9.4.18"><a href="#rfc.section.9.4.18">9.4.18</a> <a id="status.417" href="#status.417">417 Expectation Failed</a></h3> 1291 <p id="rfc.section.9.4.18.p.1">The expectation given in an Expect request-header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section 10.2</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could 1283 1292 not be met by the next-hop server. 1284 1293 </p> 1285 <h2 id="rfc.section. 8.5"><a href="#rfc.section.8.5">8.5</a> <a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>1286 <p id="rfc.section. 8.5.p.1">Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable1294 <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a> <a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2> 1295 <p id="rfc.section.9.5.p.1">Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable 1287 1296 of performing the request. Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. 1288 1297 User agents <em class="bcp14">SHOULD</em> display any included entity to the user. These response codes are applicable to any request method. … … 1290 1299 <div id="rfc.iref.58"></div> 1291 1300 <div id="rfc.iref.s.36"></div> 1292 <h3 id="rfc.section. 8.5.1"><a href="#rfc.section.8.5.1">8.5.1</a> <a id="status.500" href="#status.500">500 Internal Server Error</a></h3>1293 <p id="rfc.section. 8.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>1301 <h3 id="rfc.section.9.5.1"><a href="#rfc.section.9.5.1">9.5.1</a> <a id="status.500" href="#status.500">500 Internal Server Error</a></h3> 1302 <p id="rfc.section.9.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p> 1294 1303 <div id="rfc.iref.59"></div> 1295 1304 <div id="rfc.iref.s.37"></div> 1296 <h3 id="rfc.section. 8.5.2"><a href="#rfc.section.8.5.2">8.5.2</a> <a id="status.501" href="#status.501">501 Not Implemented</a></h3>1297 <p id="rfc.section. 8.5.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server1305 <h3 id="rfc.section.9.5.2"><a href="#rfc.section.9.5.2">9.5.2</a> <a id="status.501" href="#status.501">501 Not Implemented</a></h3> 1306 <p id="rfc.section.9.5.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server 1298 1307 does not recognize the request method and is not capable of supporting it for any resource. 1299 1308 </p> 1300 1309 <div id="rfc.iref.60"></div> 1301 1310 <div id="rfc.iref.s.38"></div> 1302 <h3 id="rfc.section. 8.5.3"><a href="#rfc.section.8.5.3">8.5.3</a> <a id="status.502" href="#status.502">502 Bad Gateway</a></h3>1303 <p id="rfc.section. 8.5.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting1311 <h3 id="rfc.section.9.5.3"><a href="#rfc.section.9.5.3">9.5.3</a> <a id="status.502" href="#status.502">502 Bad Gateway</a></h3> 1312 <p id="rfc.section.9.5.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting 1304 1313 to fulfill the request. 1305 1314 </p> 1306 1315 <div id="rfc.iref.61"></div> 1307 1316 <div id="rfc.iref.s.39"></div> 1308 <h3 id="rfc.section. 8.5.4"><a href="#rfc.section.8.5.4">8.5.4</a> <a id="status.503" href="#status.503">503 Service Unavailable</a></h3>1309 <p id="rfc.section. 8.5.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication1317 <h3 id="rfc.section.9.5.4"><a href="#rfc.section.9.5.4">9.5.4</a> <a id="status.503" href="#status.503">503 Service Unavailable</a></h3> 1318 <p id="rfc.section.9.5.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication 1310 1319 is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay <em class="bcp14">MAY</em> be indicated in a Retry-After header. If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response. 1311 1320 </p> … … 1317 1326 <div id="rfc.iref.62"></div> 1318 1327 <div id="rfc.iref.s.40"></div> 1319 <h3 id="rfc.section. 8.5.5"><a href="#rfc.section.8.5.5">8.5.5</a> <a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>1320 <p id="rfc.section. 8.5.5.p.1">The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the1328 <h3 id="rfc.section.9.5.5"><a href="#rfc.section.9.5.5">9.5.5</a> <a id="status.504" href="#status.504">504 Gateway Timeout</a></h3> 1329 <p id="rfc.section.9.5.5.p.1">The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the 1321 1330 URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request. 1322 1331 </p> … … 1327 1336 <div id="rfc.iref.63"></div> 1328 1337 <div id="rfc.iref.s.41"></div> 1329 <h3 id="rfc.section. 8.5.6"><a href="#rfc.section.8.5.6">8.5.6</a> <a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>1330 <p id="rfc.section. 8.5.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server1338 <h3 id="rfc.section.9.5.6"><a href="#rfc.section.9.5.6">9.5.6</a> <a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3> 1339 <p id="rfc.section.9.5.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server 1331 1340 is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described 1332 in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 3.1</a> of <a href="#Part1" id="rfc.xref.Part1. 7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain an entity describing why that version is not supported and what other protocols are supported by that server.1333 </p> 1334 <h1 id="rfc.section. 9"><a href="#rfc.section.9">9.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>1335 <p id="rfc.section. 9.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics.</p>1336 <p id="rfc.section. 9.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who1341 in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 3.1</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain an entity describing why that version is not supported and what other protocols are supported by that server. 1342 </p> 1343 <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1> 1344 <p id="rfc.section.10.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics.</p> 1345 <p id="rfc.section.10.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who 1337 1346 receives the entity. 1338 1347 </p> 1339 1348 <div id="rfc.iref.a.1"></div> 1340 1349 <div id="rfc.iref.h.2"></div> 1341 <h2 id="rfc.section. 9.1"><a href="#rfc.section.9.1">9.1</a> <a id="header.allow" href="#header.allow">Allow</a></h2>1342 <p id="rfc.section. 9.1.p.1">The Allow entity-header field lists the set of methods supported by the resource identified by the Request-URI. The purpose1350 <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a> <a id="header.allow" href="#header.allow">Allow</a></h2> 1351 <p id="rfc.section.10.1.p.1">The Allow entity-header field lists the set of methods supported by the resource identified by the Request-URI. The purpose 1343 1352 of this field is strictly to inform the recipient of valid methods associated with the resource. An Allow header field <em class="bcp14">MUST</em> be present in a 405 (Method Not Allowed) response. 1344 1353 </p> 1345 <div id="rfc.figure.u. 5"></div><pre class="inline"><span id="rfc.iref.g.9"></span> Allow = "Allow" ":" #Method1346 </pre><p id="rfc.section. 9.1.p.3">Example of use:</p>1347 <div id="rfc.figure.u. 6"></div><pre class="text"> Allow: GET, HEAD, PUT1348 </pre><p id="rfc.section. 9.1.p.5">This field cannot prevent a client from trying other methods. However, the indications given by the Allow header field value <em class="bcp14">SHOULD</em> be followed. The actual set of allowed methods is defined by the origin server at the time of each request.1349 </p> 1350 <p id="rfc.section. 9.1.p.6">The Allow header field <em class="bcp14">MAY</em> be provided with a PUT request to recommend the methods to be supported by the new or modified resource. The server is not1354 <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.9"></span> Allow = "Allow" ":" #Method 1355 </pre><p id="rfc.section.10.1.p.3">Example of use:</p> 1356 <div id="rfc.figure.u.8"></div><pre class="text"> Allow: GET, HEAD, PUT 1357 </pre><p id="rfc.section.10.1.p.5">This field cannot prevent a client from trying other methods. However, the indications given by the Allow header field value <em class="bcp14">SHOULD</em> be followed. The actual set of allowed methods is defined by the origin server at the time of each request. 1358 </p> 1359 <p id="rfc.section.10.1.p.6">The Allow header field <em class="bcp14">MAY</em> be provided with a PUT request to recommend the methods to be supported by the new or modified resource. The server is not 1351 1360 required to support these methods and <em class="bcp14">SHOULD</em> include an Allow header in the response giving the actual supported methods. 1352 1361 </p> 1353 <p id="rfc.section. 9.1.p.7">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field even if it does not understand all the methods specified, since the user agent might have other1362 <p id="rfc.section.10.1.p.7">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field even if it does not understand all the methods specified, since the user agent might have other 1354 1363 means of communicating with the origin server. 1355 1364 </p> 1356 1365 <div id="rfc.iref.e.1"></div> 1357 1366 <div id="rfc.iref.h.3"></div> 1358 <h2 id="rfc.section. 9.2"><a href="#rfc.section.9.2">9.2</a> <a id="header.expect" href="#header.expect">Expect</a></h2>1359 <p id="rfc.section. 9.2.p.1">The Expect request-header field is used to indicate that particular server behaviors are required by the client.</p>1360 <div id="rfc.figure.u. 7"></div><pre class="inline"><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span> Expect = "Expect" ":" 1#expectation1367 <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a> <a id="header.expect" href="#header.expect">Expect</a></h2> 1368 <p id="rfc.section.10.2.p.1">The Expect request-header field is used to indicate that particular server behaviors are required by the client.</p> 1369 <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span> Expect = "Expect" ":" 1#expectation 1361 1370 1362 1371 expectation = "100-continue" | expectation-extension … … 1364 1373 *expect-params ] 1365 1374 expect-params = ";" token [ "=" ( token | quoted-string ) ] 1366 </pre><p id="rfc.section. 9.2.p.3">A server that does not understand or is unable to comply with any of the expectation values in the Expect field of a request <em class="bcp14">MUST</em> respond with appropriate error status. The server <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status if any of the expectations cannot be met or, if there are other problems with1375 </pre><p id="rfc.section.10.2.p.3">A server that does not understand or is unable to comply with any of the expectation values in the Expect field of a request <em class="bcp14">MUST</em> respond with appropriate error status. The server <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status if any of the expectations cannot be met or, if there are other problems with 1367 1376 the request, some other 4xx status. 1368 1377 </p> 1369 <p id="rfc.section. 9.2.p.4">This header field is defined with extensible syntax to allow for future extensions. If a server receives a request containing1378 <p id="rfc.section.10.2.p.4">This header field is defined with extensible syntax to allow for future extensions. If a server receives a request containing 1370 1379 an Expect field that includes an expectation-extension that it does not support, it <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status. 1371 1380 </p> 1372 <p id="rfc.section. 9.2.p.5">Comparison of expectation values is case-insensitive for unquoted tokens (including the 100-continue token), and is case-sensitive1381 <p id="rfc.section.10.2.p.5">Comparison of expectation values is case-insensitive for unquoted tokens (including the 100-continue token), and is case-sensitive 1373 1382 for quoted-string expectation-extensions. 1374 1383 </p> 1375 <p id="rfc.section. 9.2.p.6">The Expect mechanism is hop-by-hop: that is, an HTTP/1.1 proxy <em class="bcp14">MUST</em> return a 417 (Expectation Failed) status if it receives a request with an expectation that it cannot meet. However, the Expect1384 <p id="rfc.section.10.2.p.6">The Expect mechanism is hop-by-hop: that is, an HTTP/1.1 proxy <em class="bcp14">MUST</em> return a 417 (Expectation Failed) status if it receives a request with an expectation that it cannot meet. However, the Expect 1376 1385 request-header itself is end-to-end; it <em class="bcp14">MUST</em> be forwarded if the request is forwarded. 1377 1386 </p> 1378 <p id="rfc.section. 9.2.p.7">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header.</p>1379 <p id="rfc.section. 9.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status.1387 <p id="rfc.section.10.2.p.7">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header.</p> 1388 <p id="rfc.section.10.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status. 1380 1389 </p> 1381 1390 <div id="rfc.iref.f.1"></div> 1382 1391 <div id="rfc.iref.h.4"></div> 1383 <h2 id="rfc.section. 9.3"><a href="#rfc.section.9.3">9.3</a> <a id="header.from" href="#header.from">From</a></h2>1384 <p id="rfc.section. 9.3.p.1">The From request-header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc2822#section-3.4">Section 3.4</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.1"><cite title="Internet Message Format">[RFC2822]</cite></a>:1385 </p> 1386 <div id="rfc.figure.u. 8"></div><pre class="inline"><span id="rfc.iref.g.14"></span> From = "From" ":" mailbox1387 </pre><p id="rfc.section. 9.3.p.3">An example is:</p>1388 <div id="rfc.figure.u. 9"></div><pre class="text"> From: webmaster@example.org1389 </pre><p id="rfc.section. 9.3.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed1392 <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a> <a id="header.from" href="#header.from">From</a></h2> 1393 <p id="rfc.section.10.3.p.1">The From request-header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc2822#section-3.4">Section 3.4</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.1"><cite title="Internet Message Format">[RFC2822]</cite></a>: 1394 </p> 1395 <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.14"></span> From = "From" ":" mailbox 1396 </pre><p id="rfc.section.10.3.p.3">An example is:</p> 1397 <div id="rfc.figure.u.11"></div><pre class="text"> From: webmaster@example.org 1398 </pre><p id="rfc.section.10.3.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed 1390 1399 on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header so that the person responsible for running the robot can be contacted if problems occur on the receiving 1391 1400 end. 1392 1401 </p> 1393 <p id="rfc.section. 9.3.p.6">The Internet e-mail address in this field <em class="bcp14">MAY</em> be separate from the Internet host which issued the request. For example, when a request is passed through a proxy the original1402 <p id="rfc.section.10.3.p.6">The Internet e-mail address in this field <em class="bcp14">MAY</em> be separate from the Internet host which issued the request. For example, when a request is passed through a proxy the original 1394 1403 issuer's address <em class="bcp14">SHOULD</em> be used. 1395 1404 </p> 1396 <p id="rfc.section. 9.3.p.7">The client <em class="bcp14">SHOULD NOT</em> send the From header field without the user's approval, as it might conflict with the user's privacy interests or their site's1405 <p id="rfc.section.10.3.p.7">The client <em class="bcp14">SHOULD NOT</em> send the From header field without the user's approval, as it might conflict with the user's privacy interests or their site's 1397 1406 security policy. It is strongly recommended that the user be able to disable, enable, and modify the value of this field at 1398 1407 any time prior to a request. … … 1400 1409 <div id="rfc.iref.l.1"></div> 1401 1410 <div id="rfc.iref.h.5"></div> 1402 <h2 id="rfc.section. 9.4"><a href="#rfc.section.9.4">9.4</a> <a id="header.location" href="#header.location">Location</a></h2>1403 <p id="rfc.section. 9.4.p.1">The Location response-header field is used to redirect the recipient to a location other than the Request-URI for completion1411 <h2 id="rfc.section.10.4"><a href="#rfc.section.10.4">10.4</a> <a id="header.location" href="#header.location">Location</a></h2> 1412 <p id="rfc.section.10.4.p.1">The Location response-header field is used to redirect the recipient to a location other than the Request-URI for completion 1404 1413 of the request or identification of a new resource. For 201 (Created) responses, the Location is that of the new resource 1405 1414 which was created by the request. For 3xx responses, the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource. The field value consists of a single absolute 1406 1415 URI. 1407 1416 </p> 1408 <div id="rfc.figure.u.1 0"></div><pre class="inline"><span id="rfc.iref.g.15"></span> Location = "Location" ":" absoluteURI [ "#" fragment ]1409 </pre><p id="rfc.section. 9.4.p.3">An example is:</p>1410 <div id="rfc.figure.u.1 1"></div><pre class="text"> Location: http://www.example.org/pub/WWW/People.html1411 </pre><p id="rfc.section. 9.4.p.5"> </p>1417 <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.15"></span> Location = "Location" ":" absoluteURI [ "#" fragment ] 1418 </pre><p id="rfc.section.10.4.p.3">An example is:</p> 1419 <div id="rfc.figure.u.13"></div><pre class="text"> Location: http://www.example.org/pub/WWW/People.html 1420 </pre><p id="rfc.section.10.4.p.5"> </p> 1412 1421 <dl class="empty"> 1413 <dd> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 5.7</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the request.1422 <dd> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the request. 1414 1423 It is therefore possible for a response to contain header fields for both Location and Content-Location. 1415 1424 </dd> 1416 1425 </dl> 1417 <p id="rfc.section. 9.4.p.6">There are circumstances in which a fragment identifier in a Location URL would not be appropriate: </p>1426 <p id="rfc.section.10.4.p.6">There are circumstances in which a fragment identifier in a Location URL would not be appropriate: </p> 1418 1427 <ul> 1419 1428 <li>With a 201 Created response, because in this usage the Location header specifies the URL for the entire created resource.</li> … … 1425 1434 <div id="rfc.iref.m.9"></div> 1426 1435 <div id="rfc.iref.h.6"></div> 1427 <h2 id="rfc.section. 9.5"><a href="#rfc.section.9.5">9.5</a> <a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2>1428 <p id="rfc.section. 9.5.p.1">The Max-Forwards request-header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section 7.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section 7.2</a>) methods to limit the number of proxies or gateways that can forward the request to the next inbound server. This can be1436 <h2 id="rfc.section.10.5"><a href="#rfc.section.10.5">10.5</a> <a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2> 1437 <p id="rfc.section.10.5.p.1">The Max-Forwards request-header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section 8.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section 8.2</a>) methods to limit the number of proxies or gateways that can forward the request to the next inbound server. This can be 1429 1438 useful when the client is attempting to trace a request chain which appears to be failing or looping in mid-chain. 1430 1439 </p> 1431 <div id="rfc.figure.u.1 2"></div><pre class="inline"><span id="rfc.iref.g.16"></span> Max-Forwards = "Max-Forwards" ":" 1*DIGIT1432 </pre><p id="rfc.section. 9.5.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message may be forwarded.</p>1433 <p id="rfc.section. 9.5.p.4">Each proxy or gateway recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).1434 </p> 1435 <p id="rfc.section. 9.5.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other methods defined by this specification and for any extension methods for which it is not explicitly1440 <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.16"></span> Max-Forwards = "Max-Forwards" ":" 1*DIGIT 1441 </pre><p id="rfc.section.10.5.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message may be forwarded.</p> 1442 <p id="rfc.section.10.5.p.4">Each proxy or gateway recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1). 1443 </p> 1444 <p id="rfc.section.10.5.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other methods defined by this specification and for any extension methods for which it is not explicitly 1436 1445 referred to as part of that method definition. 1437 1446 </p> 1438 1447 <div id="rfc.iref.r.1"></div> 1439 1448 <div id="rfc.iref.h.7"></div> 1440 <h2 id="rfc.section. 9.6"><a href="#rfc.section.9.6">9.6</a> <a id="header.referer" href="#header.referer">Referer</a></h2>1441 <p id="rfc.section. 9.6.p.1">The Referer[sic] request-header field allows the client to specify, for the server's benefit, the address (URI) of the resource1449 <h2 id="rfc.section.10.6"><a href="#rfc.section.10.6">10.6</a> <a id="header.referer" href="#header.referer">Referer</a></h2> 1450 <p id="rfc.section.10.6.p.1">The Referer[sic] request-header field allows the client to specify, for the server's benefit, the address (URI) of the resource 1442 1451 from which the Request-URI was obtained (the "referrer", although the header field is misspelled.) The Referer request-header 1443 1452 allows a server to generate lists of back-links to resources for interest, logging, optimized caching, etc. It also allows 1444 1453 obsolete or mistyped links to be traced for maintenance. The Referer field <em class="bcp14">MUST NOT</em> be sent if the Request-URI was obtained from a source that does not have its own URI, such as input from the user keyboard. 1445 1454 </p> 1446 <div id="rfc.figure.u.1 3"></div><pre class="inline"><span id="rfc.iref.g.17"></span> Referer = "Referer" ":" ( absoluteURI | relativeURI )1447 </pre><p id="rfc.section. 9.6.p.3">Example:</p>1448 <div id="rfc.figure.u.1 4"></div><pre class="text"> Referer: http://www.example.org/hypertext/Overview.html1449 </pre><p id="rfc.section. 9.6.p.5">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the Request-URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section 11.2</a> for security considerations.1455 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.17"></span> Referer = "Referer" ":" ( absoluteURI | relativeURI ) 1456 </pre><p id="rfc.section.10.6.p.3">Example:</p> 1457 <div id="rfc.figure.u.16"></div><pre class="text"> Referer: http://www.example.org/hypertext/Overview.html 1458 </pre><p id="rfc.section.10.6.p.5">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the Request-URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section 12.2</a> for security considerations. 1450 1459 </p> 1451 1460 <div id="rfc.iref.r.2"></div> 1452 1461 <div id="rfc.iref.h.8"></div> 1453 <h2 id="rfc.section. 9.7"><a href="#rfc.section.9.7">9.7</a> <a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>1454 <p id="rfc.section. 9.7.p.1">The Retry-After response-header field can be used with a 503 (Service Unavailable) response to indicate how long the service1462 <h2 id="rfc.section.10.7"><a href="#rfc.section.10.7">10.7</a> <a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2> 1463 <p id="rfc.section.10.7.p.1">The Retry-After response-header field can be used with a 503 (Service Unavailable) response to indicate how long the service 1455 1464 is expected to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked wait before issuing 1456 1465 the redirected request. The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after 1457 1466 the time of the response. 1458 1467 </p> 1459 <div id="rfc.figure.u.1 5"></div><pre class="inline"><span id="rfc.iref.g.18"></span> Retry-After = "Retry-After" ":" ( HTTP-date | delta-seconds )1460 </pre><p id="rfc.section. 9.7.p.3">Two examples of its use are</p>1461 <div id="rfc.figure.u.1 6"></div><pre class="text"> Retry-After: Fri, 31 Dec 1999 23:59:59 GMT1468 <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.18"></span> Retry-After = "Retry-After" ":" ( HTTP-date | delta-seconds ) 1469 </pre><p id="rfc.section.10.7.p.3">Two examples of its use are</p> 1470 <div id="rfc.figure.u.18"></div><pre class="text"> Retry-After: Fri, 31 Dec 1999 23:59:59 GMT 1462 1471 Retry-After: 120 1463 </pre><p id="rfc.section. 9.7.p.5">In the latter example, the delay is 2 minutes.</p>1472 </pre><p id="rfc.section.10.7.p.5">In the latter example, the delay is 2 minutes.</p> 1464 1473 <div id="rfc.iref.s.42"></div> 1465 1474 <div id="rfc.iref.h.9"></div> 1466 <h2 id="rfc.section. 9.8"><a href="#rfc.section.9.8">9.8</a> <a id="header.server" href="#header.server">Server</a></h2>1467 <p id="rfc.section. 9.8.p.1">The Server response-header field contains information about the software used by the origin server to handle the request.1468 The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1. 9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the server and any significant subproducts. The product tokens are listed in order of their significance1475 <h2 id="rfc.section.10.8"><a href="#rfc.section.10.8">10.8</a> <a id="header.server" href="#header.server">Server</a></h2> 1476 <p id="rfc.section.10.8.p.1">The Server response-header field contains information about the software used by the origin server to handle the request. 1477 The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the server and any significant subproducts. The product tokens are listed in order of their significance 1469 1478 for identifying the application. 1470 1479 </p> 1471 <div id="rfc.figure.u.1 7"></div><pre class="inline"><span id="rfc.iref.g.19"></span> Server = "Server" ":" 1*( product | comment )1472 </pre><p id="rfc.section. 9.8.p.3">Example:</p>1473 <div id="rfc.figure.u. 18"></div><pre class="text"> Server: CERN/3.0 libwww/2.171474 </pre><p id="rfc.section. 9.8.p.5">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).1480 <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.19"></span> Server = "Server" ":" 1*( product | comment ) 1481 </pre><p id="rfc.section.10.8.p.3">Example:</p> 1482 <div id="rfc.figure.u.20"></div><pre class="text"> Server: CERN/3.0 libwww/2.17 1483 </pre><p id="rfc.section.10.8.p.5">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 1475 1484 </p> 1476 1485 <dl class="empty"> … … 1482 1491 <div id="rfc.iref.u.1"></div> 1483 1492 <div id="rfc.iref.h.10"></div> 1484 <h2 id="rfc.section. 9.9"><a href="#rfc.section.9.9">9.9</a> <a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2>1485 <p id="rfc.section. 9.9.p.1">The User-Agent request-header field contains information about the user agent originating the request. This is for statistical1493 <h2 id="rfc.section.10.9"><a href="#rfc.section.10.9">10.9</a> <a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2> 1494 <p id="rfc.section.10.9.p.1">The User-Agent request-header field contains information about the user agent originating the request. This is for statistical 1486 1495 purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses 1487 to avoid particular user agent limitations. User agents <em class="bcp14">SHOULD</em> include this field with requests. The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.1 1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the agent and any subproducts which form a significant part of the user agent. By convention, the1496 to avoid particular user agent limitations. User agents <em class="bcp14">SHOULD</em> include this field with requests. The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the agent and any subproducts which form a significant part of the user agent. By convention, the 1488 1497 product tokens are listed in order of their significance for identifying the application. 1489 1498 </p> 1490 <div id="rfc.figure.u. 19"></div><pre class="inline"><span id="rfc.iref.g.20"></span> User-Agent = "User-Agent" ":" 1*( product | comment )1491 </pre><p id="rfc.section. 9.9.p.3">Example:</p>1492 <div id="rfc.figure.u.2 0"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b31493 </pre><h1 id="rfc.section.1 0"><a href="#rfc.section.10">10.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>1494 <p id="rfc.section.1 0.p.1"> <span class="comment">[rfc.comment.1: TBD.]</span>1495 </p> 1496 <h1 id="rfc.section.1 1"><a href="#rfc.section.11">11.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>1497 <p id="rfc.section.1 1.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.11499 <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.20"></span> User-Agent = "User-Agent" ":" 1*( product | comment ) 1500 </pre><p id="rfc.section.10.9.p.3">Example:</p> 1501 <div id="rfc.figure.u.22"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3 1502 </pre><h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 1503 <p id="rfc.section.11.p.1"> <span class="comment">[rfc.comment.1: TBD.]</span> 1504 </p> 1505 <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> 1506 <p id="rfc.section.12.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1 1498 1507 as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does 1499 1508 make some suggestions for reducing security risks. 1500 1509 </p> 1501 <h2 id="rfc.section.1 1.1"><a href="#rfc.section.11.1">11.1</a> <a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2>1502 <p id="rfc.section.1 1.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any1510 <h2 id="rfc.section.12.1"><a href="#rfc.section.12.1">12.1</a> <a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2> 1511 <p id="rfc.section.12.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any 1503 1512 a priori method of determining the sensitivity of any particular piece of information within the context of any given request. 1504 1513 Therefore, applications <em class="bcp14">SHOULD</em> supply as much control over this information as possible to the provider of that information. Four header fields are worth 1505 1514 special mention in this context: Server, Via, Referer and From. 1506 1515 </p> 1507 <p id="rfc.section.1 1.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks1516 <p id="rfc.section.12.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks 1508 1517 against software that is known to contain security holes. Implementors <em class="bcp14">SHOULD</em> make the Server header field a configurable option. 1509 1518 </p> 1510 <p id="rfc.section.1 1.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,1519 <p id="rfc.section.12.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular, 1511 1520 they <em class="bcp14">SHOULD</em> remove, or replace with sanitized versions, any Via fields generated behind the firewall. 1512 1521 </p> 1513 <p id="rfc.section.1 1.1.p.4">The Referer header allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its power1522 <p id="rfc.section.12.1.p.4">The Referer header allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its power 1514 1523 can be abused if user details are not separated from the information contained in the Referer. Even when the personal information 1515 1524 has been removed, the Referer header might indicate a private document's URI whose publication would be inappropriate. 1516 1525 </p> 1517 <p id="rfc.section.1 1.1.p.5">The information sent in the From field might conflict with the user's privacy interests or their site's security policy, and1526 <p id="rfc.section.12.1.p.5">The information sent in the From field might conflict with the user's privacy interests or their site's security policy, and 1518 1527 hence it <em class="bcp14">SHOULD NOT</em> be transmitted without the user being able to disable, enable, and modify the contents of the field. The user <em class="bcp14">MUST</em> be able to set the contents of this field within a user preference or application defaults configuration. 1519 1528 </p> 1520 <p id="rfc.section.1 1.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending1529 <p id="rfc.section.12.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending 1521 1530 of From and Referer information. 1522 1531 </p> 1523 <p id="rfc.section.1 1.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section 9.9</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section 9.8</a>) header fields can sometimes be used to determine that a specific client or server have a particular security hole which1532 <p id="rfc.section.12.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section 10.9</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section 10.8</a>) header fields can sometimes be used to determine that a specific client or server have a particular security hole which 1524 1533 might be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently 1525 1534 has no better mechanism. 1526 1535 </p> 1527 <h2 id="rfc.section.1 1.2"><a href="#rfc.section.11.2">11.2</a> <a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>1528 <p id="rfc.section.1 1.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly1536 <h2 id="rfc.section.12.2"><a href="#rfc.section.12.2">12.2</a> <a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2> 1537 <p id="rfc.section.12.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly 1529 1538 recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could 1530 1539 have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From 1531 1540 information. 1532 1541 </p> 1533 <p id="rfc.section.1 1.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.1534 </p> 1535 <p id="rfc.section.1 1.2.p.3">Authors of services should not use GET-based forms for the submission of sensitive data because that data will be encoded1542 <p id="rfc.section.12.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol. 1543 </p> 1544 <p id="rfc.section.12.2.p.3">Authors of services should not use GET-based forms for the submission of sensitive data because that data will be encoded 1536 1545 in the Request-URI. Many existing servers, proxies, and user agents log or display the Request-URI in places where it might 1537 1546 be visible to third parties. Such services can use POST-based form submission instead. 1538 1547 </p> 1539 <h2 id="rfc.section.1 1.3"><a href="#rfc.section.11.3">11.3</a> <a id="location.spoofing" href="#location.spoofing">Location Headers and Spoofing</a></h2>1540 <p id="rfc.section.1 1.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location headers in responses that are generated under control of said organizations1548 <h2 id="rfc.section.12.3"><a href="#rfc.section.12.3">12.3</a> <a id="location.spoofing" href="#location.spoofing">Location Headers and Spoofing</a></h2> 1549 <p id="rfc.section.12.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location headers in responses that are generated under control of said organizations 1541 1550 to make sure that they do not attempt to invalidate resources over which they have no authority. 1542 1551 </p> 1543 <h1 id="rfc.section.1 2"><a href="#rfc.section.12">12.</a> <a id="ack" href="#ack">Acknowledgments</a></h1>1544 <h1 id="rfc.references"><a id="rfc.section.1 3" href="#rfc.section.13">13.</a> References1552 <h1 id="rfc.section.13"><a href="#rfc.section.13">13.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> 1553 <h1 id="rfc.references"><a id="rfc.section.14" href="#rfc.section.14">14.</a> References 1545 1554 </h1> 1546 <h2 id="rfc.references.1"><a href="#rfc.section.1 3.1" id="rfc.section.13.1">13.1</a> Normative References1555 <h2 id="rfc.references.1"><a href="#rfc.section.14.1" id="rfc.section.14.1">14.1</a> Normative References 1547 1556 </h2> 1548 1557 <table summary="Normative References"> … … 1583 1592 </tr> 1584 1593 </table> 1585 <h2 id="rfc.references.2"><a href="#rfc.section.1 3.2" id="rfc.section.13.2">13.2</a> Informative References1594 <h2 id="rfc.references.2"><a href="#rfc.section.14.2" id="rfc.section.14.2">14.2</a> Informative References 1586 1595 </h2> 1587 1596 <table summary="Informative References"> … … 1630 1639 <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> 1631 1640 <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a> <a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2> 1632 <p id="rfc.section.A.1.p.1">Clarified which error code should be used for inbound server failures (e.g. DNS failures). (<a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section 8.5.5</a>).1633 </p> 1634 <p id="rfc.section.A.1.p.2">201 (Created) had a race that required an Etag be sent when a resource is first created. (<a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section 8.2.2</a>).1641 <p id="rfc.section.A.1.p.1">Clarified which error code should be used for inbound server failures (e.g. DNS failures). (<a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section 9.5.5</a>). 1642 </p> 1643 <p id="rfc.section.A.1.p.2">201 (Created) had a race that required an Etag be sent when a resource is first created. (<a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section 9.2.2</a>). 1635 1644 </p> 1636 1645 <p id="rfc.section.A.1.p.3">Rewrite of message transmission requirements to make it much harder for implementors to get it wrong, as the consequences … … 1652 1661 </ol> 1653 1662 <p id="rfc.section.A.1.p.4">This change adds the Expect header and 417 status code.</p> 1654 <p id="rfc.section.A.1.p.5">Clean up confusion between 403 and 404 responses. (Section <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden"> 8.4.4</a>, <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">8.4.5</a>, and <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">8.4.11</a>)1663 <p id="rfc.section.A.1.p.5">Clean up confusion between 403 and 404 responses. (Section <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">9.4.4</a>, <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">9.4.5</a>, and <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">9.4.11</a>) 1655 1664 </p> 1656 1665 <p id="rfc.section.A.1.p.6">The PATCH<span id="rfc.iref.p.3"></span><span id="rfc.iref.m.10"></span>, LINK<span id="rfc.iref.l.2"></span><span id="rfc.iref.m.11"></span>, UNLINK<span id="rfc.iref.u.2"></span><span id="rfc.iref.m.12"></span> methods were defined but not commonly implemented in previous versions of this specification. See <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 1657 1666 </p> 1658 1667 <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 1659 <p id="rfc.section.A.2.p.1">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.2" title="POST">Section 7.5</a>)1668 <p id="rfc.section.A.2.p.1">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.2" title="POST">Section 8.5</a>) 1660 1669 </p> 1661 1670 <p id="rfc.section.A.2.p.2">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the 1662 user agent is able to make that determination based on the request method semantics. (Sections <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently"> 8.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">8.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">8.3.8</a> )1671 user agent is able to make that determination based on the request method semantics. (Sections <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">9.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">9.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">9.3.8</a> ) 1663 1672 </p> 1664 1673 <p id="rfc.section.A.2.p.3">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications 1665 as to when it would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section 9.4</a>)1674 as to when it would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section 10.4</a>) 1666 1675 </p> 1667 1676 <p id="rfc.section.A.2.p.4">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly 1668 in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.1 2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section 9.8</a>)1677 in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section 10.8</a>) 1669 1678 </p> 1670 1679 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> Change Log (to be removed by RFC Editor before publication) … … 1713 1722 <ul> 1714 1723 <li>Move "Product Tokens" section (back) into Part 1, as "token" is used in the definition of the Upgrade header.</li> 1724 <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li> 1715 1725 </ul> 1716 1726 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> … … 1747 1757 <ul class="ind"> 1748 1758 <li class="indline0"><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul class="ind"> 1749 <li class="indline1">100 Continue (status code) <a class="iref" href="#rfc.xref.status.100.1"> 4</a>, <a class="iref" href="#rfc.iref.23"><b>8.1.1</b></a></li>1750 <li class="indline1">101 Switching Protocols (status code) <a class="iref" href="#rfc.xref.status.101.1"> 4</a>, <a class="iref" href="#rfc.iref.24"><b>8.1.2</b></a></li>1759 <li class="indline1">100 Continue (status code) <a class="iref" href="#rfc.xref.status.100.1">5</a>, <a class="iref" href="#rfc.iref.23"><b>9.1.1</b></a></li> 1760 <li class="indline1">101 Switching Protocols (status code) <a class="iref" href="#rfc.xref.status.101.1">5</a>, <a class="iref" href="#rfc.iref.24"><b>9.1.2</b></a></li> 1751 1761 </ul> 1752 1762 </li> 1753 1763 <li class="indline0"><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul class="ind"> 1754 <li class="indline1">200 OK (status code) <a class="iref" href="#rfc.xref.status.200.1"> 4</a>, <a class="iref" href="#rfc.iref.25"><b>8.2.1</b></a></li>1755 <li class="indline1">201 Created (status code) <a class="iref" href="#rfc.xref.status.201.1"> 4</a>, <a class="iref" href="#rfc.iref.26"><b>8.2.2</b></a>, <a class="iref" href="#rfc.xref.status.201.2">A.1</a></li>1756 <li class="indline1">202 Accepted (status code) <a class="iref" href="#rfc.xref.status.202.1"> 4</a>, <a class="iref" href="#rfc.iref.27"><b>8.2.3</b></a></li>1757 <li class="indline1">203 Non-Authoritative Information (status code) <a class="iref" href="#rfc.xref.status.203.1"> 4</a>, <a class="iref" href="#rfc.iref.28"><b>8.2.4</b></a></li>1758 <li class="indline1">204 No Content (status code) <a class="iref" href="#rfc.xref.status.204.1"> 4</a>, <a class="iref" href="#rfc.iref.29"><b>8.2.5</b></a></li>1759 <li class="indline1">205 Reset Content (status code) <a class="iref" href="#rfc.xref.status.205.1"> 4</a>, <a class="iref" href="#rfc.iref.30"><b>8.2.6</b></a></li>1760 <li class="indline1">206 Partial Content (status code) <a class="iref" href="#rfc.xref.status.206.1"> 4</a>, <a class="iref" href="#rfc.iref.31"><b>8.2.7</b></a></li>1764 <li class="indline1">200 OK (status code) <a class="iref" href="#rfc.xref.status.200.1">5</a>, <a class="iref" href="#rfc.iref.25"><b>9.2.1</b></a></li> 1765 <li class="indline1">201 Created (status code) <a class="iref" href="#rfc.xref.status.201.1">5</a>, <a class="iref" href="#rfc.iref.26"><b>9.2.2</b></a>, <a class="iref" href="#rfc.xref.status.201.2">A.1</a></li> 1766 <li class="indline1">202 Accepted (status code) <a class="iref" href="#rfc.xref.status.202.1">5</a>, <a class="iref" href="#rfc.iref.27"><b>9.2.3</b></a></li> 1767 <li class="indline1">203 Non-Authoritative Information (status code) <a class="iref" href="#rfc.xref.status.203.1">5</a>, <a class="iref" href="#rfc.iref.28"><b>9.2.4</b></a></li> 1768 <li class="indline1">204 No Content (status code) <a class="iref" href="#rfc.xref.status.204.1">5</a>, <a class="iref" href="#rfc.iref.29"><b>9.2.5</b></a></li> 1769 <li class="indline1">205 Reset Content (status code) <a class="iref" href="#rfc.xref.status.205.1">5</a>, <a class="iref" href="#rfc.iref.30"><b>9.2.6</b></a></li> 1770 <li class="indline1">206 Partial Content (status code) <a class="iref" href="#rfc.xref.status.206.1">5</a>, <a class="iref" href="#rfc.iref.31"><b>9.2.7</b></a></li> 1761 1771 </ul> 1762 1772 </li> 1763 1773 <li class="indline0"><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul class="ind"> 1764 <li class="indline1">300 Multiple Choices (status code) <a class="iref" href="#rfc.xref.status.300.1"> 4</a>, <a class="iref" href="#rfc.iref.32"><b>8.3.1</b></a></li>1765 <li class="indline1">301 Moved Permanently (status code) <a class="iref" href="#rfc.xref.status.301.1"> 4</a>, <a class="iref" href="#rfc.iref.33"><b>8.3.2</b></a>, <a class="iref" href="#rfc.xref.status.301.2">A.2</a></li>1766 <li class="indline1">302 Found (status code) <a class="iref" href="#rfc.xref.status.302.1"> 4</a>, <a class="iref" href="#rfc.iref.34"><b>8.3.3</b></a>, <a class="iref" href="#rfc.xref.status.302.2">A.2</a></li>1767 <li class="indline1">303 See Other (status code) <a class="iref" href="#rfc.xref.status.303.1"> 4</a>, <a class="iref" href="#rfc.iref.35"><b>8.3.4</b></a></li>1768 <li class="indline1">304 Not Modified (status code) <a class="iref" href="#rfc.xref.status.304.1"> 4</a>, <a class="iref" href="#rfc.iref.36"><b>8.3.5</b></a></li>1769 <li class="indline1">305 Use Proxy (status code) <a class="iref" href="#rfc.xref.status.305.1"> 4</a>, <a class="iref" href="#rfc.iref.37"><b>8.3.6</b></a></li>1770 <li class="indline1">306 (Unused) (status code) <a class="iref" href="#rfc.iref.38"><b> 8.3.7</b></a></li>1771 <li class="indline1">307 Temporary Redirect (status code) <a class="iref" href="#rfc.xref.status.307.1"> 4</a>, <a class="iref" href="#rfc.iref.39"><b>8.3.8</b></a>, <a class="iref" href="#rfc.xref.status.307.2">A.2</a></li>1774 <li class="indline1">300 Multiple Choices (status code) <a class="iref" href="#rfc.xref.status.300.1">5</a>, <a class="iref" href="#rfc.iref.32"><b>9.3.1</b></a></li> 1775 <li class="indline1">301 Moved Permanently (status code) <a class="iref" href="#rfc.xref.status.301.1">5</a>, <a class="iref" href="#rfc.iref.33"><b>9.3.2</b></a>, <a class="iref" href="#rfc.xref.status.301.2">A.2</a></li> 1776 <li class="indline1">302 Found (status code) <a class="iref" href="#rfc.xref.status.302.1">5</a>, <a class="iref" href="#rfc.iref.34"><b>9.3.3</b></a>, <a class="iref" href="#rfc.xref.status.302.2">A.2</a></li> 1777 <li class="indline1">303 See Other (status code) <a class="iref" href="#rfc.xref.status.303.1">5</a>, <a class="iref" href="#rfc.iref.35"><b>9.3.4</b></a></li> 1778 <li class="indline1">304 Not Modified (status code) <a class="iref" href="#rfc.xref.status.304.1">5</a>, <a class="iref" href="#rfc.iref.36"><b>9.3.5</b></a></li> 1779 <li class="indline1">305 Use Proxy (status code) <a class="iref" href="#rfc.xref.status.305.1">5</a>, <a class="iref" href="#rfc.iref.37"><b>9.3.6</b></a></li> 1780 <li class="indline1">306 (Unused) (status code) <a class="iref" href="#rfc.iref.38"><b>9.3.7</b></a></li> 1781 <li class="indline1">307 Temporary Redirect (status code) <a class="iref" href="#rfc.xref.status.307.1">5</a>, <a class="iref" href="#rfc.iref.39"><b>9.3.8</b></a>, <a class="iref" href="#rfc.xref.status.307.2">A.2</a></li> 1772 1782 </ul> 1773 1783 </li> 1774 1784 <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind"> 1775 <li class="indline1">400 Bad Request (status code) <a class="iref" href="#rfc.xref.status.400.1"> 4</a>, <a class="iref" href="#rfc.iref.40"><b>8.4.1</b></a></li>1776 <li class="indline1">401 Unauthorized (status code) <a class="iref" href="#rfc.xref.status.401.1"> 4</a>, <a class="iref" href="#rfc.iref.41"><b>8.4.2</b></a></li>1777 <li class="indline1">402 Payment Required (status code) <a class="iref" href="#rfc.xref.status.402.1"> 4</a>, <a class="iref" href="#rfc.iref.42"><b>8.4.3</b></a></li>1778 <li class="indline1">403 Forbidden (status code) <a class="iref" href="#rfc.xref.status.403.1"> 4</a>, <a class="iref" href="#rfc.iref.43"><b>8.4.4</b></a>, <a class="iref" href="#rfc.xref.status.403.2">A.1</a></li>1779 <li class="indline1">404 Not Found (status code) <a class="iref" href="#rfc.xref.status.404.1"> 4</a>, <a class="iref" href="#rfc.iref.44"><b>8.4.5</b></a>, <a class="iref" href="#rfc.xref.status.404.2">A.1</a></li>1780 <li class="indline1">405 Method Not Allowed (status code) <a class="iref" href="#rfc.xref.status.405.1"> 4</a>, <a class="iref" href="#rfc.iref.45"><b>8.4.6</b></a></li>1781 <li class="indline1">406 Not Acceptable (status code) <a class="iref" href="#rfc.xref.status.406.1"> 4</a>, <a class="iref" href="#rfc.iref.46"><b>8.4.7</b></a></li>1782 <li class="indline1">407 Proxy Authentication Required (status code) <a class="iref" href="#rfc.xref.status.407.1"> 4</a>, <a class="iref" href="#rfc.iref.47"><b>8.4.8</b></a></li>1783 <li class="indline1">408 Request Timeout (status code) <a class="iref" href="#rfc.xref.status.408.1"> 4</a>, <a class="iref" href="#rfc.iref.48"><b>8.4.9</b></a></li>1784 <li class="indline1">409 Conflict (status code) <a class="iref" href="#rfc.xref.status.409.1"> 4</a>, <a class="iref" href="#rfc.iref.49"><b>8.4.10</b></a></li>1785 <li class="indline1">410 Gone (status code) <a class="iref" href="#rfc.xref.status.410.1"> 4</a>, <a class="iref" href="#rfc.iref.50"><b>8.4.11</b></a>, <a class="iref" href="#rfc.xref.status.410.2">A.1</a></li>1786 <li class="indline1">411 Length Required (status code) <a class="iref" href="#rfc.xref.status.411.1"> 4</a>, <a class="iref" href="#rfc.iref.51"><b>8.4.12</b></a></li>1787 <li class="indline1">412 Precondition Failed (status code) <a class="iref" href="#rfc.xref.status.412.1"> 4</a>, <a class="iref" href="#rfc.iref.52"><b>8.4.13</b></a></li>1788 <li class="indline1">413 Request Entity Too Large (status code) <a class="iref" href="#rfc.xref.status.413.1"> 4</a>, <a class="iref" href="#rfc.iref.53"><b>8.4.14</b></a></li>1789 <li class="indline1">414 Request-URI Too Long (status code) <a class="iref" href="#rfc.xref.status.414.1"> 4</a>, <a class="iref" href="#rfc.iref.54"><b>8.4.15</b></a></li>1790 <li class="indline1">415 Unsupported Media Type (status code) <a class="iref" href="#rfc.xref.status.415.1"> 4</a>, <a class="iref" href="#rfc.iref.55"><b>8.4.16</b></a></li>1791 <li class="indline1">416 Requested Range Not Satisfiable (status code) <a class="iref" href="#rfc.xref.status.416.1"> 4</a>, <a class="iref" href="#rfc.iref.56"><b>8.4.17</b></a></li>1792 <li class="indline1">417 Expectation Failed (status code) <a class="iref" href="#rfc.xref.status.417.1"> 4</a>, <a class="iref" href="#rfc.iref.57"><b>8.4.18</b></a></li>1785 <li class="indline1">400 Bad Request (status code) <a class="iref" href="#rfc.xref.status.400.1">5</a>, <a class="iref" href="#rfc.iref.40"><b>9.4.1</b></a></li> 1786 <li class="indline1">401 Unauthorized (status code) <a class="iref" href="#rfc.xref.status.401.1">5</a>, <a class="iref" href="#rfc.iref.41"><b>9.4.2</b></a></li> 1787 <li class="indline1">402 Payment Required (status code) <a class="iref" href="#rfc.xref.status.402.1">5</a>, <a class="iref" href="#rfc.iref.42"><b>9.4.3</b></a></li> 1788 <li class="indline1">403 Forbidden (status code) <a class="iref" href="#rfc.xref.status.403.1">5</a>, <a class="iref" href="#rfc.iref.43"><b>9.4.4</b></a>, <a class="iref" href="#rfc.xref.status.403.2">A.1</a></li> 1789 <li class="indline1">404 Not Found (status code) <a class="iref" href="#rfc.xref.status.404.1">5</a>, <a class="iref" href="#rfc.iref.44"><b>9.4.5</b></a>, <a class="iref" href="#rfc.xref.status.404.2">A.1</a></li> 1790 <li class="indline1">405 Method Not Allowed (status code) <a class="iref" href="#rfc.xref.status.405.1">5</a>, <a class="iref" href="#rfc.iref.45"><b>9.4.6</b></a></li> 1791 <li class="indline1">406 Not Acceptable (status code) <a class="iref" href="#rfc.xref.status.406.1">5</a>, <a class="iref" href="#rfc.iref.46"><b>9.4.7</b></a></li> 1792 <li class="indline1">407 Proxy Authentication Required (status code) <a class="iref" href="#rfc.xref.status.407.1">5</a>, <a class="iref" href="#rfc.iref.47"><b>9.4.8</b></a></li> 1793 <li class="indline1">408 Request Timeout (status code) <a class="iref" href="#rfc.xref.status.408.1">5</a>, <a class="iref" href="#rfc.iref.48"><b>9.4.9</b></a></li> 1794 <li class="indline1">409 Conflict (status code) <a class="iref" href="#rfc.xref.status.409.1">5</a>, <a class="iref" href="#rfc.iref.49"><b>9.4.10</b></a></li> 1795 <li class="indline1">410 Gone (status code) <a class="iref" href="#rfc.xref.status.410.1">5</a>, <a class="iref" href="#rfc.iref.50"><b>9.4.11</b></a>, <a class="iref" href="#rfc.xref.status.410.2">A.1</a></li> 1796 <li class="indline1">411 Length Required (status code) <a class="iref" href="#rfc.xref.status.411.1">5</a>, <a class="iref" href="#rfc.iref.51"><b>9.4.12</b></a></li> 1797 <li class="indline1">412 Precondition Failed (status code) <a class="iref" href="#rfc.xref.status.412.1">5</a>, <a class="iref" href="#rfc.iref.52"><b>9.4.13</b></a></li> 1798 <li class="indline1">413 Request Entity Too Large (status code) <a class="iref" href="#rfc.xref.status.413.1">5</a>, <a class="iref" href="#rfc.iref.53"><b>9.4.14</b></a></li> 1799 <li class="indline1">414 Request-URI Too Long (status code) <a class="iref" href="#rfc.xref.status.414.1">5</a>, <a class="iref" href="#rfc.iref.54"><b>9.4.15</b></a></li> 1800 <li class="indline1">415 Unsupported Media Type (status code) <a class="iref" href="#rfc.xref.status.415.1">5</a>, <a class="iref" href="#rfc.iref.55"><b>9.4.16</b></a></li> 1801 <li class="indline1">416 Requested Range Not Satisfiable (status code) <a class="iref" href="#rfc.xref.status.416.1">5</a>, <a class="iref" href="#rfc.iref.56"><b>9.4.17</b></a></li> 1802 <li class="indline1">417 Expectation Failed (status code) <a class="iref" href="#rfc.xref.status.417.1">5</a>, <a class="iref" href="#rfc.iref.57"><b>9.4.18</b></a></li> 1793 1803 </ul> 1794 1804 </li> 1795 1805 <li class="indline0"><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul class="ind"> 1796 <li class="indline1">500 Internal Server Error (status code) <a class="iref" href="#rfc.xref.status.500.1"> 4</a>, <a class="iref" href="#rfc.iref.58"><b>8.5.1</b></a></li>1797 <li class="indline1">501 Not Implemented (status code) <a class="iref" href="#rfc.xref.status.501.1"> 4</a>, <a class="iref" href="#rfc.iref.59"><b>8.5.2</b></a></li>1798 <li class="indline1">502 Bad Gateway (status code) <a class="iref" href="#rfc.xref.status.502.1"> 4</a>, <a class="iref" href="#rfc.iref.60"><b>8.5.3</b></a></li>1799 <li class="indline1">503 Service Unavailable (status code) <a class="iref" href="#rfc.xref.status.503.1"> 4</a>, <a class="iref" href="#rfc.iref.61"><b>8.5.4</b></a></li>1800 <li class="indline1">504 Gateway Timeout (status code) <a class="iref" href="#rfc.xref.status.504.1"> 4</a>, <a class="iref" href="#rfc.iref.62"><b>8.5.5</b></a>, <a class="iref" href="#rfc.xref.status.504.2">A.1</a></li>1801 <li class="indline1">505 HTTP Version Not Supported (status code) <a class="iref" href="#rfc.xref.status.505.1"> 4</a>, <a class="iref" href="#rfc.iref.63"><b>8.5.6</b></a></li>1806 <li class="indline1">500 Internal Server Error (status code) <a class="iref" href="#rfc.xref.status.500.1">5</a>, <a class="iref" href="#rfc.iref.58"><b>9.5.1</b></a></li> 1807 <li class="indline1">501 Not Implemented (status code) <a class="iref" href="#rfc.xref.status.501.1">5</a>, <a class="iref" href="#rfc.iref.59"><b>9.5.2</b></a></li> 1808 <li class="indline1">502 Bad Gateway (status code) <a class="iref" href="#rfc.xref.status.502.1">5</a>, <a class="iref" href="#rfc.iref.60"><b>9.5.3</b></a></li> 1809 <li class="indline1">503 Service Unavailable (status code) <a class="iref" href="#rfc.xref.status.503.1">5</a>, <a class="iref" href="#rfc.iref.61"><b>9.5.4</b></a></li> 1810 <li class="indline1">504 Gateway Timeout (status code) <a class="iref" href="#rfc.xref.status.504.1">5</a>, <a class="iref" href="#rfc.iref.62"><b>9.5.5</b></a>, <a class="iref" href="#rfc.xref.status.504.2">A.1</a></li> 1811 <li class="indline1">505 HTTP Version Not Supported (status code) <a class="iref" href="#rfc.xref.status.505.1">5</a>, <a class="iref" href="#rfc.iref.63"><b>9.5.6</b></a></li> 1802 1812 </ul> 1803 1813 </li> 1804 1814 <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind"> 1805 <li class="indline1">Allow header <a class="iref" href="#rfc.xref.header.allow.1"> 2</a>, <a class="iref" href="#rfc.iref.a.1"><b>9.1</b></a></li>1815 <li class="indline1">Allow header <a class="iref" href="#rfc.xref.header.allow.1">3</a>, <a class="iref" href="#rfc.iref.a.1"><b>10.1</b></a></li> 1806 1816 </ul> 1807 1817 </li> 1808 1818 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind"> 1809 <li class="indline1">CONNECT method <a class="iref" href="#rfc.xref.CONNECT.1"> 2</a>, <a class="iref" href="#rfc.iref.c.1"><b>7.9</b></a></li>1819 <li class="indline1">CONNECT method <a class="iref" href="#rfc.xref.CONNECT.1">3</a>, <a class="iref" href="#rfc.iref.c.1"><b>8.9</b></a></li> 1810 1820 </ul> 1811 1821 </li> 1812 1822 <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind"> 1813 <li class="indline1">DELETE method <a class="iref" href="#rfc.xref.DELETE.1"> 2</a>, <a class="iref" href="#rfc.iref.d.1"><b>7.7</b></a></li>1823 <li class="indline1">DELETE method <a class="iref" href="#rfc.xref.DELETE.1">3</a>, <a class="iref" href="#rfc.iref.d.1"><b>8.7</b></a></li> 1814 1824 </ul> 1815 1825 </li> 1816 1826 <li class="indline0"><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul class="ind"> 1817 <li class="indline1">Expect header <a class="iref" href="#rfc.xref.header.expect.1"> 3</a>, <a class="iref" href="#rfc.xref.header.expect.2">8.4.18</a>, <a class="iref" href="#rfc.iref.e.1"><b>9.2</b></a></li>1827 <li class="indline1">Expect header <a class="iref" href="#rfc.xref.header.expect.1">4</a>, <a class="iref" href="#rfc.xref.header.expect.2">9.4.18</a>, <a class="iref" href="#rfc.iref.e.1"><b>10.2</b></a></li> 1818 1828 </ul> 1819 1829 </li> 1820 1830 <li class="indline0"><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul class="ind"> 1821 <li class="indline1">From header <a class="iref" href="#rfc.xref.header.from.1"> 3</a>, <a class="iref" href="#rfc.iref.f.1"><b>9.3</b></a></li>1831 <li class="indline1">From header <a class="iref" href="#rfc.xref.header.from.1">4</a>, <a class="iref" href="#rfc.iref.f.1"><b>10.3</b></a></li> 1822 1832 </ul> 1823 1833 </li> 1824 1834 <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind"> 1825 <li class="indline1">GET method <a class="iref" href="#rfc.xref.GET.1"> 2</a>, <a class="iref" href="#rfc.iref.g.8"><b>7.3</b></a></li>1835 <li class="indline1">GET method <a class="iref" href="#rfc.xref.GET.1">3</a>, <a class="iref" href="#rfc.iref.g.8"><b>8.3</b></a></li> 1826 1836 <li class="indline1"><tt>Grammar</tt> 1827 1837 <ul class="ind"> 1828 <li class="indline1"><tt>Allow</tt> <a class="iref" href="#rfc.iref.g.9"><b> 9.1</b></a></li>1829 <li class="indline1"><tt>Expect</tt> <a class="iref" href="#rfc.iref.g.10"><b> 9.2</b></a></li>1830 <li class="indline1"><tt>expect-params</tt> <a class="iref" href="#rfc.iref.g.13"><b> 9.2</b></a></li>1831 <li class="indline1"><tt>expectation</tt> <a class="iref" href="#rfc.iref.g.11"><b> 9.2</b></a></li>1832 <li class="indline1"><tt>expectation-extension</tt> <a class="iref" href="#rfc.iref.g.12"><b> 9.2</b></a></li>1833 <li class="indline1"><tt>extension-code</tt> <a class="iref" href="#rfc.iref.g.5"><b> 4</b></a></li>1834 <li class="indline1"><tt>extension-method</tt> <a class="iref" href="#rfc.iref.g.2"><b> 2</b></a></li>1835 <li class="indline1"><tt>From</tt> <a class="iref" href="#rfc.iref.g.14"><b> 9.3</b></a></li>1836 <li class="indline1"><tt>Location</tt> <a class="iref" href="#rfc.iref.g.15"><b> 9.4</b></a></li>1837 <li class="indline1"><tt>Max-Forwards</tt> <a class="iref" href="#rfc.iref.g.16"><b> 9.5</b></a></li>1838 <li class="indline1"><tt>Method</tt> <a class="iref" href="#rfc.iref.g.1"><b> 2</b></a></li>1839 <li class="indline1"><tt>Reason-Phrase</tt> <a class="iref" href="#rfc.iref.g.6"><b> 4</b></a></li>1840 <li class="indline1"><tt>Referer</tt> <a class="iref" href="#rfc.iref.g.17"><b> 9.6</b></a></li>1841 <li class="indline1"><tt>request-header</tt> <a class="iref" href="#rfc.iref.g.3"><b> 3</b></a></li>1842 <li class="indline1"><tt>response-header</tt> <a class="iref" href="#rfc.iref.g.7"><b> 5</b></a></li>1843 <li class="indline1"><tt>Retry-After</tt> <a class="iref" href="#rfc.iref.g.18"><b> 9.7</b></a></li>1844 <li class="indline1"><tt>Server</tt> <a class="iref" href="#rfc.iref.g.19"><b> 9.8</b></a></li>1845 <li class="indline1"><tt>Status-Code</tt> <a class="iref" href="#rfc.iref.g.4"><b> 4</b></a></li>1846 <li class="indline1"><tt>User-Agent</tt> <a class="iref" href="#rfc.iref.g.20"><b> 9.9</b></a></li>1838 <li class="indline1"><tt>Allow</tt> <a class="iref" href="#rfc.iref.g.9"><b>10.1</b></a></li> 1839 <li class="indline1"><tt>Expect</tt> <a class="iref" href="#rfc.iref.g.10"><b>10.2</b></a></li> 1840 <li class="indline1"><tt>expect-params</tt> <a class="iref" href="#rfc.iref.g.13"><b>10.2</b></a></li> 1841 <li class="indline1"><tt>expectation</tt> <a class="iref" href="#rfc.iref.g.11"><b>10.2</b></a></li> 1842 <li class="indline1"><tt>expectation-extension</tt> <a class="iref" href="#rfc.iref.g.12"><b>10.2</b></a></li> 1843 <li class="indline1"><tt>extension-code</tt> <a class="iref" href="#rfc.iref.g.5"><b>5</b></a></li> 1844 <li class="indline1"><tt>extension-method</tt> <a class="iref" href="#rfc.iref.g.2"><b>3</b></a></li> 1845 <li class="indline1"><tt>From</tt> <a class="iref" href="#rfc.iref.g.14"><b>10.3</b></a></li> 1846 <li class="indline1"><tt>Location</tt> <a class="iref" href="#rfc.iref.g.15"><b>10.4</b></a></li> 1847 <li class="indline1"><tt>Max-Forwards</tt> <a class="iref" href="#rfc.iref.g.16"><b>10.5</b></a></li> 1848 <li class="indline1"><tt>Method</tt> <a class="iref" href="#rfc.iref.g.1"><b>3</b></a></li> 1849 <li class="indline1"><tt>Reason-Phrase</tt> <a class="iref" href="#rfc.iref.g.6"><b>5</b></a></li> 1850 <li class="indline1"><tt>Referer</tt> <a class="iref" href="#rfc.iref.g.17"><b>10.6</b></a></li> 1851 <li class="indline1"><tt>request-header</tt> <a class="iref" href="#rfc.iref.g.3"><b>4</b></a></li> 1852 <li class="indline1"><tt>response-header</tt> <a class="iref" href="#rfc.iref.g.7"><b>6</b></a></li> 1853 <li class="indline1"><tt>Retry-After</tt> <a class="iref" href="#rfc.iref.g.18"><b>10.7</b></a></li> 1854 <li class="indline1"><tt>Server</tt> <a class="iref" href="#rfc.iref.g.19"><b>10.8</b></a></li> 1855 <li class="indline1"><tt>Status-Code</tt> <a class="iref" href="#rfc.iref.g.4"><b>5</b></a></li> 1856 <li class="indline1"><tt>User-Agent</tt> <a class="iref" href="#rfc.iref.g.20"><b>10.9</b></a></li> 1847 1857 </ul> 1848 1858 </li> … … 1850 1860 </li> 1851 1861 <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind"> 1852 <li class="indline1">HEAD method <a class="iref" href="#rfc.xref.HEAD.1"> 2</a>, <a class="iref" href="#rfc.iref.h.1"><b>7.4</b></a></li>1862 <li class="indline1">HEAD method <a class="iref" href="#rfc.xref.HEAD.1">3</a>, <a class="iref" href="#rfc.iref.h.1"><b>8.4</b></a></li> 1853 1863 <li class="indline1">Headers 1854 1864 <ul class="ind"> 1855 <li class="indline1">Allow <a class="iref" href="#rfc.xref.header.allow.1"> 2</a>, <a class="iref" href="#rfc.iref.h.2"><b>9.1</b></a></li>1856 <li class="indline1">Expect <a class="iref" href="#rfc.xref.header.expect.1"> 3</a>, <a class="iref" href="#rfc.xref.header.expect.2">8.4.18</a>, <a class="iref" href="#rfc.iref.h.3"><b>9.2</b></a></li>1857 <li class="indline1">From <a class="iref" href="#rfc.xref.header.from.1"> 3</a>, <a class="iref" href="#rfc.iref.h.4"><b>9.3</b></a></li>1858 <li class="indline1">Location <a class="iref" href="#rfc.xref.header.location.1"> 5</a>, <a class="iref" href="#rfc.xref.header.location.2">7.5</a>, <a class="iref" href="#rfc.iref.h.5"><b>9.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">A.2</a></li>1859 <li class="indline1">Max-Forwards <a class="iref" href="#rfc.xref.header.max-forwards.1"> 3</a>, <a class="iref" href="#rfc.xref.header.max-forwards.2">7.8</a>, <a class="iref" href="#rfc.iref.h.6"><b>9.5</b></a></li>1860 <li class="indline1">Referer <a class="iref" href="#rfc.xref.header.referer.1"> 3</a>, <a class="iref" href="#rfc.iref.h.7"><b>9.6</b></a></li>1861 <li class="indline1">Retry-After <a class="iref" href="#rfc.xref.header.retry-after.1"> 5</a>, <a class="iref" href="#rfc.iref.h.8"><b>9.7</b></a></li>1862 <li class="indline1">Server <a class="iref" href="#rfc.xref.header.server.1"> 5</a>, <a class="iref" href="#rfc.iref.h.9"><b>9.8</b></a>, <a class="iref" href="#rfc.xref.header.server.2">11.1</a>, <a class="iref" href="#rfc.xref.header.server.3">A.2</a></li>1863 <li class="indline1">User-Agent <a class="iref" href="#rfc.xref.header.user-agent.1"> 3</a>, <a class="iref" href="#rfc.iref.h.10"><b>9.9</b></a>, <a class="iref" href="#rfc.xref.header.user-agent.2">11.1</a></li>1865 <li class="indline1">Allow <a class="iref" href="#rfc.xref.header.allow.1">3</a>, <a class="iref" href="#rfc.iref.h.2"><b>10.1</b></a></li> 1866 <li class="indline1">Expect <a class="iref" href="#rfc.xref.header.expect.1">4</a>, <a class="iref" href="#rfc.xref.header.expect.2">9.4.18</a>, <a class="iref" href="#rfc.iref.h.3"><b>10.2</b></a></li> 1867 <li class="indline1">From <a class="iref" href="#rfc.xref.header.from.1">4</a>, <a class="iref" href="#rfc.iref.h.4"><b>10.3</b></a></li> 1868 <li class="indline1">Location <a class="iref" href="#rfc.xref.header.location.1">6</a>, <a class="iref" href="#rfc.xref.header.location.2">8.5</a>, <a class="iref" href="#rfc.iref.h.5"><b>10.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">A.2</a></li> 1869 <li class="indline1">Max-Forwards <a class="iref" href="#rfc.xref.header.max-forwards.1">4</a>, <a class="iref" href="#rfc.xref.header.max-forwards.2">8.8</a>, <a class="iref" href="#rfc.iref.h.6"><b>10.5</b></a></li> 1870 <li class="indline1">Referer <a class="iref" href="#rfc.xref.header.referer.1">4</a>, <a class="iref" href="#rfc.iref.h.7"><b>10.6</b></a></li> 1871 <li class="indline1">Retry-After <a class="iref" href="#rfc.xref.header.retry-after.1">6</a>, <a class="iref" href="#rfc.iref.h.8"><b>10.7</b></a></li> 1872 <li class="indline1">Server <a class="iref" href="#rfc.xref.header.server.1">6</a>, <a class="iref" href="#rfc.iref.h.9"><b>10.8</b></a>, <a class="iref" href="#rfc.xref.header.server.2">12.1</a>, <a class="iref" href="#rfc.xref.header.server.3">A.2</a></li> 1873 <li class="indline1">User-Agent <a class="iref" href="#rfc.xref.header.user-agent.1">4</a>, <a class="iref" href="#rfc.iref.h.10"><b>10.9</b></a>, <a class="iref" href="#rfc.xref.header.user-agent.2">12.1</a></li> 1864 1874 </ul> 1865 1875 </li> … … 1868 1878 <li class="indline0"><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul class="ind"> 1869 1879 <li class="indline1">LINK method <a class="iref" href="#rfc.iref.l.2"><b>A.1</b></a></li> 1870 <li class="indline1">Location header <a class="iref" href="#rfc.xref.header.location.1"> 5</a>, <a class="iref" href="#rfc.xref.header.location.2">7.5</a>, <a class="iref" href="#rfc.iref.l.1"><b>9.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">A.2</a></li>1871 <li class="indline1"><em>Luo1998</em> <a class="iref" href="#rfc.xref.Luo1998.1"> 7.9</a>, <a class="iref" href="#Luo1998"><b>13.2</b></a></li>1880 <li class="indline1">Location header <a class="iref" href="#rfc.xref.header.location.1">6</a>, <a class="iref" href="#rfc.xref.header.location.2">8.5</a>, <a class="iref" href="#rfc.iref.l.1"><b>10.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">A.2</a></li> 1881 <li class="indline1"><em>Luo1998</em> <a class="iref" href="#rfc.xref.Luo1998.1">8.9</a>, <a class="iref" href="#Luo1998"><b>14.2</b></a></li> 1872 1882 </ul> 1873 1883 </li> 1874 1884 <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind"> 1875 <li class="indline1">Max-Forwards header <a class="iref" href="#rfc.xref.header.max-forwards.1"> 3</a>, <a class="iref" href="#rfc.xref.header.max-forwards.2">7.8</a>, <a class="iref" href="#rfc.iref.m.9"><b>9.5</b></a></li>1885 <li class="indline1">Max-Forwards header <a class="iref" href="#rfc.xref.header.max-forwards.1">4</a>, <a class="iref" href="#rfc.xref.header.max-forwards.2">8.8</a>, <a class="iref" href="#rfc.iref.m.9"><b>10.5</b></a></li> 1876 1886 <li class="indline1">Methods 1877 1887 <ul class="ind"> 1878 <li class="indline1">CONNECT <a class="iref" href="#rfc.xref.CONNECT.1"> 2</a>, <a class="iref" href="#rfc.iref.m.8"><b>7.9</b></a></li>1879 <li class="indline1">DELETE <a class="iref" href="#rfc.xref.DELETE.1"> 2</a>, <a class="iref" href="#rfc.iref.m.6"><b>7.7</b></a></li>1880 <li class="indline1">GET <a class="iref" href="#rfc.xref.GET.1"> 2</a>, <a class="iref" href="#rfc.iref.m.2"><b>7.3</b></a></li>1881 <li class="indline1">HEAD <a class="iref" href="#rfc.xref.HEAD.1"> 2</a>, <a class="iref" href="#rfc.iref.m.3"><b>7.4</b></a></li>1888 <li class="indline1">CONNECT <a class="iref" href="#rfc.xref.CONNECT.1">3</a>, <a class="iref" href="#rfc.iref.m.8"><b>8.9</b></a></li> 1889 <li class="indline1">DELETE <a class="iref" href="#rfc.xref.DELETE.1">3</a>, <a class="iref" href="#rfc.iref.m.6"><b>8.7</b></a></li> 1890 <li class="indline1">GET <a class="iref" href="#rfc.xref.GET.1">3</a>, <a class="iref" href="#rfc.iref.m.2"><b>8.3</b></a></li> 1891 <li class="indline1">HEAD <a class="iref" href="#rfc.xref.HEAD.1">3</a>, <a class="iref" href="#rfc.iref.m.3"><b>8.4</b></a></li> 1882 1892 <li class="indline1">LINK <a class="iref" href="#rfc.iref.m.11"><b>A.1</b></a></li> 1883 <li class="indline1">OPTIONS <a class="iref" href="#rfc.xref.OPTIONS.1"> 2</a>, <a class="iref" href="#rfc.iref.m.1"><b>7.2</b></a>, <a class="iref" href="#rfc.xref.OPTIONS.2">9.5</a></li>1893 <li class="indline1">OPTIONS <a class="iref" href="#rfc.xref.OPTIONS.1">3</a>, <a class="iref" href="#rfc.iref.m.1"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.OPTIONS.2">10.5</a></li> 1884 1894 <li class="indline1">PATCH <a class="iref" href="#rfc.iref.m.10"><b>A.1</b></a></li> 1885 <li class="indline1">POST <a class="iref" href="#rfc.xref.POST.1"> 2</a>, <a class="iref" href="#rfc.iref.m.4"><b>7.5</b></a>, <a class="iref" href="#rfc.xref.POST.2">A.2</a></li>1886 <li class="indline1">PUT <a class="iref" href="#rfc.xref.PUT.1"> 2</a>, <a class="iref" href="#rfc.iref.m.5"><b>7.6</b></a></li>1887 <li class="indline1">TRACE <a class="iref" href="#rfc.xref.TRACE.1"> 2</a>, <a class="iref" href="#rfc.iref.m.7"><b>7.8</b></a>, <a class="iref" href="#rfc.xref.TRACE.2">9.5</a></li>1895 <li class="indline1">POST <a class="iref" href="#rfc.xref.POST.1">3</a>, <a class="iref" href="#rfc.iref.m.4"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.POST.2">A.2</a></li> 1896 <li class="indline1">PUT <a class="iref" href="#rfc.xref.PUT.1">3</a>, <a class="iref" href="#rfc.iref.m.5"><b>8.6</b></a></li> 1897 <li class="indline1">TRACE <a class="iref" href="#rfc.xref.TRACE.1">3</a>, <a class="iref" href="#rfc.iref.m.7"><b>8.8</b></a>, <a class="iref" href="#rfc.xref.TRACE.2">10.5</a></li> 1888 1898 <li class="indline1">UNLINK <a class="iref" href="#rfc.iref.m.12"><b>A.1</b></a></li> 1889 1899 </ul> … … 1892 1902 </li> 1893 1903 <li class="indline0"><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul class="ind"> 1894 <li class="indline1">OPTIONS method <a class="iref" href="#rfc.xref.OPTIONS.1"> 2</a>, <a class="iref" href="#rfc.iref.o.1"><b>7.2</b></a>, <a class="iref" href="#rfc.xref.OPTIONS.2">9.5</a></li>1904 <li class="indline1">OPTIONS method <a class="iref" href="#rfc.xref.OPTIONS.1">3</a>, <a class="iref" href="#rfc.iref.o.1"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.OPTIONS.2">10.5</a></li> 1895 1905 </ul> 1896 1906 </li> 1897 1907 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 1898 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1</a>, <a class="iref" href="#rfc.xref.Part1.2">3</a>, <a class="iref" href="#rfc.xref.Part1.3">3</a>, <a class="iref" href="#rfc.xref.Part1.4">6</a>, <a class="iref" href="#rfc.xref.Part1.5">7.8</a>, <a class="iref" href="#rfc.xref.Part1.6">8.1.1</a>, <a class="iref" href="#rfc.xref.Part1.7">8.5.6</a>, <a class="iref" href="#rfc.xref.Part1.8">9.2</a>, <a class="iref" href="#rfc.xref.Part1.9">9.8</a>, <a class="iref" href="#rfc.xref.Part1.10">9.8</a>, <a class="iref" href="#rfc.xref.Part1.11">9.9</a>, <a class="iref" href="#Part1"><b>13.1</b></a>, <a class="iref" href="#rfc.xref.Part1.12">A.2</a><ul class="ind"> 1899 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part1.7">8.5.6</a></li> 1900 <li class="indline1"><em>Section 3.5</em> <a class="iref" href="#rfc.xref.Part1.9">9.8</a>, <a class="iref" href="#rfc.xref.Part1.11">9.9</a></li> 1901 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.4">6</a></li> 1902 <li class="indline1"><em>Section 7.2.3</em> <a class="iref" href="#rfc.xref.Part1.6">8.1.1</a>, <a class="iref" href="#rfc.xref.Part1.8">9.2</a></li> 1903 <li class="indline1"><em>Section 8.4</em> <a class="iref" href="#rfc.xref.Part1.2">3</a></li> 1904 <li class="indline1"><em>Section 8.8</em> <a class="iref" href="#rfc.xref.Part1.3">3</a></li> 1905 <li class="indline1"><em>Section 8.9</em> <a class="iref" href="#rfc.xref.Part1.5">7.8</a>, <a class="iref" href="#rfc.xref.Part1.10">9.8</a>, <a class="iref" href="#rfc.xref.Part1.12">A.2</a></li> 1908 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">4</a>, <a class="iref" href="#rfc.xref.Part1.9">4</a>, <a class="iref" href="#rfc.xref.Part1.10">7</a>, <a class="iref" href="#rfc.xref.Part1.11">8.8</a>, <a class="iref" href="#rfc.xref.Part1.12">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.13">9.5.6</a>, <a class="iref" href="#rfc.xref.Part1.14">10.2</a>, <a class="iref" href="#rfc.xref.Part1.15">10.8</a>, <a class="iref" href="#rfc.xref.Part1.16">10.8</a>, <a class="iref" href="#rfc.xref.Part1.17">10.9</a>, <a class="iref" href="#Part1"><b>14.1</b></a>, <a class="iref" href="#rfc.xref.Part1.18">A.2</a><ul class="ind"> 1909 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.2">2</a></li> 1910 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a></li> 1911 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part1.13">9.5.6</a></li> 1912 <li class="indline1"><em>Section 3.5</em> <a class="iref" href="#rfc.xref.Part1.15">10.8</a>, <a class="iref" href="#rfc.xref.Part1.17">10.9</a></li> 1913 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.10">7</a></li> 1914 <li class="indline1"><em>Section 7.2.3</em> <a class="iref" href="#rfc.xref.Part1.12">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.14">10.2</a></li> 1915 <li class="indline1"><em>Section 8.4</em> <a class="iref" href="#rfc.xref.Part1.8">4</a></li> 1916 <li class="indline1"><em>Section 8.8</em> <a class="iref" href="#rfc.xref.Part1.9">4</a></li> 1917 <li class="indline1"><em>Section 8.9</em> <a class="iref" href="#rfc.xref.Part1.11">8.8</a>, <a class="iref" href="#rfc.xref.Part1.16">10.8</a>, <a class="iref" href="#rfc.xref.Part1.18">A.2</a></li> 1906 1918 </ul> 1907 1919 </li> 1908 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1"> 3</a>, <a class="iref" href="#rfc.xref.Part3.2">3</a>, <a class="iref" href="#rfc.xref.Part3.3">3</a>, <a class="iref" href="#rfc.xref.Part3.4">3</a>, <a class="iref" href="#rfc.xref.Part3.5">6</a>, <a class="iref" href="#rfc.xref.Part3.6">8.3.1</a>, <a class="iref" href="#rfc.xref.Part3.7">9.4</a>, <a class="iref" href="#Part3"><b>13.1</b></a><ul class="ind">1909 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.6">8.3.1</a></li>1910 <li class="indline1"><em>Section 5.1</em> <a class="iref" href="#rfc.xref.Part3.1">3</a></li>1911 <li class="indline1"><em>Section 5.2</em> <a class="iref" href="#rfc.xref.Part3.2">3</a></li>1912 <li class="indline1"><em>Section 5.3</em> <a class="iref" href="#rfc.xref.Part3.3">3</a></li>1913 <li class="indline1"><em>Section 5.4</em> <a class="iref" href="#rfc.xref.Part3.4">3</a></li>1914 <li class="indline1"><em>Section 5.7</em> <a class="iref" href="#rfc.xref.Part3.7">9.4</a></li>1920 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">4</a>, <a class="iref" href="#rfc.xref.Part3.2">4</a>, <a class="iref" href="#rfc.xref.Part3.3">4</a>, <a class="iref" href="#rfc.xref.Part3.4">4</a>, <a class="iref" href="#rfc.xref.Part3.5">7</a>, <a class="iref" href="#rfc.xref.Part3.6">9.3.1</a>, <a class="iref" href="#rfc.xref.Part3.7">10.4</a>, <a class="iref" href="#Part3"><b>14.1</b></a><ul class="ind"> 1921 <li class="indline1"><em>Section 5</em> <a class="iref" href="#rfc.xref.Part3.6">9.3.1</a></li> 1922 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part3.1">4</a></li> 1923 <li class="indline1"><em>Section 6.2</em> <a class="iref" href="#rfc.xref.Part3.2">4</a></li> 1924 <li class="indline1"><em>Section 6.3</em> <a class="iref" href="#rfc.xref.Part3.3">4</a></li> 1925 <li class="indline1"><em>Section 6.4</em> <a class="iref" href="#rfc.xref.Part3.4">4</a></li> 1926 <li class="indline1"><em>Section 6.7</em> <a class="iref" href="#rfc.xref.Part3.7">10.4</a></li> 1915 1927 </ul> 1916 1928 </li> 1917 <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1"> 3</a>, <a class="iref" href="#rfc.xref.Part4.2">3</a>, <a class="iref" href="#rfc.xref.Part4.3">3</a>, <a class="iref" href="#rfc.xref.Part4.4">3</a>, <a class="iref" href="#rfc.xref.Part4.5">5</a>, <a class="iref" href="#rfc.xref.Part4.6">8.2.2</a>, <a class="iref" href="#rfc.xref.Part4.7">8.3.5</a>, <a class="iref" href="#rfc.xref.Part4.8">8.4.13</a>, <a class="iref" href="#Part4"><b>13.1</b></a>, <a class="iref" href="#rfc.xref.Part4.9">B.2</a><ul class="ind">1918 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part4.5">5</a>, <a class="iref" href="#rfc.xref.Part4.6">8.2.2</a></li>1919 <li class="indline1"><em>Section 6.2</em> <a class="iref" href="#rfc.xref.Part4.1">3</a></li>1920 <li class="indline1"><em>Section 6.3</em> <a class="iref" href="#rfc.xref.Part4.2">3</a></li>1921 <li class="indline1"><em>Section 6.4</em> <a class="iref" href="#rfc.xref.Part4.3">3</a></li>1922 <li class="indline1"><em>Section 6.5</em> <a class="iref" href="#rfc.xref.Part4.4">3</a></li>1929 <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1">4</a>, <a class="iref" href="#rfc.xref.Part4.2">4</a>, <a class="iref" href="#rfc.xref.Part4.3">4</a>, <a class="iref" href="#rfc.xref.Part4.4">4</a>, <a class="iref" href="#rfc.xref.Part4.5">6</a>, <a class="iref" href="#rfc.xref.Part4.6">9.2.2</a>, <a class="iref" href="#rfc.xref.Part4.7">9.3.5</a>, <a class="iref" href="#rfc.xref.Part4.8">9.4.13</a>, <a class="iref" href="#Part4"><b>14.1</b></a>, <a class="iref" href="#rfc.xref.Part4.9">B.2</a><ul class="ind"> 1930 <li class="indline1"><em>Section 7.1</em> <a class="iref" href="#rfc.xref.Part4.5">6</a>, <a class="iref" href="#rfc.xref.Part4.6">9.2.2</a></li> 1931 <li class="indline1"><em>Section 7.2</em> <a class="iref" href="#rfc.xref.Part4.1">4</a></li> 1932 <li class="indline1"><em>Section 7.3</em> <a class="iref" href="#rfc.xref.Part4.2">4</a></li> 1933 <li class="indline1"><em>Section 7.4</em> <a class="iref" href="#rfc.xref.Part4.3">4</a></li> 1934 <li class="indline1"><em>Section 7.5</em> <a class="iref" href="#rfc.xref.Part4.4">4</a></li> 1923 1935 </ul> 1924 1936 </li> 1925 <li class="indline1"><em>Part5</em> <a class="iref" href="#rfc.xref.Part5.1"> 3</a>, <a class="iref" href="#rfc.xref.Part5.2">3</a>, <a class="iref" href="#rfc.xref.Part5.3">5</a>, <a class="iref" href="#rfc.xref.Part5.4">7.3</a>, <a class="iref" href="#rfc.xref.Part5.5">8.1.2</a>, <a class="iref" href="#rfc.xref.Part5.6">8.2.7</a>, <a class="iref" href="#rfc.xref.Part5.7">8.4.17</a>, <a class="iref" href="#Part5"><b>13.1</b></a><ul class="ind">1926 <li class="indline1"><em>Section 5.1</em> <a class="iref" href="#rfc.xref.Part5.3">5</a></li>1927 <li class="indline1"><em>Section 5.3</em> <a class="iref" href="#rfc.xref.Part5.1">3</a></li>1928 <li class="indline1"><em>Section 5.4</em> <a class="iref" href="#rfc.xref.Part5.2">3</a>, <a class="iref" href="#rfc.xref.Part5.4">7.3</a>, <a class="iref" href="#rfc.xref.Part5.5">8.1.2</a>, <a class="iref" href="#rfc.xref.Part5.7">8.4.17</a></li>1937 <li class="indline1"><em>Part5</em> <a class="iref" href="#rfc.xref.Part5.1">4</a>, <a class="iref" href="#rfc.xref.Part5.2">4</a>, <a class="iref" href="#rfc.xref.Part5.3">6</a>, <a class="iref" href="#rfc.xref.Part5.4">8.3</a>, <a class="iref" href="#rfc.xref.Part5.5">9.1.2</a>, <a class="iref" href="#rfc.xref.Part5.6">9.2.7</a>, <a class="iref" href="#rfc.xref.Part5.7">9.4.17</a>, <a class="iref" href="#Part5"><b>14.1</b></a><ul class="ind"> 1938 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part5.3">6</a></li> 1939 <li class="indline1"><em>Section 6.3</em> <a class="iref" href="#rfc.xref.Part5.1">4</a></li> 1940 <li class="indline1"><em>Section 6.4</em> <a class="iref" href="#rfc.xref.Part5.2">4</a>, <a class="iref" href="#rfc.xref.Part5.4">8.3</a>, <a class="iref" href="#rfc.xref.Part5.5">9.1.2</a>, <a class="iref" href="#rfc.xref.Part5.7">9.4.17</a></li> 1929 1941 </ul> 1930 1942 </li> 1931 <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1"> 5</a>, <a class="iref" href="#rfc.xref.Part6.2">5</a>, <a class="iref" href="#rfc.xref.Part6.3">7.3</a>, <a class="iref" href="#Part6"><b>13.1</b></a><ul class="ind">1932 <li class="indline1"><em>Section 1 5.1</em> <a class="iref" href="#rfc.xref.Part6.1">5</a></li>1933 <li class="indline1"><em>Section 1 5.5</em> <a class="iref" href="#rfc.xref.Part6.2">5</a></li>1943 <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1">6</a>, <a class="iref" href="#rfc.xref.Part6.2">6</a>, <a class="iref" href="#rfc.xref.Part6.3">8.3</a>, <a class="iref" href="#Part6"><b>14.1</b></a><ul class="ind"> 1944 <li class="indline1"><em>Section 16.1</em> <a class="iref" href="#rfc.xref.Part6.1">6</a></li> 1945 <li class="indline1"><em>Section 16.5</em> <a class="iref" href="#rfc.xref.Part6.2">6</a></li> 1934 1946 </ul> 1935 1947 </li> 1936 <li class="indline1"><em>Part7</em> <a class="iref" href="#rfc.xref.Part7.1"> 3</a>, <a class="iref" href="#rfc.xref.Part7.2">3</a>, <a class="iref" href="#rfc.xref.Part7.3">5</a>, <a class="iref" href="#rfc.xref.Part7.4">5</a>, <a class="iref" href="#rfc.xref.Part7.5">8.4.2</a>, <a class="iref" href="#rfc.xref.Part7.6">8.4.8</a>, <a class="iref" href="#Part7"><b>13.1</b></a><ul class="ind">1937 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part7.1">3</a></li>1938 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part7.3">5</a></li>1939 <li class="indline1"><em>Section 3.3</em> <a class="iref" href="#rfc.xref.Part7.2">3</a></li>1940 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.Part7.4">5</a></li>1948 <li class="indline1"><em>Part7</em> <a class="iref" href="#rfc.xref.Part7.1">4</a>, <a class="iref" href="#rfc.xref.Part7.2">4</a>, <a class="iref" href="#rfc.xref.Part7.3">6</a>, <a class="iref" href="#rfc.xref.Part7.4">6</a>, <a class="iref" href="#rfc.xref.Part7.5">9.4.2</a>, <a class="iref" href="#rfc.xref.Part7.6">9.4.8</a>, <a class="iref" href="#Part7"><b>14.1</b></a><ul class="ind"> 1949 <li class="indline1"><em>Section 4.1</em> <a class="iref" href="#rfc.xref.Part7.1">4</a></li> 1950 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part7.3">6</a></li> 1951 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part7.2">4</a></li> 1952 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part7.4">6</a></li> 1941 1953 </ul> 1942 1954 </li> 1943 1955 <li class="indline1">PATCH method <a class="iref" href="#rfc.iref.p.3"><b>A.1</b></a></li> 1944 <li class="indline1">POST method <a class="iref" href="#rfc.xref.POST.1"> 2</a>, <a class="iref" href="#rfc.iref.p.1"><b>7.5</b></a>, <a class="iref" href="#rfc.xref.POST.2">A.2</a></li>1945 <li class="indline1">PUT method <a class="iref" href="#rfc.xref.PUT.1"> 2</a>, <a class="iref" href="#rfc.iref.p.2"><b>7.6</b></a></li>1956 <li class="indline1">POST method <a class="iref" href="#rfc.xref.POST.1">3</a>, <a class="iref" href="#rfc.iref.p.1"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.POST.2">A.2</a></li> 1957 <li class="indline1">PUT method <a class="iref" href="#rfc.xref.PUT.1">3</a>, <a class="iref" href="#rfc.iref.p.2"><b>8.6</b></a></li> 1946 1958 </ul> 1947 1959 </li> 1948 1960 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"> 1949 <li class="indline1">Referer header <a class="iref" href="#rfc.xref.header.referer.1"> 3</a>, <a class="iref" href="#rfc.iref.r.1"><b>9.6</b></a></li>1950 <li class="indline1">Retry-After header <a class="iref" href="#rfc.xref.header.retry-after.1"> 5</a>, <a class="iref" href="#rfc.iref.r.2"><b>9.7</b></a></li>1951 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#rfc.xref.RFC1945.1"> 8.3.3</a>, <a class="iref" href="#RFC1945"><b>13.2</b></a></li>1952 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1"> 8.3.3</a>, <a class="iref" href="#rfc.xref.RFC2068.2">8.3.6</a>, <a class="iref" href="#RFC2068"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.3">A.1</a></li>1953 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>1 3.1</b></a></li>1954 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>1 3.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">B.1</a></li>1955 <li class="indline1"><em>RFC2822</em> <a class="iref" href="#rfc.xref.RFC2822.1"> 9.3</a>, <a class="iref" href="#RFC2822"><b>13.2</b></a><ul class="ind">1956 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.RFC2822.1"> 9.3</a></li>1961 <li class="indline1">Referer header <a class="iref" href="#rfc.xref.header.referer.1">4</a>, <a class="iref" href="#rfc.iref.r.1"><b>10.6</b></a></li> 1962 <li class="indline1">Retry-After header <a class="iref" href="#rfc.xref.header.retry-after.1">6</a>, <a class="iref" href="#rfc.iref.r.2"><b>10.7</b></a></li> 1963 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#rfc.xref.RFC1945.1">9.3.3</a>, <a class="iref" href="#RFC1945"><b>14.2</b></a></li> 1964 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">9.3.3</a>, <a class="iref" href="#rfc.xref.RFC2068.2">9.3.6</a>, <a class="iref" href="#RFC2068"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.3">A.1</a></li>