| 1 | <!DOCTYPE html |
|---|
| 2 | PUBLIC "-//W3C//DTD HTML 4.01//EN"> |
|---|
| 3 | <html lang="en"> |
|---|
| 4 | <head profile="http://www.w3.org/2006/03/hcard"> |
|---|
| 5 | <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> |
|---|
| 6 | <title>HTTP/1.1, part 6: Caching</title><style type="text/css" title="Xml2Rfc (sans serif)"> |
|---|
| 7 | a { |
|---|
| 8 | text-decoration: none; |
|---|
| 9 | } |
|---|
| 10 | a.smpl { |
|---|
| 11 | color: black; |
|---|
| 12 | } |
|---|
| 13 | a:hover { |
|---|
| 14 | text-decoration: underline; |
|---|
| 15 | } |
|---|
| 16 | a:active { |
|---|
| 17 | text-decoration: underline; |
|---|
| 18 | } |
|---|
| 19 | address { |
|---|
| 20 | margin-top: 1em; |
|---|
| 21 | margin-left: 2em; |
|---|
| 22 | font-style: normal; |
|---|
| 23 | } |
|---|
| 24 | body { |
|---|
| 25 | color: black; |
|---|
| 26 | font-family: verdana, helvetica, arial, sans-serif; |
|---|
| 27 | font-size: 10pt; |
|---|
| 28 | } |
|---|
| 29 | cite { |
|---|
| 30 | font-style: normal; |
|---|
| 31 | } |
|---|
| 32 | dd { |
|---|
| 33 | margin-right: 2em; |
|---|
| 34 | } |
|---|
| 35 | dl { |
|---|
| 36 | margin-left: 2em; |
|---|
| 37 | } |
|---|
| 38 | |
|---|
| 39 | dl.empty dd { |
|---|
| 40 | margin-top: .5em; |
|---|
| 41 | } |
|---|
| 42 | dl p { |
|---|
| 43 | margin-left: 0em; |
|---|
| 44 | } |
|---|
| 45 | dt { |
|---|
| 46 | margin-top: .5em; |
|---|
| 47 | } |
|---|
| 48 | h1 { |
|---|
| 49 | font-size: 14pt; |
|---|
| 50 | line-height: 21pt; |
|---|
| 51 | page-break-after: avoid; |
|---|
| 52 | } |
|---|
| 53 | h1.np { |
|---|
| 54 | page-break-before: always; |
|---|
| 55 | } |
|---|
| 56 | h1 a { |
|---|
| 57 | color: #333333; |
|---|
| 58 | } |
|---|
| 59 | h2 { |
|---|
| 60 | font-size: 12pt; |
|---|
| 61 | line-height: 15pt; |
|---|
| 62 | page-break-after: avoid; |
|---|
| 63 | } |
|---|
| 64 | h2 a { |
|---|
| 65 | color: black; |
|---|
| 66 | } |
|---|
| 67 | h3 { |
|---|
| 68 | font-size: 10pt; |
|---|
| 69 | page-break-after: avoid; |
|---|
| 70 | } |
|---|
| 71 | h3 a { |
|---|
| 72 | color: black; |
|---|
| 73 | } |
|---|
| 74 | h4 { |
|---|
| 75 | font-size: 10pt; |
|---|
| 76 | page-break-after: avoid; |
|---|
| 77 | } |
|---|
| 78 | h4 a { |
|---|
| 79 | color: black; |
|---|
| 80 | } |
|---|
| 81 | h5 { |
|---|
| 82 | font-size: 10pt; |
|---|
| 83 | page-break-after: avoid; |
|---|
| 84 | } |
|---|
| 85 | h5 a { |
|---|
| 86 | color: black; |
|---|
| 87 | } |
|---|
| 88 | img { |
|---|
| 89 | margin-left: 3em; |
|---|
| 90 | } |
|---|
| 91 | li { |
|---|
| 92 | margin-left: 2em; |
|---|
| 93 | margin-right: 2em; |
|---|
| 94 | } |
|---|
| 95 | ol { |
|---|
| 96 | margin-left: 2em; |
|---|
| 97 | margin-right: 2em; |
|---|
| 98 | } |
|---|
| 99 | ol p { |
|---|
| 100 | margin-left: 0em; |
|---|
| 101 | } |
|---|
| 102 | p { |
|---|
| 103 | margin-left: 2em; |
|---|
| 104 | margin-right: 2em; |
|---|
| 105 | } |
|---|
| 106 | pre { |
|---|
| 107 | margin-left: 3em; |
|---|
| 108 | background-color: lightyellow; |
|---|
| 109 | padding: .25em; |
|---|
| 110 | } |
|---|
| 111 | pre.text2 { |
|---|
| 112 | border-style: dotted; |
|---|
| 113 | border-width: 1px; |
|---|
| 114 | background-color: #f0f0f0; |
|---|
| 115 | width: 69em; |
|---|
| 116 | } |
|---|
| 117 | pre.inline { |
|---|
| 118 | background-color: white; |
|---|
| 119 | padding: 0em; |
|---|
| 120 | } |
|---|
| 121 | pre.text { |
|---|
| 122 | border-style: dotted; |
|---|
| 123 | border-width: 1px; |
|---|
| 124 | background-color: #f8f8f8; |
|---|
| 125 | width: 69em; |
|---|
| 126 | } |
|---|
| 127 | pre.drawing { |
|---|
| 128 | border-style: solid; |
|---|
| 129 | border-width: 1px; |
|---|
| 130 | background-color: #f8f8f8; |
|---|
| 131 | padding: 2em; |
|---|
| 132 | } |
|---|
| 133 | table { |
|---|
| 134 | margin-left: 2em; |
|---|
| 135 | } |
|---|
| 136 | table.header { |
|---|
| 137 | width: 95%; |
|---|
| 138 | font-size: 10pt; |
|---|
| 139 | color: white; |
|---|
| 140 | } |
|---|
| 141 | td.top { |
|---|
| 142 | vertical-align: top; |
|---|
| 143 | } |
|---|
| 144 | td.topnowrap { |
|---|
| 145 | vertical-align: top; |
|---|
| 146 | white-space: nowrap; |
|---|
| 147 | } |
|---|
| 148 | td.header { |
|---|
| 149 | background-color: gray; |
|---|
| 150 | width: 50%; |
|---|
| 151 | } |
|---|
| 152 | td.reference { |
|---|
| 153 | vertical-align: top; |
|---|
| 154 | white-space: nowrap; |
|---|
| 155 | padding-right: 1em; |
|---|
| 156 | } |
|---|
| 157 | thead { |
|---|
| 158 | display:table-header-group; |
|---|
| 159 | } |
|---|
| 160 | ul.toc { |
|---|
| 161 | list-style: none; |
|---|
| 162 | margin-left: 1.5em; |
|---|
| 163 | margin-right: 0em; |
|---|
| 164 | padding-left: 0em; |
|---|
| 165 | } |
|---|
| 166 | li.tocline0 { |
|---|
| 167 | line-height: 150%; |
|---|
| 168 | font-weight: bold; |
|---|
| 169 | font-size: 10pt; |
|---|
| 170 | margin-left: 0em; |
|---|
| 171 | margin-right: 0em; |
|---|
| 172 | } |
|---|
| 173 | li.tocline1 { |
|---|
| 174 | line-height: normal; |
|---|
| 175 | font-weight: normal; |
|---|
| 176 | font-size: 9pt; |
|---|
| 177 | margin-left: 0em; |
|---|
| 178 | margin-right: 0em; |
|---|
| 179 | } |
|---|
| 180 | li.tocline2 { |
|---|
| 181 | font-size: 0pt; |
|---|
| 182 | } |
|---|
| 183 | ul p { |
|---|
| 184 | margin-left: 0em; |
|---|
| 185 | } |
|---|
| 186 | ul.ind { |
|---|
| 187 | list-style: none; |
|---|
| 188 | margin-left: 1.5em; |
|---|
| 189 | margin-right: 0em; |
|---|
| 190 | padding-left: 0em; |
|---|
| 191 | } |
|---|
| 192 | li.indline0 { |
|---|
| 193 | font-weight: bold; |
|---|
| 194 | line-height: 200%; |
|---|
| 195 | margin-left: 0em; |
|---|
| 196 | margin-right: 0em; |
|---|
| 197 | } |
|---|
| 198 | li.indline1 { |
|---|
| 199 | font-weight: normal; |
|---|
| 200 | line-height: 150%; |
|---|
| 201 | margin-left: 0em; |
|---|
| 202 | margin-right: 0em; |
|---|
| 203 | } |
|---|
| 204 | .bcp14 { |
|---|
| 205 | font-style: normal; |
|---|
| 206 | text-transform: lowercase; |
|---|
| 207 | font-variant: small-caps; |
|---|
| 208 | } |
|---|
| 209 | .comment { |
|---|
| 210 | background-color: yellow; |
|---|
| 211 | } |
|---|
| 212 | .center { |
|---|
| 213 | text-align: center; |
|---|
| 214 | } |
|---|
| 215 | .error { |
|---|
| 216 | color: red; |
|---|
| 217 | font-style: italic; |
|---|
| 218 | font-weight: bold; |
|---|
| 219 | } |
|---|
| 220 | .figure { |
|---|
| 221 | font-weight: bold; |
|---|
| 222 | text-align: center; |
|---|
| 223 | font-size: 9pt; |
|---|
| 224 | } |
|---|
| 225 | .filename { |
|---|
| 226 | color: #333333; |
|---|
| 227 | font-weight: bold; |
|---|
| 228 | font-size: 12pt; |
|---|
| 229 | line-height: 21pt; |
|---|
| 230 | text-align: center; |
|---|
| 231 | } |
|---|
| 232 | .fn { |
|---|
| 233 | font-weight: bold; |
|---|
| 234 | } |
|---|
| 235 | .hidden { |
|---|
| 236 | display: none; |
|---|
| 237 | } |
|---|
| 238 | .left { |
|---|
| 239 | text-align: left; |
|---|
| 240 | } |
|---|
| 241 | .right { |
|---|
| 242 | text-align: right; |
|---|
| 243 | } |
|---|
| 244 | .title { |
|---|
| 245 | color: #990000; |
|---|
| 246 | font-size: 18pt; |
|---|
| 247 | line-height: 18pt; |
|---|
| 248 | font-weight: bold; |
|---|
| 249 | text-align: center; |
|---|
| 250 | margin-top: 36pt; |
|---|
| 251 | } |
|---|
| 252 | .vcardline { |
|---|
| 253 | display: block; |
|---|
| 254 | } |
|---|
| 255 | .warning { |
|---|
| 256 | font-size: 14pt; |
|---|
| 257 | background-color: yellow; |
|---|
| 258 | } |
|---|
| 259 | |
|---|
| 260 | |
|---|
| 261 | @media print { |
|---|
| 262 | .noprint { |
|---|
| 263 | display: none; |
|---|
| 264 | } |
|---|
| 265 | |
|---|
| 266 | a { |
|---|
| 267 | color: black; |
|---|
| 268 | text-decoration: none; |
|---|
| 269 | } |
|---|
| 270 | |
|---|
| 271 | table.header { |
|---|
| 272 | width: 90%; |
|---|
| 273 | } |
|---|
| 274 | |
|---|
| 275 | td.header { |
|---|
| 276 | width: 50%; |
|---|
| 277 | color: black; |
|---|
| 278 | background-color: white; |
|---|
| 279 | vertical-align: top; |
|---|
| 280 | font-size: 12pt; |
|---|
| 281 | } |
|---|
| 282 | |
|---|
| 283 | ul.toc a::after { |
|---|
| 284 | content: leader('.') target-counter(attr(href), page); |
|---|
| 285 | } |
|---|
| 286 | |
|---|
| 287 | a.iref { |
|---|
| 288 | content: target-counter(attr(href), page); |
|---|
| 289 | } |
|---|
| 290 | |
|---|
| 291 | .print2col { |
|---|
| 292 | column-count: 2; |
|---|
| 293 | -moz-column-count: 2; |
|---|
| 294 | column-fill: auto; |
|---|
| 295 | } |
|---|
| 296 | } |
|---|
| 297 | |
|---|
| 298 | @page { |
|---|
| 299 | @top-left { |
|---|
| 300 | content: "INTERNET DRAFT"; |
|---|
| 301 | } |
|---|
| 302 | @top-right { |
|---|
| 303 | content: "January 2008"; |
|---|
| 304 | } |
|---|
| 305 | @top-center { |
|---|
| 306 | content: "HTTP/1.1, Part 6"; |
|---|
| 307 | } |
|---|
| 308 | @bottom-left { |
|---|
| 309 | content: "Fielding, et al."; |
|---|
| 310 | } |
|---|
| 311 | @bottom-center { |
|---|
| 312 | content: "Standards Track"; |
|---|
| 313 | } |
|---|
| 314 | @bottom-right { |
|---|
| 315 | content: "[Page " counter(page) "]"; |
|---|
| 316 | } |
|---|
| 317 | } |
|---|
| 318 | |
|---|
| 319 | @page:first { |
|---|
| 320 | @top-left { |
|---|
| 321 | content: normal; |
|---|
| 322 | } |
|---|
| 323 | @top-right { |
|---|
| 324 | content: normal; |
|---|
| 325 | } |
|---|
| 326 | @top-center { |
|---|
| 327 | content: normal; |
|---|
| 328 | } |
|---|
| 329 | } |
|---|
| 330 | </style><link rel="Contents" href="#rfc.toc"> |
|---|
| 331 | <link rel="Author" href="#rfc.authors"> |
|---|
| 332 | <link rel="Copyright" href="#rfc.copyright"> |
|---|
| 333 | <link rel="Index" href="#rfc.index"> |
|---|
| 334 | <link rel="Chapter" title="1 Introduction" href="#rfc.section.1"> |
|---|
| 335 | <link rel="Chapter" title="2 Caching in HTTP" href="#rfc.section.2"> |
|---|
| 336 | <link rel="Chapter" title="3 Header Field Definitions" href="#rfc.section.3"> |
|---|
| 337 | <link rel="Chapter" title="4 IANA Considerations" href="#rfc.section.4"> |
|---|
| 338 | <link rel="Chapter" title="5 Security Considerations" href="#rfc.section.5"> |
|---|
| 339 | <link rel="Chapter" title="6 Acknowledgments" href="#rfc.section.6"> |
|---|
| 340 | <link rel="Chapter" href="#rfc.section.7" title="7 References"> |
|---|
| 341 | <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A"> |
|---|
| 342 | <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B"> |
|---|
| 343 | <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.354, 2007/12/31 13:43:05, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> |
|---|
| 344 | <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> |
|---|
| 345 | <meta name="DC.Creator" content="Fielding, R."> |
|---|
| 346 | <meta name="DC.Creator" content="Gettys, J."> |
|---|
| 347 | <meta name="DC.Creator" content="Mogul, J."> |
|---|
| 348 | <meta name="DC.Creator" content="Frystyk, H."> |
|---|
| 349 | <meta name="DC.Creator" content="Masinter, L."> |
|---|
| 350 | <meta name="DC.Creator" content="Leach, P."> |
|---|
| 351 | <meta name="DC.Creator" content="Berners-Lee, T."> |
|---|
| 352 | <meta name="DC.Creator" content="Lafon, Y."> |
|---|
| 353 | <meta name="DC.Creator" content="Reschke, J. F."> |
|---|
| 354 | <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> |
|---|
| 355 | <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-01"> |
|---|
| 356 | <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2068"> |
|---|
| 357 | <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> |
|---|
| 358 | <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> |
|---|
| 359 | </head> |
|---|
| 360 | <body> |
|---|
| 361 | <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1"> |
|---|
| 362 | <tr> |
|---|
| 363 | <td class="header left">Network Working Group</td> |
|---|
| 364 | <td class="header right">R. Fielding, Editor</td> |
|---|
| 365 | </tr> |
|---|
| 366 | <tr> |
|---|
| 367 | <td class="header left">Internet Draft</td> |
|---|
| 368 | <td class="header right">Day Software</td> |
|---|
| 369 | </tr> |
|---|
| 370 | <tr> |
|---|
| 371 | <td class="header left"> |
|---|
| 372 | <draft-ietf-httpbis-p6-cache-latest> |
|---|
| 373 | |
|---|
| 374 | </td> |
|---|
| 375 | <td class="header right">J. Gettys</td> |
|---|
| 376 | </tr> |
|---|
| 377 | <tr> |
|---|
| 378 | <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a>, |
|---|
| 379 | <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) |
|---|
| 380 | </td> |
|---|
| 381 | <td class="header right">One Laptop per Child</td> |
|---|
| 382 | </tr> |
|---|
| 383 | <tr> |
|---|
| 384 | <td class="header left">Intended status: Standards Track</td> |
|---|
| 385 | <td class="header right">J. Mogul</td> |
|---|
| 386 | </tr> |
|---|
| 387 | <tr> |
|---|
| 388 | <td class="header left">Expires: July 2008</td> |
|---|
| 389 | <td class="header right">HP</td> |
|---|
| 390 | </tr> |
|---|
| 391 | <tr> |
|---|
| 392 | <td class="header left"></td> |
|---|
| 393 | <td class="header right">H. Frystyk</td> |
|---|
| 394 | </tr> |
|---|
| 395 | <tr> |
|---|
| 396 | <td class="header left"></td> |
|---|
| 397 | <td class="header right">Microsoft</td> |
|---|
| 398 | </tr> |
|---|
| 399 | <tr> |
|---|
| 400 | <td class="header left"></td> |
|---|
| 401 | <td class="header right">L. Masinter</td> |
|---|
| 402 | </tr> |
|---|
| 403 | <tr> |
|---|
| 404 | <td class="header left"></td> |
|---|
| 405 | <td class="header right">Adobe Systems</td> |
|---|
| 406 | </tr> |
|---|
| 407 | <tr> |
|---|
| 408 | <td class="header left"></td> |
|---|
| 409 | <td class="header right">P. Leach</td> |
|---|
| 410 | </tr> |
|---|
| 411 | <tr> |
|---|
| 412 | <td class="header left"></td> |
|---|
| 413 | <td class="header right">Microsoft</td> |
|---|
| 414 | </tr> |
|---|
| 415 | <tr> |
|---|
| 416 | <td class="header left"></td> |
|---|
| 417 | <td class="header right">T. Berners-Lee</td> |
|---|
| 418 | </tr> |
|---|
| 419 | <tr> |
|---|
| 420 | <td class="header left"></td> |
|---|
| 421 | <td class="header right">W3C/MIT</td> |
|---|
| 422 | </tr> |
|---|
| 423 | <tr> |
|---|
| 424 | <td class="header left"></td> |
|---|
| 425 | <td class="header right">Y. Lafon, Editor</td> |
|---|
| 426 | </tr> |
|---|
| 427 | <tr> |
|---|
| 428 | <td class="header left"></td> |
|---|
| 429 | <td class="header right">W3C</td> |
|---|
| 430 | </tr> |
|---|
| 431 | <tr> |
|---|
| 432 | <td class="header left"></td> |
|---|
| 433 | <td class="header right">J. F. Reschke, Editor</td> |
|---|
| 434 | </tr> |
|---|
| 435 | <tr> |
|---|
| 436 | <td class="header left"></td> |
|---|
| 437 | <td class="header right">greenbytes</td> |
|---|
| 438 | </tr> |
|---|
| 439 | <tr> |
|---|
| 440 | <td class="header left"></td> |
|---|
| 441 | <td class="header right">January 2008</td> |
|---|
| 442 | </tr> |
|---|
| 443 | </table> |
|---|
| 444 | <p class="title">HTTP/1.1, part 6: Caching<br><span class="filename">draft-ietf-httpbis-p6-cache-latest</span></p> |
|---|
| 445 | <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1> |
|---|
| 446 | <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she |
|---|
| 447 | is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section |
|---|
| 448 | 6 of BCP 79. |
|---|
| 449 | </p> |
|---|
| 450 | <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note |
|---|
| 451 | that other groups may also distribute working documents as Internet-Drafts. |
|---|
| 452 | </p> |
|---|
| 453 | <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other |
|---|
| 454 | documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work |
|---|
| 455 | in progress”. |
|---|
| 456 | </p> |
|---|
| 457 | <p>The list of current Internet-Drafts can be accessed at <<a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>>. |
|---|
| 458 | </p> |
|---|
| 459 | <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. |
|---|
| 460 | </p> |
|---|
| 461 | <p>This Internet-Draft will expire in July 2008.</p> |
|---|
| 462 | <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> |
|---|
| 463 | <p>Copyright © The IETF Trust (2008). All Rights Reserved.</p> |
|---|
| 464 | <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> |
|---|
| 465 | <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information |
|---|
| 466 | systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the |
|---|
| 467 | seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part |
|---|
| 468 | 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response |
|---|
| 469 | messages. |
|---|
| 470 | </p> |
|---|
| 471 | <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> |
|---|
| 472 | <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues |
|---|
| 473 | list is at <<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>> and related documents (including fancy diffs) can be found at <<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>>. |
|---|
| 474 | </p> |
|---|
| 475 | <hr class="noprint"> |
|---|
| 476 | <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1> |
|---|
| 477 | <ul class="toc"> |
|---|
| 478 | <li class="tocline0">1. <a href="#introduction">Introduction</a><ul class="toc"> |
|---|
| 479 | <li class="tocline1">1.1 <a href="#intro.requirements">Requirements</a></li> |
|---|
| 480 | <li class="tocline1">1.2 <a href="#intro.terminology">Terminology</a></li> |
|---|
| 481 | <li class="tocline1">1.3 <a href="#delta.seconds">Delta Seconds</a></li> |
|---|
| 482 | </ul> |
|---|
| 483 | </li> |
|---|
| 484 | <li class="tocline0">2. <a href="#caching">Caching in HTTP</a><ul class="toc"> |
|---|
| 485 | <li class="tocline1">2.1 <a href="#caching.overview">Overview</a><ul class="toc"> |
|---|
| 486 | <li class="tocline1">2.1.1 <a href="#cache.correctness">Cache Correctness</a></li> |
|---|
| 487 | <li class="tocline1">2.1.2 <a href="#warnings">Warnings</a></li> |
|---|
| 488 | <li class="tocline1">2.1.3 <a href="#cache-control.mechanisms">Cache-control Mechanisms</a></li> |
|---|
| 489 | <li class="tocline1">2.1.4 <a href="#explicit.ua.warnings">Explicit User Agent Warnings</a></li> |
|---|
| 490 | <li class="tocline1">2.1.5 <a href="#exceptions.to.the.rules.and.warnings">Exceptions to the Rules and Warnings</a></li> |
|---|
| 491 | <li class="tocline1">2.1.6 <a href="#client-controlled.behavior">Client-controlled Behavior</a></li> |
|---|
| 492 | </ul> |
|---|
| 493 | </li> |
|---|
| 494 | <li class="tocline1">2.2 <a href="#expiration.model">Expiration Model</a><ul class="toc"> |
|---|
| 495 | <li class="tocline1">2.2.1 <a href="#server-specified.expiration">Server-Specified Expiration</a></li> |
|---|
| 496 | <li class="tocline1">2.2.2 <a href="#heuristic.expiration">Heuristic Expiration</a></li> |
|---|
| 497 | <li class="tocline1">2.2.3 <a href="#age.calculations">Age Calculations</a></li> |
|---|
| 498 | <li class="tocline1">2.2.4 <a href="#expiration.calculations">Expiration Calculations</a></li> |
|---|
| 499 | <li class="tocline1">2.2.5 <a href="#disambiguating.expiration.values">Disambiguating Expiration Values</a></li> |
|---|
| 500 | <li class="tocline1">2.2.6 <a href="#disambiguating.multiple.responses">Disambiguating Multiple Responses</a></li> |
|---|
| 501 | </ul> |
|---|
| 502 | </li> |
|---|
| 503 | <li class="tocline1">2.3 <a href="#validation.model">Validation Model</a><ul class="toc"> |
|---|
| 504 | <li class="tocline1">2.3.1 <a href="#last-modified.dates">Last-Modified Dates</a></li> |
|---|
| 505 | <li class="tocline1">2.3.2 <a href="#entity.tag.cache.validators">Entity Tag Cache Validators</a></li> |
|---|
| 506 | <li class="tocline1">2.3.3 <a href="#non-validating.conditionals">Non-validating Conditionals</a></li> |
|---|
| 507 | </ul> |
|---|
| 508 | </li> |
|---|
| 509 | <li class="tocline1">2.4 <a href="#response.cacheability">Response Cacheability</a></li> |
|---|
| 510 | <li class="tocline1">2.5 <a href="#constructing.responses.from.caches">Constructing Responses From Caches</a><ul class="toc"> |
|---|
| 511 | <li class="tocline1">2.5.1 <a href="#end-to-end.and.hop-by-hop.headers">End-to-end and Hop-by-hop Headers</a></li> |
|---|
| 512 | <li class="tocline1">2.5.2 <a href="#non-modifiable.headers">Non-modifiable Headers</a></li> |
|---|
| 513 | <li class="tocline1">2.5.3 <a href="#combining.headers">Combining Headers</a></li> |
|---|
| 514 | </ul> |
|---|
| 515 | </li> |
|---|
| 516 | <li class="tocline1">2.6 <a href="#caching.negotiated.responses">Caching Negotiated Responses</a></li> |
|---|
| 517 | <li class="tocline1">2.7 <a href="#shared.and.non-shared.caches">Shared and Non-Shared Caches</a></li> |
|---|
| 518 | <li class="tocline1">2.8 <a href="#errors.or.incomplete.response.cache.behavior">Errors or Incomplete Response Cache Behavior</a></li> |
|---|
| 519 | <li class="tocline1">2.9 <a href="#side.effects.of.get.and.head">Side Effects of GET and HEAD</a></li> |
|---|
| 520 | <li class="tocline1">2.10 <a href="#invalidation.after.updates.or.deletions">Invalidation After Updates or Deletions</a></li> |
|---|
| 521 | <li class="tocline1">2.11 <a href="#write-through.mandatory">Write-Through Mandatory</a></li> |
|---|
| 522 | <li class="tocline1">2.12 <a href="#cache.replacement">Cache Replacement</a></li> |
|---|
| 523 | <li class="tocline1">2.13 <a href="#history.lists">History Lists</a></li> |
|---|
| 524 | </ul> |
|---|
| 525 | </li> |
|---|
| 526 | <li class="tocline0">3. <a href="#header.fields">Header Field Definitions</a><ul class="toc"> |
|---|
| 527 | <li class="tocline1">3.1 <a href="#header.age">Age</a></li> |
|---|
| 528 | <li class="tocline1">3.2 <a href="#header.cache-control">Cache-Control</a><ul class="toc"> |
|---|
| 529 | <li class="tocline1">3.2.1 <a href="#what.is.cacheable">What is Cacheable</a></li> |
|---|
| 530 | <li class="tocline1">3.2.2 <a href="#what.may.be.stored.by.caches">What May be Stored by Caches</a></li> |
|---|
| 531 | <li class="tocline1">3.2.3 <a href="#modifications.of.the.basic.expiration.mechanism">Modifications of the Basic Expiration Mechanism</a></li> |
|---|
| 532 | <li class="tocline1">3.2.4 <a href="#cache.revalidation.and.reload.controls">Cache Revalidation and Reload Controls</a></li> |
|---|
| 533 | <li class="tocline1">3.2.5 <a href="#no-transform.directive">No-Transform Directive</a></li> |
|---|
| 534 | <li class="tocline1">3.2.6 <a href="#cache.control.extensions">Cache Control Extensions</a></li> |
|---|
| 535 | </ul> |
|---|
| 536 | </li> |
|---|
| 537 | <li class="tocline1">3.3 <a href="#header.expires">Expires</a></li> |
|---|
| 538 | <li class="tocline1">3.4 <a href="#header.pragma">Pragma</a></li> |
|---|
| 539 | <li class="tocline1">3.5 <a href="#header.vary">Vary</a></li> |
|---|
| 540 | <li class="tocline1">3.6 <a href="#header.warning">Warning</a></li> |
|---|
| 541 | </ul> |
|---|
| 542 | </li> |
|---|
| 543 | <li class="tocline0">4. <a href="#IANA.considerations">IANA Considerations</a></li> |
|---|
| 544 | <li class="tocline0">5. <a href="#security.considerations">Security Considerations</a></li> |
|---|
| 545 | <li class="tocline0">6. <a href="#ack">Acknowledgments</a></li> |
|---|
| 546 | <li class="tocline0">7. <a href="#rfc.references">References</a><ul class="toc"> |
|---|
| 547 | <li class="tocline1">7.1 <a href="#rfc.references.1">Normative References</a></li> |
|---|
| 548 | <li class="tocline1">7.2 <a href="#rfc.references.2">Informative References</a></li> |
|---|
| 549 | <li class="tocline1">7.3 <a href="#rfc.references.3">References (to be categorized)</a></li> |
|---|
| 550 | </ul> |
|---|
| 551 | </li> |
|---|
| 552 | <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li> |
|---|
| 553 | <li class="tocline0">A. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc"> |
|---|
| 554 | <li class="tocline1">A.1 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> |
|---|
| 555 | <li class="tocline1">A.2 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> |
|---|
| 556 | </ul> |
|---|
| 557 | </li> |
|---|
| 558 | <li class="tocline0">B. <a href="#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> |
|---|
| 559 | <li class="tocline1">B.1 <a href="#rfc.section.B.1">Since RFC2616</a></li> |
|---|
| 560 | <li class="tocline1">B.2 <a href="#rfc.section.B.2">Since draft-ietf-httpbis-p6-cache-00</a></li> |
|---|
| 561 | </ul> |
|---|
| 562 | </li> |
|---|
| 563 | <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li> |
|---|
| 564 | <li class="tocline0"><a href="#rfc.index">Index</a></li> |
|---|
| 565 | </ul> |
|---|
| 566 | <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a id="introduction" href="#introduction">Introduction</a></h1> |
|---|
| 567 | <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to caching response messages. Right now it only includes the extracted relevant |
|---|
| 568 | sections of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite> without edit. |
|---|
| 569 | </p> |
|---|
| 570 | <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a> <a id="intro.requirements" href="#intro.requirements">Requirements</a></h2> |
|---|
| 571 | <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" |
|---|
| 572 | in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>. |
|---|
| 573 | </p> |
|---|
| 574 | <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." |
|---|
| 575 | </p> |
|---|
| 576 | <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a> <a id="intro.terminology" href="#intro.terminology">Terminology</a></h2> |
|---|
| 577 | <p id="rfc.section.1.2.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p> |
|---|
| 578 | <p id="rfc.section.1.2.p.2"> <span id="rfc.iref.c.1"></span> <dfn>cache</dfn> |
|---|
| 579 | </p> |
|---|
| 580 | <dl class="empty"> |
|---|
| 581 | <dd>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion. |
|---|
| 582 | A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent |
|---|
| 583 | requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel. |
|---|
| 584 | </dd> |
|---|
| 585 | </dl> |
|---|
| 586 | <p id="rfc.section.1.2.p.3"> <span id="rfc.iref.c.2"></span> <dfn>cacheable</dfn> |
|---|
| 587 | </p> |
|---|
| 588 | <dl class="empty"> |
|---|
| 589 | <dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests. |
|---|
| 590 | The rules for determining the cacheability of HTTP responses are defined in <a href="#caching" title="Caching in HTTP">Section 2</a>. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular |
|---|
| 591 | request. |
|---|
| 592 | </dd> |
|---|
| 593 | </dl> |
|---|
| 594 | <p id="rfc.section.1.2.p.4"> <span id="rfc.iref.f.1"></span> <dfn>first-hand</dfn> |
|---|
| 595 | </p> |
|---|
| 596 | <dl class="empty"> |
|---|
| 597 | <dd>A response is first-hand if it comes directly and without unnecessary delay from the origin server, perhaps via one or more |
|---|
| 598 | proxies. A response is also first-hand if its validity has just been checked directly with the origin server. |
|---|
| 599 | </dd> |
|---|
| 600 | </dl> |
|---|
| 601 | <p id="rfc.section.1.2.p.5"> <span id="rfc.iref.e.1"></span> <dfn>explicit expiration time</dfn> |
|---|
| 602 | </p> |
|---|
| 603 | <dl class="empty"> |
|---|
| 604 | <dd>The time at which the origin server intends that an entity should no longer be returned by a cache without further validation.</dd> |
|---|
| 605 | </dl> |
|---|
| 606 | <p id="rfc.section.1.2.p.6"> <span id="rfc.iref.h.1"></span> <dfn>heuristic expiration time</dfn> |
|---|
| 607 | </p> |
|---|
| 608 | <dl class="empty"> |
|---|
| 609 | <dd>An expiration time assigned by a cache when no explicit expiration time is available.</dd> |
|---|
| 610 | </dl> |
|---|
| 611 | <p id="rfc.section.1.2.p.7"> <span id="rfc.iref.a.1"></span> <dfn>age</dfn> |
|---|
| 612 | </p> |
|---|
| 613 | <dl class="empty"> |
|---|
| 614 | <dd>The age of a response is the time since it was sent by, or successfully validated with, the origin server.</dd> |
|---|
| 615 | </dl> |
|---|
| 616 | <p id="rfc.section.1.2.p.8"> <span id="rfc.iref.f.2"></span> <dfn>freshness lifetime</dfn> |
|---|
| 617 | </p> |
|---|
| 618 | <dl class="empty"> |
|---|
| 619 | <dd>The length of time between the generation of a response and its expiration time.</dd> |
|---|
| 620 | </dl> |
|---|
| 621 | <p id="rfc.section.1.2.p.9"> <span id="rfc.iref.f.3"></span> <dfn>fresh</dfn> |
|---|
| 622 | </p> |
|---|
| 623 | <dl class="empty"> |
|---|
| 624 | <dd>A response is fresh if its age has not yet exceeded its freshness lifetime.</dd> |
|---|
| 625 | </dl> |
|---|
| 626 | <p id="rfc.section.1.2.p.10"> <span id="rfc.iref.s.1"></span> <dfn>stale</dfn> |
|---|
| 627 | </p> |
|---|
| 628 | <dl class="empty"> |
|---|
| 629 | <dd>A response is stale if its age has passed its freshness lifetime.</dd> |
|---|
| 630 | </dl> |
|---|
| 631 | <p id="rfc.section.1.2.p.11"> <span id="rfc.iref.s.2"></span> <dfn>semantically transparent</dfn> |
|---|
| 632 | </p> |
|---|
| 633 | <dl class="empty"> |
|---|
| 634 | <dd>A cache behaves in a "semantically transparent" manner, with respect to a particular response, when its use affects neither |
|---|
| 635 | the requesting client nor the origin server, except to improve performance. When a cache is semantically transparent, the |
|---|
| 636 | client receives exactly the same response (except for hop-by-hop headers) that it would have received had its request been |
|---|
| 637 | handled directly by the origin server. |
|---|
| 638 | </dd> |
|---|
| 639 | </dl> |
|---|
| 640 | <p id="rfc.section.1.2.p.12"> <span id="rfc.iref.v.1"></span> <dfn>validator</dfn> |
|---|
| 641 | </p> |
|---|
| 642 | <dl class="empty"> |
|---|
| 643 | <dd>A protocol element (e.g., an entity tag or a Last-Modified time) that is used to find out whether a cache entry is an equivalent |
|---|
| 644 | copy of an entity. |
|---|
| 645 | </dd> |
|---|
| 646 | </dl> |
|---|
| 647 | <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a> <a id="delta.seconds" href="#delta.seconds">Delta Seconds</a></h2> |
|---|
| 648 | <p id="rfc.section.1.3.p.1">Some HTTP header fields allow a time value to be specified as an integer number of seconds, represented in decimal, after |
|---|
| 649 | the time that the message was received. |
|---|
| 650 | </p> |
|---|
| 651 | <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span> delta-seconds = 1*DIGIT |
|---|
| 652 | </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="caching" href="#caching">Caching in HTTP</a></h1> |
|---|
| 653 | <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="caching.overview" href="#caching.overview">Overview</a></h2> |
|---|
| 654 | <p id="rfc.section.2.1.p.1">HTTP is typically used for distributed information systems, where performance can be improved by the use of response caches. |
|---|
| 655 | The HTTP/1.1 protocol includes a number of elements intended to make caching work as well as possible. Because these elements |
|---|
| 656 | are inextricable from other aspects of the protocol, and because they interact with each other, it is useful to describe the |
|---|
| 657 | basic caching design of HTTP separately from the detailed descriptions of methods, headers, response codes, etc. |
|---|
| 658 | </p> |
|---|
| 659 | <p id="rfc.section.2.1.p.2">Caching would be useless if it did not significantly improve performance. The goal of caching in HTTP/1.1 is to eliminate |
|---|
| 660 | the need to send requests in many cases, and to eliminate the need to send full responses in many other cases. The former |
|---|
| 661 | reduces the number of network round-trips required for many operations; we use an "expiration" mechanism for this purpose |
|---|
| 662 | (see <a href="#expiration.model" title="Expiration Model">Section 2.2</a>). The latter reduces network bandwidth requirements; we use a "validation" mechanism for this purpose (see <a href="#validation.model" title="Validation Model">Section 2.3</a>). |
|---|
| 663 | </p> |
|---|
| 664 | <p id="rfc.section.2.1.p.3">Requirements for performance, availability, and disconnected operation require us to be able to relax the goal of semantic |
|---|
| 665 | transparency. The HTTP/1.1 protocol allows origin servers, caches, and clients to explicitly reduce transparency when necessary. |
|---|
| 666 | However, because non-transparent operation may confuse non-expert users, and might be incompatible with certain server applications |
|---|
| 667 | (such as those for ordering merchandise), the protocol requires that transparency be relaxed |
|---|
| 668 | </p> |
|---|
| 669 | <ul> |
|---|
| 670 | <li>only by an explicit protocol-level request when relaxed by client or origin server</li> |
|---|
| 671 | <li>only with an explicit warning to the end user when relaxed by cache or client</li> |
|---|
| 672 | </ul> |
|---|
| 673 | <p id="rfc.section.2.1.p.4">Therefore, the HTTP/1.1 protocol provides these important elements: </p> |
|---|
| 674 | <ol> |
|---|
| 675 | <li>Protocol features that provide full semantic transparency when this is required by all parties.</li> |
|---|
| 676 | <li>Protocol features that allow an origin server or user agent to explicitly request and control non-transparent operation.</li> |
|---|
| 677 | <li>Protocol features that allow a cache to attach warnings to responses that do not preserve the requested approximation of semantic |
|---|
| 678 | transparency. |
|---|
| 679 | </li> |
|---|
| 680 | </ol> |
|---|
| 681 | <p id="rfc.section.2.1.p.5">A basic principle is that it must be possible for the clients to detect any potential relaxation of semantic transparency. </p> |
|---|
| 682 | <dl class="empty"> |
|---|
| 683 | <dd> <b>Note:</b> The server, cache, or client implementor might be faced with design decisions not explicitly discussed in this specification. |
|---|
| 684 | If a decision might affect semantic transparency, the implementor ought to err on the side of maintaining transparency unless |
|---|
| 685 | a careful and complete analysis shows significant benefits in breaking transparency. |
|---|
| 686 | </dd> |
|---|
| 687 | </dl> |
|---|
| 688 | <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a> <a id="cache.correctness" href="#cache.correctness">Cache Correctness</a></h3> |
|---|
| 689 | <p id="rfc.section.2.1.1.p.1">A correct cache <em class="bcp14">MUST</em> respond to a request with the most up-to-date response held by the cache that is appropriate to the request (see Sections <a href="#disambiguating.expiration.values" title="Disambiguating Expiration Values">2.2.5</a>, <a href="#disambiguating.multiple.responses" title="Disambiguating Multiple Responses">2.2.6</a>, and <a href="#cache.replacement" title="Cache Replacement">2.12</a>) which meets one of the following conditions: |
|---|
| 690 | </p> |
|---|
| 691 | <ol> |
|---|
| 692 | <li>It has been checked for equivalence with what the origin server would have returned by revalidating the response with the |
|---|
| 693 | origin server (<a href="#validation.model" title="Validation Model">Section 2.3</a>); |
|---|
| 694 | </li> |
|---|
| 695 | <li>It is "fresh enough" (see <a href="#expiration.model" title="Expiration Model">Section 2.2</a>). In the default case, this means it meets the least restrictive freshness requirement of the client, origin server, and |
|---|
| 696 | cache (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.1" title="Cache-Control">Section 3.2</a>); if the origin server so specifies, it is the freshness requirement of the origin server alone. If a stored response is |
|---|
| 697 | not "fresh enough" by the most restrictive freshness requirement of both the client and the origin server, in carefully considered |
|---|
| 698 | circumstances the cache <em class="bcp14">MAY</em> still return the response with the appropriate Warning header (see Sections <a href="#exceptions.to.the.rules.and.warnings" title="Exceptions to the Rules and Warnings">2.1.5</a> and <a href="#header.warning" id="rfc.xref.header.warning.1" title="Warning">3.6</a>), unless such a response is prohibited (e.g., by a "no-store" cache-directive, or by a "no-cache" cache-request-directive; |
|---|
| 699 | see <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section 3.2</a>). |
|---|
| 700 | </li> |
|---|
| 701 | <li>It is an appropriate 304 (Not Modified), 305 (Proxy Redirect), or error (4xx or 5xx) response message.</li> |
|---|
| 702 | </ol> |
|---|
| 703 | <p id="rfc.section.2.1.1.p.2">If the cache can not communicate with the origin server, then a correct cache <em class="bcp14">SHOULD</em> respond as above if the response can be correctly served from the cache; if not it <em class="bcp14">MUST</em> return an error or warning indicating that there was a communication failure. |
|---|
| 704 | </p> |
|---|
| 705 | <p id="rfc.section.2.1.1.p.3">If a cache receives a response (either an entire response, or a 304 (Not Modified) response) that it would normally forward |
|---|
| 706 | to the requesting client, and the received response is no longer fresh, the cache <em class="bcp14">SHOULD</em> forward it to the requesting client without adding a new Warning (but without removing any existing Warning headers). A cache <em class="bcp14">SHOULD NOT</em> attempt to revalidate a response simply because that response became stale in transit; this might lead to an infinite loop. |
|---|
| 707 | A user agent that receives a stale response without a Warning <em class="bcp14">MAY</em> display a warning indication to the user. |
|---|
| 708 | </p> |
|---|
| 709 | <h3 id="rfc.section.2.1.2"><a href="#rfc.section.2.1.2">2.1.2</a> <a id="warnings" href="#warnings">Warnings</a></h3> |
|---|
| 710 | <p id="rfc.section.2.1.2.p.1">Whenever a cache returns a response that is neither first-hand nor "fresh enough" (in the sense of condition 2 in <a href="#cache.correctness" title="Cache Correctness">Section 2.1.1</a>), it <em class="bcp14">MUST</em> attach a warning to that effect, using a Warning general-header. The Warning header and the currently defined warnings are |
|---|
| 711 | described in <a href="#header.warning" id="rfc.xref.header.warning.2" title="Warning">Section 3.6</a>. The warning allows clients to take appropriate action. |
|---|
| 712 | </p> |
|---|
| 713 | <p id="rfc.section.2.1.2.p.2">Warnings <em class="bcp14">MAY</em> be used for other purposes, both cache-related and otherwise. The use of a warning, rather than an error status code, distinguish |
|---|
| 714 | these responses from true failures. |
|---|
| 715 | </p> |
|---|
| 716 | <p id="rfc.section.2.1.2.p.3">Warnings are assigned three digit warn-codes. The first digit indicates whether the Warning <em class="bcp14">MUST</em> or <em class="bcp14">MUST NOT</em> be deleted from a stored cache entry after a successful revalidation: |
|---|
| 717 | </p> |
|---|
| 718 | <p id="rfc.section.2.1.2.p.4"> </p> |
|---|
| 719 | <dl> |
|---|
| 720 | <dt>1xx</dt> |
|---|
| 721 | <dd>Warnings that describe the freshness or revalidation status of the response, and so <em class="bcp14">MUST</em> be deleted after a successful revalidation. 1XX warn-codes <em class="bcp14">MAY</em> be generated by a cache only when validating a cached entry. It <em class="bcp14">MUST NOT</em> be generated by clients. |
|---|
| 722 | </dd> |
|---|
| 723 | <dt>2xx</dt> |
|---|
| 724 | <dd>Warnings that describe some aspect of the entity body or entity headers that is not rectified by a revalidation (for example, |
|---|
| 725 | a lossy compression of the entity bodies) and which <em class="bcp14">MUST NOT</em> be deleted after a successful revalidation. |
|---|
| 726 | </dd> |
|---|
| 727 | </dl> |
|---|
| 728 | <p id="rfc.section.2.1.2.p.5">See <a href="#header.warning" id="rfc.xref.header.warning.3" title="Warning">Section 3.6</a> for the definitions of the codes themselves. |
|---|
| 729 | </p> |
|---|
| 730 | <p id="rfc.section.2.1.2.p.6">HTTP/1.0 caches will cache all Warnings in responses, without deleting the ones in the first category. Warnings in responses |
|---|
| 731 | that are passed to HTTP/1.0 caches carry an extra warning-date field, which prevents a future HTTP/1.1 recipient from believing |
|---|
| 732 | an erroneously cached Warning. |
|---|
| 733 | </p> |
|---|
| 734 | <p id="rfc.section.2.1.2.p.7">Warnings also carry a warning text. The text <em class="bcp14">MAY</em> be in any appropriate natural language (perhaps based on the client's Accept headers), and include an <em class="bcp14">OPTIONAL</em> indication of what character set is used. |
|---|
| 735 | </p> |
|---|
| 736 | <p id="rfc.section.2.1.2.p.8">Multiple warnings <em class="bcp14">MAY</em> be attached to a response (either by the origin server or by a cache), including multiple warnings with the same code number. |
|---|
| 737 | For example, a server might provide the same warning with texts in both English and Basque. |
|---|
| 738 | </p> |
|---|
| 739 | <p id="rfc.section.2.1.2.p.9">When multiple warnings are attached to a response, it might not be practical or reasonable to display all of them to the user. |
|---|
| 740 | This version of HTTP does not specify strict priority rules for deciding which warnings to display and in what order, but |
|---|
| 741 | does suggest some heuristics. |
|---|
| 742 | </p> |
|---|
| 743 | <h3 id="rfc.section.2.1.3"><a href="#rfc.section.2.1.3">2.1.3</a> <a id="cache-control.mechanisms" href="#cache-control.mechanisms">Cache-control Mechanisms</a></h3> |
|---|
| 744 | <p id="rfc.section.2.1.3.p.1">The basic cache mechanisms in HTTP/1.1 (server-specified expiration times and validators) are implicit directives to caches. |
|---|
| 745 | In some cases, a server or client might need to provide explicit directives to the HTTP caches. We use the Cache-Control header |
|---|
| 746 | for this purpose. |
|---|
| 747 | </p> |
|---|
| 748 | <p id="rfc.section.2.1.3.p.2">The Cache-Control header allows a client or server to transmit a variety of directives in either requests or responses. These |
|---|
| 749 | directives typically override the default caching algorithms. As a general rule, if there is any apparent conflict between |
|---|
| 750 | header values, the most restrictive interpretation is applied (that is, the one that is most likely to preserve semantic transparency). |
|---|
| 751 | However, in some cases, cache-control directives are explicitly specified as weakening the approximation of semantic transparency |
|---|
| 752 | (for example, "max-stale" or "public"). |
|---|
| 753 | </p> |
|---|
| 754 | <p id="rfc.section.2.1.3.p.3">The cache-control directives are described in detail in <a href="#header.cache-control" id="rfc.xref.header.cache-control.3" title="Cache-Control">Section 3.2</a>. |
|---|
| 755 | </p> |
|---|
| 756 | <h3 id="rfc.section.2.1.4"><a href="#rfc.section.2.1.4">2.1.4</a> <a id="explicit.ua.warnings" href="#explicit.ua.warnings">Explicit User Agent Warnings</a></h3> |
|---|
| 757 | <p id="rfc.section.2.1.4.p.1">Many user agents make it possible for users to override the basic caching mechanisms. For example, the user agent might allow |
|---|
| 758 | the user to specify that cached entities (even explicitly stale ones) are never validated. Or the user agent might habitually |
|---|
| 759 | add "Cache-Control: max-stale=3600" to every request. The user agent <em class="bcp14">SHOULD NOT</em> default to either non-transparent behavior, or behavior that results in abnormally ineffective caching, but <em class="bcp14">MAY</em> be explicitly configured to do so by an explicit action of the user. |
|---|
| 760 | </p> |
|---|
| 761 | <p id="rfc.section.2.1.4.p.2">If the user has overridden the basic caching mechanisms, the user agent <em class="bcp14">SHOULD</em> explicitly indicate to the user whenever this results in the display of information that might not meet the server's transparency |
|---|
| 762 | requirements (in particular, if the displayed entity is known to be stale). Since the protocol normally allows the user agent |
|---|
| 763 | to determine if responses are stale or not, this indication need only be displayed when this actually happens. The indication |
|---|
| 764 | need not be a dialog box; it could be an icon (for example, a picture of a rotting fish) or some other indicator. |
|---|
| 765 | </p> |
|---|
| 766 | <p id="rfc.section.2.1.4.p.3">If the user has overridden the caching mechanisms in a way that would abnormally reduce the effectiveness of caches, the user |
|---|
| 767 | agent <em class="bcp14">SHOULD</em> continually indicate this state to the user (for example, by a display of a picture of currency in flames) so that the user |
|---|
| 768 | does not inadvertently consume excess resources or suffer from excessive latency. |
|---|
| 769 | </p> |
|---|
| 770 | <h3 id="rfc.section.2.1.5"><a href="#rfc.section.2.1.5">2.1.5</a> <a id="exceptions.to.the.rules.and.warnings" href="#exceptions.to.the.rules.and.warnings">Exceptions to the Rules and Warnings</a></h3> |
|---|
| 771 | <p id="rfc.section.2.1.5.p.1">In some cases, the operator of a cache <em class="bcp14">MAY</em> choose to configure it to return stale responses even when not requested by clients. This decision ought not be made lightly, |
|---|
| 772 | but may be necessary for reasons of availability or performance, especially when the cache is poorly connected to the origin |
|---|
| 773 | server. Whenever a cache returns a stale response, it <em class="bcp14">MUST</em> mark it as such (using a Warning header) enabling the client software to alert the user that there might be a potential problem. |
|---|
| 774 | </p> |
|---|
| 775 | <p id="rfc.section.2.1.5.p.2">It also allows the user agent to take steps to obtain a first-hand or fresh response. For this reason, a cache <em class="bcp14">SHOULD NOT</em> return a stale response if the client explicitly requests a first-hand or fresh one, unless it is impossible to comply for |
|---|
| 776 | technical or policy reasons. |
|---|
| 777 | </p> |
|---|
| 778 | <h3 id="rfc.section.2.1.6"><a href="#rfc.section.2.1.6">2.1.6</a> <a id="client-controlled.behavior" href="#client-controlled.behavior">Client-controlled Behavior</a></h3> |
|---|
| 779 | <p id="rfc.section.2.1.6.p.1">While the origin server (and to a lesser extent, intermediate caches, by their contribution to the age of a response) are |
|---|
| 780 | the primary source of expiration information, in some cases the client might need to control a cache's decision about whether |
|---|
| 781 | to return a cached response without validating it. Clients do this using several directives of the Cache-Control header. |
|---|
| 782 | </p> |
|---|
| 783 | <p id="rfc.section.2.1.6.p.2">A client's request <em class="bcp14">MAY</em> specify the maximum age it is willing to accept of an unvalidated response; specifying a value of zero forces the cache(s) |
|---|
| 784 | to revalidate all responses. A client <em class="bcp14">MAY</em> also specify the minimum time remaining before a response expires. Both of these options increase constraints on the behavior |
|---|
| 785 | of caches, and so cannot further relax the cache's approximation of semantic transparency. |
|---|
| 786 | </p> |
|---|
| 787 | <p id="rfc.section.2.1.6.p.3">A client <em class="bcp14">MAY</em> also specify that it will accept stale responses, up to some maximum amount of staleness. This loosens the constraints on |
|---|
| 788 | the caches, and so might violate the origin server's specified constraints on semantic transparency, but might be necessary |
|---|
| 789 | to support disconnected operation, or high availability in the face of poor connectivity. |
|---|
| 790 | </p> |
|---|
| 791 | <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a> <a id="expiration.model" href="#expiration.model">Expiration Model</a></h2> |
|---|
| 792 | <h3 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a> <a id="server-specified.expiration" href="#server-specified.expiration">Server-Specified Expiration</a></h3> |
|---|
| 793 | <p id="rfc.section.2.2.1.p.1">HTTP caching works best when caches can entirely avoid making requests to the origin server. The primary mechanism for avoiding |
|---|
| 794 | requests is for an origin server to provide an explicit expiration time in the future, indicating that a response <em class="bcp14">MAY</em> be used to satisfy subsequent requests. In other words, a cache can return a fresh response without first contacting the server. |
|---|
| 795 | </p> |
|---|
| 796 | <p id="rfc.section.2.2.1.p.2">Our expectation is that servers will assign future explicit expiration times to responses in the belief that the entity is |
|---|
| 797 | not likely to change, in a semantically significant way, before the expiration time is reached. This normally preserves semantic |
|---|
| 798 | transparency, as long as the server's expiration times are carefully chosen. |
|---|
| 799 | </p> |
|---|
| 800 | <p id="rfc.section.2.2.1.p.3">The expiration mechanism applies only to responses taken from a cache and not to first-hand responses forwarded immediately |
|---|
| 801 | to the requesting client. |
|---|
| 802 | </p> |
|---|
| 803 | <p id="rfc.section.2.2.1.p.4">If an origin server wishes to force a semantically transparent cache to validate every request, it <em class="bcp14">MAY</em> assign an explicit expiration time in the past. This means that the response is always stale, and so the cache <em class="bcp14">SHOULD</em> validate it before using it for subsequent requests. See <a href="#cache.revalidation.and.reload.controls" title="Cache Revalidation and Reload Controls">Section 3.2.4</a> for a more restrictive way to force revalidation. |
|---|
| 804 | </p> |
|---|
| 805 | <p id="rfc.section.2.2.1.p.5">If an origin server wishes to force any HTTP/1.1 cache, no matter how it is configured, to validate every request, it <em class="bcp14">SHOULD</em> use the "must-revalidate" cache-control directive (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.4" title="Cache-Control">Section 3.2</a>). |
|---|
| 806 | </p> |
|---|
| 807 | <p id="rfc.section.2.2.1.p.6">Servers specify explicit expiration times using either the Expires header, or the max-age directive of the Cache-Control header.</p> |
|---|
| 808 | <p id="rfc.section.2.2.1.p.7">An expiration time cannot be used to force a user agent to refresh its display or reload a resource; its semantics apply only |
|---|
| 809 | to caching mechanisms, and such mechanisms need only check a resource's expiration status when a new request for that resource |
|---|
| 810 | is initiated. See <a href="#history.lists" title="History Lists">Section 2.13</a> for an explanation of the difference between caches and history mechanisms. |
|---|
| 811 | </p> |
|---|
| 812 | <h3 id="rfc.section.2.2.2"><a href="#rfc.section.2.2.2">2.2.2</a> <a id="heuristic.expiration" href="#heuristic.expiration">Heuristic Expiration</a></h3> |
|---|
| 813 | <p id="rfc.section.2.2.2.p.1">Since origin servers do not always provide explicit expiration times, HTTP caches typically assign heuristic expiration times, |
|---|
| 814 | employing algorithms that use other header values (such as the Last-Modified time) to estimate a plausible expiration time. |
|---|
| 815 | The HTTP/1.1 specification does not provide specific algorithms, but does impose worst-case constraints on their results. |
|---|
| 816 | Since heuristic expiration times might compromise semantic transparency, they ought to be used cautiously, and we encourage |
|---|
| 817 | origin servers to provide explicit expiration times as much as possible. |
|---|
| 818 | </p> |
|---|
| 819 | <h3 id="rfc.section.2.2.3"><a href="#rfc.section.2.2.3">2.2.3</a> <a id="age.calculations" href="#age.calculations">Age Calculations</a></h3> |
|---|
| 820 | <p id="rfc.section.2.2.3.p.1">In order to know if a cached entry is fresh, a cache needs to know if its age exceeds its freshness lifetime. We discuss how |
|---|
| 821 | to calculate the latter in <a href="#expiration.calculations" title="Expiration Calculations">Section 2.2.4</a>; this section describes how to calculate the age of a response or cache entry. |
|---|
| 822 | </p> |
|---|
| 823 | <p id="rfc.section.2.2.3.p.2">In this discussion, we use the term "now" to mean "the current value of the clock at the host performing the calculation." |
|---|
| 824 | Hosts that use HTTP, but especially hosts running origin servers and caches, <em class="bcp14">SHOULD</em> use NTP <a href="#RFC1305" id="rfc.xref.RFC1305.1"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a> or some similar protocol to synchronize their clocks to a globally accurate time standard. |
|---|
| 825 | </p> |
|---|
| 826 | <p id="rfc.section.2.2.3.p.3">HTTP/1.1 requires origin servers to send a Date header, if possible, with every response, giving the time at which the response |
|---|
| 827 | was generated (see <a href="p1-messaging.html#header.date" title="Date">Section 8.3</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). We use the term "date_value" to denote the value of the Date header, in a form appropriate for arithmetic operations. |
|---|
| 828 | </p> |
|---|
| 829 | <p id="rfc.section.2.2.3.p.4">HTTP/1.1 uses the Age response-header to convey the estimated age of the response message when obtained from a cache. The |
|---|
| 830 | Age field value is the cache's estimate of the amount of time since the response was generated or revalidated by the origin |
|---|
| 831 | server. |
|---|
| 832 | </p> |
|---|
| 833 | <p id="rfc.section.2.2.3.p.5">In essence, the Age value is the sum of the time that the response has been resident in each of the caches along the path |
|---|
| 834 | from the origin server, plus the amount of time it has been in transit along network paths. |
|---|
| 835 | </p> |
|---|
| 836 | <p id="rfc.section.2.2.3.p.6">We use the term "age_value" to denote the value of the Age header, in a form appropriate for arithmetic operations.</p> |
|---|
| 837 | <p id="rfc.section.2.2.3.p.7">A response's age can be calculated in two entirely independent ways: </p> |
|---|
| 838 | <ol> |
|---|
| 839 | <li>now minus date_value, if the local clock is reasonably well synchronized to the origin server's clock. If the result is negative, |
|---|
| 840 | the result is replaced by zero. |
|---|
| 841 | </li> |
|---|
| 842 | <li>age_value, if all of the caches along the response path implement HTTP/1.1.</li> |
|---|
| 843 | </ol> |
|---|
| 844 | <p id="rfc.section.2.2.3.p.8">Given that we have two independent ways to compute the age of a response when it is received, we can combine these as</p> |
|---|
| 845 | <div id="rfc.figure.u.2"></div><pre class="text"> corrected_received_age = max(now - date_value, age_value) |
|---|
| 846 | </pre><p id="rfc.section.2.2.3.p.10">and as long as we have either nearly synchronized clocks or all-HTTP/1.1 paths, one gets a reliable (conservative) result.</p> |
|---|
| 847 | <p id="rfc.section.2.2.3.p.11">Because of network-imposed delays, some significant interval might pass between the time that a server generates a response |
|---|
| 848 | and the time it is received at the next outbound cache or client. If uncorrected, this delay could result in improperly low |
|---|
| 849 | ages. |
|---|
| 850 | </p> |
|---|
| 851 | <p id="rfc.section.2.2.3.p.12">Because the request that resulted in the returned Age value must have been initiated prior to that Age value's generation, |
|---|
| 852 | we can correct for delays imposed by the network by recording the time at which the request was initiated. Then, when an Age |
|---|
| 853 | value is received, it <em class="bcp14">MUST</em> be interpreted relative to the time the request was initiated, not the time that the response was received. This algorithm |
|---|
| 854 | results in conservative behavior no matter how much delay is experienced. So, we compute: |
|---|
| 855 | </p> |
|---|
| 856 | <div id="rfc.figure.u.3"></div><pre class="text"> corrected_initial_age = corrected_received_age |
|---|
| 857 | + (now - request_time) |
|---|
| 858 | </pre><p id="rfc.section.2.2.3.p.14">where "request_time" is the time (according to the local clock) when the request that elicited this response was sent.</p> |
|---|
| 859 | <p id="rfc.section.2.2.3.p.15">Summary of age calculation algorithm, when a cache receives a response:</p> |
|---|
| 860 | <div id="rfc.figure.u.4"></div><pre class="text"> /* |
|---|
| 861 | * age_value |
|---|
| 862 | * is the value of Age: header received by the cache with |
|---|
| 863 | * this response. |
|---|
| 864 | * date_value |
|---|
| 865 | * is the value of the origin server's Date: header |
|---|
| 866 | * request_time |
|---|
| 867 | * is the (local) time when the cache made the request |
|---|
| 868 | * that resulted in this cached response |
|---|
| 869 | * response_time |
|---|
| 870 | * is the (local) time when the cache received the |
|---|
| 871 | * response |
|---|
| 872 | * now |
|---|
| 873 | * is the current (local) time |
|---|
| 874 | */ |
|---|
| 875 | |
|---|
| 876 | apparent_age = max(0, response_time - date_value); |
|---|
| 877 | corrected_received_age = max(apparent_age, age_value); |
|---|
| 878 | response_delay = response_time - request_time; |
|---|
| 879 | corrected_initial_age = corrected_received_age + response_delay; |
|---|
| 880 | resident_time = now - response_time; |
|---|
| 881 | current_age = corrected_initial_age + resident_time; |
|---|
| 882 | </pre><p id="rfc.section.2.2.3.p.17">The current_age of a cache entry is calculated by adding the amount of time (in seconds) since the cache entry was last validated |
|---|
| 883 | by the origin server to the corrected_initial_age. When a response is generated from a cache entry, the cache <em class="bcp14">MUST</em> include a single Age header field in the response with a value equal to the cache entry's current_age. |
|---|
| 884 | </p> |
|---|
| 885 | <p id="rfc.section.2.2.3.p.18">The presence of an Age header field in a response implies that a response is not first-hand. However, the converse is not |
|---|
| 886 | true, since the lack of an Age header field in a response does not imply that the response is first-hand unless all caches |
|---|
| 887 | along the request path are compliant with HTTP/1.1 (i.e., older HTTP caches did not implement the Age header field). |
|---|
| 888 | </p> |
|---|
| 889 | <h3 id="rfc.section.2.2.4"><a href="#rfc.section.2.2.4">2.2.4</a> <a id="expiration.calculations" href="#expiration.calculations">Expiration Calculations</a></h3> |
|---|
| 890 | <p id="rfc.section.2.2.4.p.1">In order to decide whether a response is fresh or stale, we need to compare its freshness lifetime to its age. The age is |
|---|
| 891 | calculated as described in <a href="#age.calculations" title="Age Calculations">Section 2.2.3</a>; this section describes how to calculate the freshness lifetime, and to determine if a response has expired. In the discussion |
|---|
| 892 | below, the values can be represented in any form appropriate for arithmetic operations. |
|---|
| 893 | </p> |
|---|
| 894 | <p id="rfc.section.2.2.4.p.2">We use the term "expires_value" to denote the value of the Expires header. We use the term "max_age_value" to denote an appropriate |
|---|
| 895 | value of the number of seconds carried by the "max-age" directive of the Cache-Control header in a response (see <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section 3.2.3</a>). |
|---|
| 896 | </p> |
|---|
| 897 | <p id="rfc.section.2.2.4.p.3">The max-age directive takes priority over Expires, so if max-age is present in a response, the calculation is simply:</p> |
|---|
| 898 | <div id="rfc.figure.u.5"></div><pre class="text"> freshness_lifetime = max_age_value |
|---|
| 899 | </pre><p id="rfc.section.2.2.4.p.5">Otherwise, if Expires is present in the response, the calculation is:</p> |
|---|
| 900 | <div id="rfc.figure.u.6"></div><pre class="text"> freshness_lifetime = expires_value - date_value |
|---|
| 901 | </pre><p id="rfc.section.2.2.4.p.7">Note that neither of these calculations is vulnerable to clock skew, since all of the information comes from the origin server.</p> |
|---|
| 902 | <p id="rfc.section.2.2.4.p.8">If none of Expires, Cache-Control: max-age, or Cache-Control: s-maxage (see <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section 3.2.3</a>) appears in the response, and the response does not include other restrictions on caching, the cache <em class="bcp14">MAY</em> compute a freshness lifetime using a heuristic. The cache <em class="bcp14">MUST</em> attach Warning 113 to any response whose age is more than 24 hours if such warning has not already been added. |
|---|
| 903 | </p> |
|---|
| 904 | <p id="rfc.section.2.2.4.p.9">Also, if the response does have a Last-Modified time, the heuristic expiration value <em class="bcp14">SHOULD</em> be no more than some fraction of the interval since that time. A typical setting of this fraction might be 10%. |
|---|
| 905 | </p> |
|---|
| 906 | <p id="rfc.section.2.2.4.p.10">The calculation to determine if a response has expired is quite simple:</p> |
|---|
| 907 | <div id="rfc.figure.u.7"></div><pre class="text"> response_is_fresh = (freshness_lifetime > current_age) |
|---|
| 908 | </pre><h3 id="rfc.section.2.2.5"><a href="#rfc.section.2.2.5">2.2.5</a> <a id="disambiguating.expiration.values" href="#disambiguating.expiration.values">Disambiguating Expiration Values</a></h3> |
|---|
| 909 | <p id="rfc.section.2.2.5.p.1">Because expiration values are assigned optimistically, it is possible for two caches to contain fresh values for the same |
|---|
| 910 | resource that are different. |
|---|
| 911 | </p> |
|---|
| 912 | <p id="rfc.section.2.2.5.p.2">If a client performing a retrieval receives a non-first-hand response for a request that was already fresh in its own cache, |
|---|
| 913 | and the Date header in its existing cache entry is newer than the Date on the new response, then the client <em class="bcp14">MAY</em> ignore the response. If so, it <em class="bcp14">MAY</em> retry the request with a "Cache-Control: max-age=0" directive (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.5" title="Cache-Control">Section 3.2</a>), to force a check with the origin server. |
|---|
| 914 | </p> |
|---|
| 915 | <p id="rfc.section.2.2.5.p.3">If a cache has two fresh responses for the same representation with different validators, it <em class="bcp14">MUST</em> use the one with the more recent Date header. This situation might arise because the cache is pooling responses from other |
|---|
| 916 | caches, or because a client has asked for a reload or a revalidation of an apparently fresh cache entry. |
|---|
| 917 | </p> |
|---|
| 918 | <h3 id="rfc.section.2.2.6"><a href="#rfc.section.2.2.6">2.2.6</a> <a id="disambiguating.multiple.responses" href="#disambiguating.multiple.responses">Disambiguating Multiple Responses</a></h3> |
|---|
| 919 | <p id="rfc.section.2.2.6.p.1">Because a client might be receiving responses via multiple paths, so that some responses flow through one set of caches and |
|---|
| 920 | other responses flow through a different set of caches, a client might receive responses in an order different from that in |
|---|
| 921 | which the origin server sent them. We would like the client to use the most recently generated response, even if older responses |
|---|
| 922 | are still apparently fresh. |
|---|
| 923 | </p> |
|---|
| 924 | <p id="rfc.section.2.2.6.p.2">Neither the entity tag nor the expiration value can impose an ordering on responses, since it is possible that a later response |
|---|
| 925 | intentionally carries an earlier expiration time. The Date values are ordered to a granularity of one second. |
|---|
| 926 | </p> |
|---|
| 927 | <p id="rfc.section.2.2.6.p.3">When a client tries to revalidate a cache entry, and the response it receives contains a Date header that appears to be older |
|---|
| 928 | than the one for the existing entry, then the client <em class="bcp14">SHOULD</em> repeat the request unconditionally, and include |
|---|
| 929 | </p> |
|---|
| 930 | <div id="rfc.figure.u.8"></div><pre class="text"> Cache-Control: max-age=0 |
|---|
| 931 | </pre><p id="rfc.section.2.2.6.p.5">to force any intermediate caches to validate their copies directly with the origin server, or</p> |
|---|
| 932 | <div id="rfc.figure.u.9"></div><pre class="text"> Cache-Control: no-cache |
|---|
| 933 | </pre><p id="rfc.section.2.2.6.p.7">to force any intermediate caches to obtain a new copy from the origin server.</p> |
|---|
| 934 | <p id="rfc.section.2.2.6.p.8">If the Date values are equal, then the client <em class="bcp14">MAY</em> use either response (or <em class="bcp14">MAY</em>, if it is being extremely prudent, request a new response). Servers <em class="bcp14">MUST NOT</em> depend on clients being able to choose deterministically between responses generated during the same second, if their expiration |
|---|
| 935 | times overlap. |
|---|
| 936 | </p> |
|---|
| 937 | <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a> <a id="validation.model" href="#validation.model">Validation Model</a></h2> |
|---|
| 938 | <p id="rfc.section.2.3.p.1">When a cache has a stale entry that it would like to use as a response to a client's request, it first has to check with the |
|---|
| 939 | origin server (or possibly an intermediate cache with a fresh response) to see if its cached entry is still usable. We call |
|---|
| 940 | this "validating" the cache entry. Since we do not want to have to pay the overhead of retransmitting the full response if |
|---|
| 941 | the cached entry is good, and we do not want to pay the overhead of an extra round trip if the cached entry is invalid, the |
|---|
| 942 | HTTP/1.1 protocol supports the use of conditional methods. |
|---|
| 943 | </p> |
|---|
| 944 | <p id="rfc.section.2.3.p.2">The key protocol features for supporting conditional methods are those concerned with "cache validators." When an origin server |
|---|
| 945 | generates a full response, it attaches some sort of validator to it, which is kept with the cache entry. When a client (user |
|---|
| 946 | agent or proxy cache) makes a conditional request for a resource for which it has a cache entry, it includes the associated |
|---|
| 947 | validator in the request. |
|---|
| 948 | </p> |
|---|
| 949 | <p id="rfc.section.2.3.p.3">The server then checks that validator against the current validator for the entity, and, if they match (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak and Strong Validators">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>), it responds with a special status code (usually, 304 (Not Modified)) and no entity-body. Otherwise, it returns a full response |
|---|
| 950 | (including entity-body). Thus, we avoid transmitting the full response if the validator matches, and we avoid an extra round |
|---|
| 951 | trip if it does not match. |
|---|
| 952 | </p> |
|---|
| 953 | <p id="rfc.section.2.3.p.4">In HTTP/1.1, a conditional request looks exactly the same as a normal request for the same resource, except that it carries |
|---|
| 954 | a special header (which includes the validator) that implicitly turns the method (usually, GET) into a conditional. |
|---|
| 955 | </p> |
|---|
| 956 | <p id="rfc.section.2.3.p.5">The protocol includes both positive and negative senses of cache-validating conditions. That is, it is possible to request |
|---|
| 957 | either that a method be performed if and only if a validator matches or if and only if no validators match. |
|---|
| 958 | </p> |
|---|
| 959 | <dl class="empty"> |
|---|
| 960 | <dd> <b>Note:</b> a response that lacks a validator may still be cached, and served from cache until it expires, unless this is explicitly prohibited |
|---|
| 961 | by a cache-control directive. However, a cache cannot do a conditional retrieval if it does not have a validator for the entity, |
|---|
| 962 | which means it will not be refreshable after it expires. |
|---|
| 963 | </dd> |
|---|
| 964 | </dl> |
|---|
| 965 | <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a> <a id="last-modified.dates" href="#last-modified.dates">Last-Modified Dates</a></h3> |
|---|
| 966 | <p id="rfc.section.2.3.1.p.1">The Last-Modified entity-header field value is often used as a cache validator. In simple terms, a cache entry is considered |
|---|
| 967 | to be valid if the entity has not been modified since the Last-Modified value. |
|---|
| 968 | </p> |
|---|
| 969 | <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a> <a id="entity.tag.cache.validators" href="#entity.tag.cache.validators">Entity Tag Cache Validators</a></h3> |
|---|
| 970 | <p id="rfc.section.2.3.2.p.1">The ETag response-header field value, an entity tag, provides for an "opaque" cache validator. This might allow more reliable |
|---|
| 971 | validation in situations where it is inconvenient to store modification dates, where the one-second resolution of HTTP date |
|---|
| 972 | values is not sufficient, or where the origin server wishes to avoid certain paradoxes that might arise from the use of modification |
|---|
| 973 | dates. |
|---|
| 974 | </p> |
|---|
| 975 | <p id="rfc.section.2.3.2.p.2">Entity Tags are described in <a href="p4-conditional.html#entity.tags" title="Entity Tags">Section 2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. The headers used with entity tags are described in <a href="p4-conditional.html#header.fields" title="Header Field Definitions">Section 6</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. |
|---|
| 976 | </p> |
|---|
| 977 | <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a> <a id="non-validating.conditionals" href="#non-validating.conditionals">Non-validating Conditionals</a></h3> |
|---|
| 978 | <p id="rfc.section.2.3.3.p.1">The principle behind entity tags is that only the service author knows the semantics of a resource well enough to select an |
|---|
| 979 | appropriate cache validation mechanism, and the specification of any validator comparison function more complex than byte-equality |
|---|
| 980 | would open up a can of worms. Thus, comparisons of any other headers (except Last-Modified, for compatibility with HTTP/1.0) |
|---|
| 981 | are never used for purposes of validating a cache entry. |
|---|
| 982 | </p> |
|---|
| 983 | <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a> <a id="response.cacheability" href="#response.cacheability">Response Cacheability</a></h2> |
|---|
| 984 | <p id="rfc.section.2.4.p.1">Unless specifically constrained by a cache-control (<a href="#header.cache-control" id="rfc.xref.header.cache-control.6" title="Cache-Control">Section 3.2</a>) directive, a caching system <em class="bcp14">MAY</em> always store a successful response (see <a href="#errors.or.incomplete.response.cache.behavior" title="Errors or Incomplete Response Cache Behavior">Section 2.8</a>) as a cache entry, <em class="bcp14">MAY</em> return it without validation if it is fresh, and <em class="bcp14">MAY</em> return it after successful validation. If there is neither a cache validator nor an explicit expiration time associated with |
|---|
| 985 | a response, we do not expect it to be cached, but certain caches <em class="bcp14">MAY</em> violate this expectation (for example, when little or no network connectivity is available). A client can usually detect that |
|---|
| 986 | such a response was taken from a cache by comparing the Date header to the current time. |
|---|
| 987 | </p> |
|---|
| 988 | <dl class="empty"> |
|---|
| 989 | <dd> <b>Note:</b> some HTTP/1.0 caches are known to violate this expectation without providing any Warning. |
|---|
| 990 | </dd> |
|---|
| 991 | </dl> |
|---|
| 992 | <p id="rfc.section.2.4.p.2">However, in some cases it might be inappropriate for a cache to retain an entity, or to return it in response to a subsequent |
|---|
| 993 | request. This might be because absolute semantic transparency is deemed necessary by the service author, or because of security |
|---|
| 994 | or privacy considerations. Certain cache-control directives are therefore provided so that the server can indicate that certain |
|---|
| 995 | resource entities, or portions thereof, are not to be cached regardless of other considerations. |
|---|
| 996 | </p> |
|---|
| 997 | <p id="rfc.section.2.4.p.3">Note that <a href="p7-auth.html#header.authorization" title="Authorization">Section 3.1</a> of <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a> normally prevents a shared cache from saving and returning a response to a previous request if that request included an Authorization |
|---|
| 998 | header. |
|---|
| 999 | </p> |
|---|
| 1000 | <p id="rfc.section.2.4.p.4">A response received with a status code of 200, 203, 206, 300, 301 or 410 <em class="bcp14">MAY</em> be stored by a cache and used in reply to a subsequent request, subject to the expiration mechanism, unless a cache-control |
|---|
| 1001 | directive prohibits caching. However, a cache that does not support the Range and Content-Range headers <em class="bcp14">MUST NOT</em> cache 206 (Partial Content) responses. |
|---|
| 1002 | </p> |
|---|
| 1003 | <p id="rfc.section.2.4.p.5">A response received with any other status code (e.g. status codes 302 and 307) <em class="bcp14">MUST NOT</em> be returned in a reply to a subsequent request unless there are cache-control directives or another header(s) that explicitly |
|---|
| 1004 | allow it. For example, these include the following: an Expires header (<a href="#header.expires" id="rfc.xref.header.expires.1" title="Expires">Section 3.3</a>); a "max-age", "s-maxage", "must-revalidate", "proxy-revalidate", "public" or "private" cache-control directive (<a href="#header.cache-control" id="rfc.xref.header.cache-control.7" title="Cache-Control">Section 3.2</a>). |
|---|
| 1005 | </p> |
|---|
| 1006 | <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a> <a id="constructing.responses.from.caches" href="#constructing.responses.from.caches">Constructing Responses From Caches</a></h2> |
|---|
| 1007 | <p id="rfc.section.2.5.p.1">The purpose of an HTTP cache is to store information received in response to requests for use in responding to future requests. |
|---|
| 1008 | In many cases, a cache simply returns the appropriate parts of a response to the requester. However, if the cache holds a |
|---|
| 1009 | cache entry based on a previous response, it might have to combine parts of a new response with what is held in the cache |
|---|
| 1010 | entry. |
|---|
| 1011 | </p> |
|---|
| 1012 | <h3 id="rfc.section.2.5.1"><a href="#rfc.section.2.5.1">2.5.1</a> <a id="end-to-end.and.hop-by-hop.headers" href="#end-to-end.and.hop-by-hop.headers">End-to-end and Hop-by-hop Headers</a></h3> |
|---|
| 1013 | <p id="rfc.section.2.5.1.p.1">For the purpose of defining the behavior of caches and non-caching proxies, we divide HTTP headers into two categories: </p> |
|---|
| 1014 | <ul> |
|---|
| 1015 | <li>End-to-end headers, which are transmitted to the ultimate recipient of a request or response. End-to-end headers in responses <em class="bcp14">MUST</em> be stored as part of a cache entry and <em class="bcp14">MUST</em> be transmitted in any response formed from a cache entry. |
|---|
| 1016 | </li> |
|---|
| 1017 | <li>Hop-by-hop headers, which are meaningful only for a single transport-level connection, and are not stored by caches or forwarded |
|---|
| 1018 | by proxies. |
|---|
| 1019 | </li> |
|---|
| 1020 | </ul> |
|---|
| 1021 | <p id="rfc.section.2.5.1.p.2">The following HTTP/1.1 headers are hop-by-hop headers: </p> |
|---|
| 1022 | <ul> |
|---|
| 1023 | <li>Connection</li> |
|---|
| 1024 | <li>Keep-Alive</li> |
|---|
| 1025 | <li>Proxy-Authenticate</li> |
|---|
| 1026 | <li>Proxy-Authorization</li> |
|---|
| 1027 | <li>TE</li> |
|---|
| 1028 | <li>Trailer</li> |
|---|
| 1029 | <li>Transfer-Encoding</li> |
|---|
| 1030 | <li>Upgrade</li> |
|---|
| 1031 | </ul> |
|---|
| 1032 | <p id="rfc.section.2.5.1.p.3">All other headers defined by HTTP/1.1 are end-to-end headers.</p> |
|---|
| 1033 | <p id="rfc.section.2.5.1.p.4">Other hop-by-hop headers <em class="bcp14">MUST</em> be listed in a Connection header (<a href="p1-messaging.html#header.connection" title="Connection">Section 8.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>). |
|---|
| 1034 | </p> |
|---|
| 1035 | <h3 id="rfc.section.2.5.2"><a href="#rfc.section.2.5.2">2.5.2</a> <a id="non-modifiable.headers" href="#non-modifiable.headers">Non-modifiable Headers</a></h3> |
|---|
| 1036 | <p id="rfc.section.2.5.2.p.1">Some features of the HTTP/1.1 protocol, such as Digest Authentication, depend on the value of certain end-to-end headers. |
|---|
| 1037 | A transparent proxy <em class="bcp14">SHOULD NOT</em> modify an end-to-end header unless the definition of that header requires or specifically allows that. |
|---|
| 1038 | </p> |
|---|
| 1039 | <p id="rfc.section.2.5.2.p.2">A transparent proxy <em class="bcp14">MUST NOT</em> modify any of the following fields in a request or response, and it <em class="bcp14">MUST NOT</em> add any of these fields if not already present: |
|---|
| 1040 | </p> |
|---|
| 1041 | <ul> |
|---|
| 1042 | <li>Content-Location</li> |
|---|
| 1043 | <li>Content-MD5</li> |
|---|
| 1044 | <li>ETag</li> |
|---|
| 1045 | <li>Last-Modified</li> |
|---|
| 1046 | </ul> |
|---|
| 1047 | <p id="rfc.section.2.5.2.p.3">A transparent proxy <em class="bcp14">MUST NOT</em> modify any of the following fields in a response: |
|---|
| 1048 | </p> |
|---|
| 1049 | <ul> |
|---|
| 1050 | <li>Expires</li> |
|---|
| 1051 | </ul> |
|---|
| 1052 | <p id="rfc.section.2.5.2.p.4">but it <em class="bcp14">MAY</em> add any of these fields if not already present. If an Expires header is added, it <em class="bcp14">MUST</em> be given a field-value identical to that of the Date header in that response. |
|---|
| 1053 | </p> |
|---|
| 1054 | <p id="rfc.section.2.5.2.p.5">A proxy <em class="bcp14">MUST NOT</em> modify or add any of the following fields in a message that contains the no-transform cache-control directive, or in any request: |
|---|
| 1055 | </p> |
|---|
| 1056 | <ul> |
|---|
| 1057 | <li>Content-Encoding</li> |
|---|
| 1058 | <li>Content-Range</li> |
|---|
| 1059 | <li>Content-Type</li> |
|---|
| 1060 | </ul> |
|---|
| 1061 | <p id="rfc.section.2.5.2.p.6">A non-transparent proxy <em class="bcp14">MAY</em> modify or add these fields to a message that does not include no-transform, but if it does so, it <em class="bcp14">MUST</em> add a Warning 214 (Transformation applied) if one does not already appear in the message (see <a href="#header.warning" id="rfc.xref.header.warning.4" title="Warning">Section 3.6</a>). |
|---|
| 1062 | </p> |
|---|
| 1063 | <dl class="empty"> |
|---|
| 1064 | <dd>Warning: unnecessary modification of end-to-end headers might cause authentication failures if stronger authentication mechanisms |
|---|
| 1065 | are introduced in later versions of HTTP. Such authentication mechanisms <em class="bcp14">MAY</em> rely on the values of header fields not listed here. |
|---|
| 1066 | </dd> |
|---|
| 1067 | </dl> |
|---|
| 1068 | <p id="rfc.section.2.5.2.p.7">The Content-Length field of a request or response is added or deleted according to the rules in <a href="p1-messaging.html#message.length" title="Message Length">Section 4.4</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>. A transparent proxy <em class="bcp14">MUST</em> preserve the entity-length (<a href="p3-payload.html#entity.length" title="Entity Length">Section 3.2.2</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>) of the entity-body, although it <em class="bcp14">MAY</em> change the transfer-length (<a href="p1-messaging.html#message.length" title="Message Length">Section 4.4</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>). |
|---|
| 1069 | </p> |
|---|
| 1070 | <h3 id="rfc.section.2.5.3"><a href="#rfc.section.2.5.3">2.5.3</a> <a id="combining.headers" href="#combining.headers">Combining Headers</a></h3> |
|---|
| 1071 | <p id="rfc.section.2.5.3.p.1">When a cache makes a validating request to a server, and the server provides a 304 (Not Modified) response or a 206 (Partial |
|---|
| 1072 | Content) response, the cache then constructs a response to send to the requesting client. |
|---|
| 1073 | </p> |
|---|
| 1074 | <p id="rfc.section.2.5.3.p.2">If the status code is 304 (Not Modified), the cache uses the entity-body stored in the cache entry as the entity-body of this |
|---|
| 1075 | outgoing response. If the status code is 206 (Partial Content) and the ETag or Last-Modified headers match exactly, the cache <em class="bcp14">MAY</em> combine the contents stored in the cache entry with the new contents received in the response and use the result as the entity-body |
|---|
| 1076 | of this outgoing response, (see <a href="p5-range.html#combining.byte.ranges" title="Combining Byte Ranges">Section 4</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>). |
|---|
| 1077 | </p> |
|---|
| 1078 | <p id="rfc.section.2.5.3.p.3">The end-to-end headers stored in the cache entry are used for the constructed response, except that </p> |
|---|
| 1079 | <ul> |
|---|
| 1080 | <li>any stored Warning headers with warn-code 1xx (see <a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section 3.6</a>) <em class="bcp14">MUST</em> be deleted from the cache entry and the forwarded response. |
|---|
| 1081 | </li> |
|---|
| 1082 | <li>any stored Warning headers with warn-code 2xx <em class="bcp14">MUST</em> be retained in the cache entry and the forwarded response. |
|---|
| 1083 | </li> |
|---|
| 1084 | <li>any end-to-end headers provided in the 304 or 206 response <em class="bcp14">MUST</em> replace the corresponding headers from the cache entry. |
|---|
| 1085 | </li> |
|---|
| 1086 | </ul> |
|---|
| 1087 | <p id="rfc.section.2.5.3.p.4">Unless the cache decides to remove the cache entry, it <em class="bcp14">MUST</em> also replace the end-to-end headers stored with the cache entry with corresponding headers received in the incoming response, |
|---|
| 1088 | except for Warning headers as described immediately above. If a header field-name in the incoming response matches more than |
|---|
| 1089 | one header in the cache entry, all such old headers <em class="bcp14">MUST</em> be replaced. |
|---|
| 1090 | </p> |
|---|
| 1091 | <p id="rfc.section.2.5.3.p.5">In other words, the set of end-to-end headers received in the incoming response overrides all corresponding end-to-end headers |
|---|
| 1092 | stored with the cache entry (except for stored Warning headers with warn-code 1xx, which are deleted even if not overridden). |
|---|
| 1093 | </p> |
|---|
| 1094 | <dl class="empty"> |
|---|
| 1095 | <dd> <b>Note:</b> this rule allows an origin server to use a 304 (Not Modified) or a 206 (Partial Content) response to update any header associated |
|---|
| 1096 | with a previous response for the same entity or sub-ranges thereof, although it might not always be meaningful or correct |
|---|
| 1097 | to do so. This rule does not allow an origin server to use a 304 (Not Modified) or a 206 (Partial Content) response to entirely |
|---|
| 1098 | delete a header that it had provided with a previous response. |
|---|
| 1099 | </dd> |
|---|
| 1100 | </dl> |
|---|
| 1101 | <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a> <a id="caching.negotiated.responses" href="#caching.negotiated.responses">Caching Negotiated Responses</a></h2> |
|---|
| 1102 | <p id="rfc.section.2.6.p.1">Use of server-driven content negotiation (<a href="p3-payload.html#server-driven.negotiation" title="Server-driven Negotiation">Section 4.1</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>), as indicated by the presence of a Vary header field in a response, alters the conditions and procedure by which a cache |
|---|
| 1103 | can use the response for subsequent requests. See <a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section 3.5</a> for use of the Vary header field by servers. |
|---|
| 1104 | </p> |
|---|
| 1105 | <p id="rfc.section.2.6.p.2">A server <em class="bcp14">SHOULD</em> use the Vary header field to inform a cache of what request-header fields were used to select among multiple representations |
|---|
| 1106 | of a cacheable response subject to server-driven negotiation. The set of header fields named by the Vary field value is known |
|---|
| 1107 | as the "selecting" request-headers. |
|---|
| 1108 | </p> |
|---|
| 1109 | <p id="rfc.section.2.6.p.3">When the cache receives a subsequent request whose Request-URI specifies one or more cache entries including a Vary header |
|---|
| 1110 | field, the cache <em class="bcp14">MUST NOT</em> use such a cache entry to construct a response to the new request unless all of the selecting request-headers present in the |
|---|
| 1111 | new request match the corresponding stored request-headers in the original request. |
|---|
| 1112 | </p> |
|---|
| 1113 | <p id="rfc.section.2.6.p.4">The selecting request-headers from two requests are defined to match if and only if the selecting request-headers in the first |
|---|
| 1114 | request can be transformed to the selecting request-headers in the second request by adding or removing linear white space |
|---|
| 1115 | (LWS) at places where this is allowed by the corresponding BNF, and/or combining multiple message-header fields with the same |
|---|
| 1116 | field name following the rules about message headers in <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</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>. |
|---|
| 1117 | </p> |
|---|
| 1118 | <p id="rfc.section.2.6.p.5">A Vary header field-value of "*" always fails to match and subsequent requests on that resource can only be properly interpreted |
|---|
| 1119 | by the origin server. |
|---|
| 1120 | </p> |
|---|
| 1121 | <p id="rfc.section.2.6.p.6">If the selecting request header fields for the cached entry do not match the selecting request header fields of the new request, |
|---|
| 1122 | then the cache <em class="bcp14">MUST NOT</em> use a cached entry to satisfy the request unless it first relays the new request to the origin server in a conditional request |
|---|
| 1123 | and the server responds with 304 (Not Modified), including an entity tag or Content-Location that indicates the entity to |
|---|
| 1124 | be used. |
|---|
| 1125 | </p> |
|---|
| 1126 | <p id="rfc.section.2.6.p.7">If an entity tag was assigned to a cached representation, the forwarded request <em class="bcp14">SHOULD</em> be conditional and include the entity tags in an If-None-Match header field from all its cache entries for the resource. This |
|---|
| 1127 | conveys to the server the set of entities currently held by the cache, so that if any one of these entities matches the requested |
|---|
| 1128 | entity, the server can use the ETag header field in its 304 (Not Modified) response to tell the cache which entry is appropriate. |
|---|
| 1129 | If the entity-tag of the new response matches that of an existing entry, the new response <em class="bcp14">SHOULD</em> be used to update the header fields of the existing entry, and the result <em class="bcp14">MUST</em> be returned to the client. |
|---|
| 1130 | </p> |
|---|
| 1131 | <p id="rfc.section.2.6.p.8">If any of the existing cache entries contains only partial content for the associated entity, its entity-tag <em class="bcp14">SHOULD NOT</em> be included in the If-None-Match header field unless the request is for a range that would be fully satisfied by that entry. |
|---|
| 1132 | </p> |
|---|
| 1133 | <p id="rfc.section.2.6.p.9">If a cache receives a successful response whose Content-Location field matches that of an existing cache entry for the same |
|---|
| 1134 | Request-URI, whose entity-tag differs from that of the existing entry, and whose Date is more recent than that of the existing |
|---|
| 1135 | entry, the existing entry <em class="bcp14">SHOULD NOT</em> be returned in response to future requests and <em class="bcp14">SHOULD</em> be deleted from the cache. |
|---|
| 1136 | </p> |
|---|
| 1137 | <h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a> <a id="shared.and.non-shared.caches" href="#shared.and.non-shared.caches">Shared and Non-Shared Caches</a></h2> |
|---|
| 1138 | <p id="rfc.section.2.7.p.1">For reasons of security and privacy, it is necessary to make a distinction between "shared" and "non-shared" caches. A non-shared |
|---|
| 1139 | cache is one that is accessible only to a single user. Accessibility in this case <em class="bcp14">SHOULD</em> be enforced by appropriate security mechanisms. All other caches are considered to be "shared." Other sections of this specification |
|---|
| 1140 | place certain constraints on the operation of shared caches in order to prevent loss of privacy or failure of access controls. |
|---|
| 1141 | </p> |
|---|
| 1142 | <h2 id="rfc.section.2.8"><a href="#rfc.section.2.8">2.8</a> <a id="errors.or.incomplete.response.cache.behavior" href="#errors.or.incomplete.response.cache.behavior">Errors or Incomplete Response Cache Behavior</a></h2> |
|---|
| 1143 | <p id="rfc.section.2.8.p.1">A cache that receives an incomplete response (for example, with fewer bytes of data than specified in a Content-Length header) <em class="bcp14">MAY</em> store the response. However, the cache <em class="bcp14">MUST</em> treat this as a partial response. Partial responses <em class="bcp14">MAY</em> be combined as described in <a href="p5-range.html#combining.byte.ranges" title="Combining Byte Ranges">Section 4</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>; the result might be a full response or might still be partial. A cache <em class="bcp14">MUST NOT</em> return a partial response to a client without explicitly marking it as such, using the 206 (Partial Content) status code. |
|---|
| 1144 | A cache <em class="bcp14">MUST NOT</em> return a partial response using a status code of 200 (OK). |
|---|
| 1145 | </p> |
|---|
| 1146 | <p id="rfc.section.2.8.p.2">If a cache receives a 5xx response while attempting to revalidate an entry, it <em class="bcp14">MAY</em> either forward this response to the requesting client, or act as if the server failed to respond. In the latter case, it <em class="bcp14">MAY</em> return a previously received response unless the cached entry includes the "must-revalidate" cache-control directive (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.8" title="Cache-Control">Section 3.2</a>). |
|---|
| 1147 | </p> |
|---|
| 1148 | <h2 id="rfc.section.2.9"><a href="#rfc.section.2.9">2.9</a> <a id="side.effects.of.get.and.head" href="#side.effects.of.get.and.head">Side Effects of GET and HEAD</a></h2> |
|---|
| 1149 | <p id="rfc.section.2.9.p.1">Unless the origin server explicitly prohibits the caching of their responses, the application of GET and HEAD methods to any |
|---|
| 1150 | resources <em class="bcp14">SHOULD NOT</em> have side effects that would lead to erroneous behavior if these responses are taken from a cache. They <em class="bcp14">MAY</em> still have side effects, but a cache is not required to consider such side effects in its caching decisions. Caches are always |
|---|
| 1151 | expected to observe an origin server's explicit restrictions on caching. |
|---|
| 1152 | </p> |
|---|
| 1153 | <p id="rfc.section.2.9.p.2">We note one exception to this rule: since some applications have traditionally used GETs and HEADs with query URLs (those |
|---|
| 1154 | containing a "?" in the rel_path part) to perform operations with significant side effects, caches <em class="bcp14">MUST NOT</em> treat responses to such URIs as fresh unless the server provides an explicit expiration time. This specifically means that |
|---|
| 1155 | responses from HTTP/1.0 servers for such URIs <em class="bcp14">SHOULD NOT</em> be taken from a cache. See <a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 8.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a> for related information. |
|---|
| 1156 | </p> |
|---|
| 1157 | <h2 id="rfc.section.2.10"><a href="#rfc.section.2.10">2.10</a> <a id="invalidation.after.updates.or.deletions" href="#invalidation.after.updates.or.deletions">Invalidation After Updates or Deletions</a></h2> |
|---|
| 1158 | <p id="rfc.section.2.10.p.1">The effect of certain methods performed on a resource at the origin server might cause one or more existing cache entries |
|---|
| 1159 | to become non-transparently invalid. That is, although they might continue to be "fresh," they do not accurately reflect what |
|---|
| 1160 | the origin server would return for a new request on that resource. |
|---|
| 1161 | </p> |
|---|
| 1162 | <p id="rfc.section.2.10.p.2">There is no way for the HTTP protocol to guarantee that all such cache entries are marked invalid. For example, the request |
|---|
| 1163 | that caused the change at the origin server might not have gone through the proxy where a cache entry is stored. However, |
|---|
| 1164 | several rules help reduce the likelihood of erroneous behavior. |
|---|
| 1165 | </p> |
|---|
| 1166 | <p id="rfc.section.2.10.p.3">In this section, the phrase "invalidate an entity" means that the cache will either remove all instances of that entity from |
|---|
| 1167 | its storage, or will mark these as "invalid" and in need of a mandatory revalidation before they can be returned in response |
|---|
| 1168 | to a subsequent request. |
|---|
| 1169 | </p> |
|---|
| 1170 | <p id="rfc.section.2.10.p.4">Some HTTP methods <em class="bcp14">MUST</em> cause a cache to invalidate an entity. This is either the entity referred to by the Request-URI, or by the Location or Content-Location |
|---|
| 1171 | headers (if present). These methods are: |
|---|
| 1172 | </p> |
|---|
| 1173 | <ul> |
|---|
| 1174 | <li>PUT</li> |
|---|
| 1175 | <li>DELETE</li> |
|---|
| 1176 | <li>POST</li> |
|---|
| 1177 | </ul> |
|---|
| 1178 | <p id="rfc.section.2.10.p.5">An invalidation based on the URI in a Location or Content-Location header <em class="bcp14">MUST NOT</em> be performed if the host part of that URI differs from the host part in the Request-URI. This helps prevent denial of service |
|---|
| 1179 | attacks. |
|---|
| 1180 | </p> |
|---|
| 1181 | <p id="rfc.section.2.10.p.6">A cache that passes through requests for methods it does not understand <em class="bcp14">SHOULD</em> invalidate any entities referred to by the Request-URI. |
|---|
| 1182 | </p> |
|---|
| 1183 | <h2 id="rfc.section.2.11"><a href="#rfc.section.2.11">2.11</a> <a id="write-through.mandatory" href="#write-through.mandatory">Write-Through Mandatory</a></h2> |
|---|
| 1184 | <p id="rfc.section.2.11.p.1">All methods that might be expected to cause modifications to the origin server's resources <em class="bcp14">MUST</em> be written through to the origin server. This currently includes all methods except for GET and HEAD. A cache <em class="bcp14">MUST NOT</em> reply to such a request from a client before having transmitted the request to the inbound server, and having received a corresponding |
|---|
| 1185 | response from the inbound server. This does not prevent a proxy cache from sending a 100 (Continue) response before the inbound |
|---|
| 1186 | server has sent its final reply. |
|---|
| 1187 | </p> |
|---|
| 1188 | <p id="rfc.section.2.11.p.2">The alternative (known as "write-back" or "copy-back" caching) is not allowed in HTTP/1.1, due to the difficulty of providing |
|---|
| 1189 | consistent updates and the problems arising from server, cache, or network failure prior to write-back. |
|---|
| 1190 | </p> |
|---|
| 1191 | <h2 id="rfc.section.2.12"><a href="#rfc.section.2.12">2.12</a> <a id="cache.replacement" href="#cache.replacement">Cache Replacement</a></h2> |
|---|
| 1192 | <p id="rfc.section.2.12.p.1">If a new cacheable (see Sections <a href="#what.may.be.stored.by.caches" title="What May be Stored by Caches">3.2.2</a>, <a href="#disambiguating.expiration.values" title="Disambiguating Expiration Values">2.2.5</a>, <a href="#disambiguating.multiple.responses" title="Disambiguating Multiple Responses">2.2.6</a> and <a href="#errors.or.incomplete.response.cache.behavior" title="Errors or Incomplete Response Cache Behavior">2.8</a>) response is received from a resource while any existing responses for the same resource are cached, the cache <em class="bcp14">SHOULD</em> use the new response to reply to the current request. It <em class="bcp14">MAY</em> insert it into cache storage and <em class="bcp14">MAY</em>, if it meets all other requirements, use it to respond to any future requests that would previously have caused the old response |
|---|
| 1193 | to be returned. If it inserts the new response into cache storage the rules in <a href="#combining.headers" title="Combining Headers">Section 2.5.3</a> apply. |
|---|
| 1194 | </p> |
|---|
| 1195 | <dl class="empty"> |
|---|
| 1196 | <dd> <b>Note:</b> a new response that has an older Date header value than existing cached responses is not cacheable. |
|---|
| 1197 | </dd> |
|---|
| 1198 | </dl> |
|---|
| 1199 | <h2 id="rfc.section.2.13"><a href="#rfc.section.2.13">2.13</a> <a id="history.lists" href="#history.lists">History Lists</a></h2> |
|---|
| 1200 | <p id="rfc.section.2.13.p.1">User agents often have history mechanisms, such as "Back" buttons and history lists, which can be used to redisplay an entity |
|---|
| 1201 | retrieved earlier in a session. |
|---|
| 1202 | </p> |
|---|
| 1203 | <p id="rfc.section.2.13.p.2">History mechanisms and caches are different. In particular history mechanisms <em class="bcp14">SHOULD NOT</em> try to show a semantically transparent view of the current state of a resource. Rather, a history mechanism is meant to show |
|---|
| 1204 | exactly what the user saw at the time when the resource was retrieved. |
|---|
| 1205 | </p> |
|---|
| 1206 | <p id="rfc.section.2.13.p.3">By default, an expiration time does not apply to history mechanisms. If the entity is still in storage, a history mechanism <em class="bcp14">SHOULD</em> display it even if the entity has expired, unless the user has specifically configured the agent to refresh expired history |
|---|
| 1207 | documents. |
|---|
| 1208 | </p> |
|---|
| 1209 | <p id="rfc.section.2.13.p.4">This is not to be construed to prohibit the history mechanism from telling the user that a view might be stale. </p> |
|---|
| 1210 | <dl class="empty"> |
|---|
| 1211 | <dd> <b>Note:</b> if history list mechanisms unnecessarily prevent users from viewing stale resources, this will tend to force service authors |
|---|
| 1212 | to avoid using HTTP expiration controls and cache controls when they would otherwise like to. Service authors may consider |
|---|
| 1213 | it important that users not be presented with error messages or warning messages when they use navigation controls (such as |
|---|
| 1214 | BACK) to view previously fetched resources. Even though sometimes such resources ought not to cached, or ought to expire quickly, |
|---|
| 1215 | user interface considerations may force service authors to resort to other means of preventing caching (e.g. "once-only" URLs) |
|---|
| 1216 | in order not to suffer the effects of improperly functioning history mechanisms. |
|---|
| 1217 | </dd> |
|---|
| 1218 | </dl> |
|---|
| 1219 | <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1> |
|---|
| 1220 | <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to caching.</p> |
|---|
| 1221 | <p id="rfc.section.3.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who |
|---|
| 1222 | receives the entity. |
|---|
| 1223 | </p> |
|---|
| 1224 | <div id="rfc.iref.a.2"></div> |
|---|
| 1225 | <div id="rfc.iref.h.2"></div> |
|---|
| 1226 | <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a> <a id="header.age" href="#header.age">Age</a></h2> |
|---|
| 1227 | <p id="rfc.section.3.1.p.1">The Age response-header field conveys the sender's estimate of the amount of time since the response (or its revalidation) |
|---|
| 1228 | was generated at the origin server. A cached response is "fresh" if its age does not exceed its freshness lifetime. Age values |
|---|
| 1229 | are calculated as specified in <a href="#age.calculations" title="Age Calculations">Section 2.2.3</a>. |
|---|
| 1230 | </p> |
|---|
| 1231 | <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span> Age = "Age" ":" age-value |
|---|
| 1232 | age-value = delta-seconds |
|---|
| 1233 | </pre><p id="rfc.section.3.1.p.3">Age values are non-negative decimal integers, representing time in seconds.</p> |
|---|
| 1234 | <p id="rfc.section.3.1.p.4">If a cache receives a value larger than the largest positive integer it can represent, or if any of its age calculations overflows, |
|---|
| 1235 | it <em class="bcp14">MUST</em> transmit an Age header with a value of 2147483648 (2^31). An HTTP/1.1 server that includes a cache <em class="bcp14">MUST</em> include an Age header field in every response generated from its own cache. Caches <em class="bcp14">SHOULD</em> use an arithmetic type of at least 31 bits of range. |
|---|
| 1236 | </p> |
|---|
| 1237 | <div id="rfc.iref.c.3"></div> |
|---|
| 1238 | <div id="rfc.iref.h.3"></div> |
|---|
| 1239 | <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="header.cache-control" href="#header.cache-control">Cache-Control</a></h2> |
|---|
| 1240 | <p id="rfc.section.3.2.p.1">The Cache-Control general-header field is used to specify directives that <em class="bcp14">MUST</em> be obeyed by all caching mechanisms along the request/response chain. The directives specify behavior intended to prevent |
|---|
| 1241 | caches from adversely interfering with the request or response. These directives typically override the default caching algorithms. |
|---|
| 1242 | Cache directives are unidirectional in that the presence of a directive in a request does not imply that the same directive |
|---|
| 1243 | is to be given in the response. |
|---|
| 1244 | </p> |
|---|
| 1245 | <dl class="empty"> |
|---|
| 1246 | <dd>Note that HTTP/1.0 caches might not implement Cache-Control and might only implement Pragma: no-cache (see <a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section 3.4</a>). |
|---|
| 1247 | </dd> |
|---|
| 1248 | </dl> |
|---|
| 1249 | <p id="rfc.section.3.2.p.2">Cache directives <em class="bcp14">MUST</em> be passed through by a proxy or gateway application, regardless of their significance to that application, since the directives |
|---|
| 1250 | might be applicable to all recipients along the request/response chain. It is not possible to specify a cache-directive for |
|---|
| 1251 | a specific cache. |
|---|
| 1252 | </p> |
|---|
| 1253 | <div id="rfc.figure.u.11"></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><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span> Cache-Control = "Cache-Control" ":" 1#cache-directive |
|---|
| 1254 | |
|---|
| 1255 | cache-directive = cache-request-directive |
|---|
| 1256 | | cache-response-directive |
|---|
| 1257 | |
|---|
| 1258 | cache-request-directive = |
|---|
| 1259 | "no-cache" ; <a href="#what.is.cacheable" title="What is Cacheable">Section 3.2.1</a> |
|---|
| 1260 | | "no-store" ; <a href="#what.may.be.stored.by.caches" title="What May be Stored by Caches">Section 3.2.2</a> |
|---|
| 1261 | | "max-age" "=" delta-seconds ; <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section 3.2.3</a>, <a href="#cache.revalidation.and.reload.controls" title="Cache Revalidation and Reload Controls">3.2.4</a> |
|---|
| 1262 | | "max-stale" [ "=" delta-seconds ] ; <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section 3.2.3</a> |
|---|
| 1263 | | "min-fresh" "=" delta-seconds ; <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section 3.2.3</a> |
|---|
| 1264 | | "no-transform" ; <a href="#no-transform.directive" title="No-Transform Directive">Section 3.2.5</a> |
|---|
| 1265 | | "only-if-cached" ; <a href="#cache.revalidation.and.reload.controls" title="Cache Revalidation and Reload Controls">Section 3.2.4</a> |
|---|
| 1266 | | cache-extension ; <a href="#cache.control.extensions" title="Cache Control Extensions">Section 3.2.6</a> |
|---|
| 1267 | |
|---|
| 1268 | cache-response-directive = |
|---|
| 1269 | "public" ; <a href="#what.is.cacheable" title="What is Cacheable">Section 3.2.1</a> |
|---|
| 1270 | | "private" [ "=" <"> 1#field-name <"> ] ; <a href="#what.is.cacheable" title="What is Cacheable">Section 3.2.1</a> |
|---|
| 1271 | | "no-cache" [ "=" <"> 1#field-name <"> ]; <a href="#what.is.cacheable" title="What is Cacheable">Section 3.2.1</a> |
|---|
| 1272 | | "no-store" ; <a href="#what.may.be.stored.by.caches" title="What May be Stored by Caches">Section 3.2.2</a> |
|---|
| 1273 | | "no-transform" ; <a href="#no-transform.directive" title="No-Transform Directive">Section 3.2.5</a> |
|---|
| 1274 | | "must-revalidate" ; <a href="#cache.revalidation.and.reload.controls" title="Cache Revalidation and Reload Controls">Section 3.2.4</a> |
|---|
| 1275 | | "proxy-revalidate" ; <a href="#cache.revalidation.and.reload.controls" title="Cache Revalidation and Reload Controls">Section 3.2.4</a> |
|---|
| 1276 | | "max-age" "=" delta-seconds ; <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section 3.2.3</a> |
|---|
| 1277 | | "s-maxage" "=" delta-seconds ; <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section 3.2.3</a> |
|---|
| 1278 | | cache-extension ; <a href="#cache.control.extensions" title="Cache Control Extensions">Section 3.2.6</a> |
|---|
| 1279 | |
|---|
| 1280 | cache-extension = token [ "=" ( token | quoted-string ) ] |
|---|
| 1281 | </pre><p id="rfc.section.3.2.p.4">When a directive appears without any 1#field-name parameter, the directive applies to the entire request or response. When |
|---|
| 1282 | such a directive appears with a 1#field-name parameter, it applies only to the named field or fields, and not to the rest |
|---|
| 1283 | of the request or response. This mechanism supports extensibility; implementations of future versions of the HTTP protocol |
|---|
| 1284 | might apply these directives to header fields not defined in HTTP/1.1. |
|---|
| 1285 | </p> |
|---|
| 1286 | <p id="rfc.section.3.2.p.5">The cache-control directives can be broken down into these general categories: </p> |
|---|
| 1287 | <ul> |
|---|
| 1288 | <li>Restrictions on what are cacheable; these may only be imposed by the origin server.</li> |
|---|
| 1289 | <li>Restrictions on what may be stored by a cache; these may be imposed by either the origin server or the user agent.</li> |
|---|
| 1290 | <li>Modifications of the basic expiration mechanism; these may be imposed by either the origin server or the user agent.</li> |
|---|
| 1291 | <li>Controls over cache revalidation and reload; these may only be imposed by a user agent.</li> |
|---|
| 1292 | <li>Control over transformation of entities.</li> |
|---|
| 1293 | <li>Extensions to the caching system.</li> |
|---|
| 1294 | </ul> |
|---|
| 1295 | <h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a> <a id="what.is.cacheable" href="#what.is.cacheable">What is Cacheable</a></h3> |
|---|
| 1296 | <p id="rfc.section.3.2.1.p.1">By default, a response is cacheable if the requirements of the request method, request header fields, and the response status |
|---|
| 1297 | indicate that it is cacheable. <a href="#response.cacheability" title="Response Cacheability">Section 2.4</a> summarizes these defaults for cacheability. The following Cache-Control response directives allow an origin server to override |
|---|
| 1298 | the default cacheability of a response: |
|---|
| 1299 | </p> |
|---|
| 1300 | <p id="rfc.section.3.2.1.p.2"> <span id="rfc.iref.c.4"></span> <span id="rfc.iref.p.1"></span> public |
|---|
| 1301 | </p> |
|---|
| 1302 | <dl class="empty"> |
|---|
| 1303 | <dd>Indicates that the response <em class="bcp14">MAY</em> be cached by any cache, even if it would normally be non-cacheable or cacheable only within a non-shared cache. (See also |
|---|
| 1304 | Authorization, <a href="p7-auth.html#header.authorization" title="Authorization">Section 3.1</a> of <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, for additional details.) |
|---|
| 1305 | </dd> |
|---|
| 1306 | </dl> |
|---|
| 1307 | <p id="rfc.section.3.2.1.p.3"> <span id="rfc.iref.c.5"></span> <span id="rfc.iref.p.2"></span> private |
|---|
| 1308 | </p> |
|---|
| 1309 | <dl class="empty"> |
|---|
| 1310 | <dd>Indicates that all or part of the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be cached by a shared cache. This allows an origin server to state that the specified parts of the response are intended for |
|---|
| 1311 | only one user and are not a valid response for requests by other users. A private (non-shared) cache <em class="bcp14">MAY</em> cache the response. |
|---|
| 1312 | </dd> |
|---|
| 1313 | <dd> <b>Note:</b> This usage of the word private only controls where the response may be cached, and cannot ensure the privacy of the message |
|---|
| 1314 | content. |
|---|
| 1315 | </dd> |
|---|
| 1316 | </dl> |
|---|
| 1317 | <p id="rfc.section.3.2.1.p.4"> <span id="rfc.iref.c.6"></span> <span id="rfc.iref.n.1"></span> no-cache |
|---|
| 1318 | </p> |
|---|
| 1319 | <dl class="empty"> |
|---|
| 1320 | <dd>If the no-cache directive does not specify a field-name, then a cache <em class="bcp14">MUST NOT</em> use the response to satisfy a subsequent request without successful revalidation with the origin server. This allows an origin |
|---|
| 1321 | server to prevent caching even by caches that have been configured to return stale responses to client requests. |
|---|
| 1322 | </dd> |
|---|
| 1323 | <dd>If the no-cache directive does specify one or more field-names, then a cache <em class="bcp14">MAY</em> use the response to satisfy a subsequent request, subject to any other restrictions on caching. However, the specified field-name(s) <em class="bcp14">MUST NOT</em> be sent in the response to a subsequent request without successful revalidation with the origin server. This allows an origin |
|---|
| 1324 | server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response. |
|---|
| 1325 | <dl class="empty"> |
|---|
| 1326 | <dd> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. |
|---|
| 1327 | </dd> |
|---|
| 1328 | </dl> |
|---|
| 1329 | </dd> |
|---|
| 1330 | </dl> |
|---|
| 1331 | <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a> <a id="what.may.be.stored.by.caches" href="#what.may.be.stored.by.caches">What May be Stored by Caches</a></h3> |
|---|
| 1332 | <p id="rfc.section.3.2.2.p.1"> <span id="rfc.iref.c.7"></span> <span id="rfc.iref.n.2"></span> no-store |
|---|
| 1333 | </p> |
|---|
| 1334 | <dl class="empty"> |
|---|
| 1335 | <dd>The purpose of the no-store directive is to prevent the inadvertent release or retention of sensitive information (for example, |
|---|
| 1336 | on backup tapes). The no-store directive applies to the entire message, and <em class="bcp14">MAY</em> be sent either in a response or in a request. If sent in a request, a cache <em class="bcp14">MUST NOT</em> store any part of either this request or any response to it. If sent in a response, a cache <em class="bcp14">MUST NOT</em> store any part of either this response or the request that elicited it. This directive applies to both non-shared and shared |
|---|
| 1337 | caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it. |
|---|
| 1338 | </dd> |
|---|
| 1339 | <dd>Even when this directive is associated with a response, users might explicitly store such a response outside of the caching |
|---|
| 1340 | system (e.g., with a "Save As" dialog). History buffers <em class="bcp14">MAY</em> store such responses as part of their normal operation. |
|---|
| 1341 | </dd> |
|---|
| 1342 | <dd>The purpose of this directive is to meet the stated requirements of certain users and service authors who are concerned about |
|---|
| 1343 | accidental releases of information via unanticipated accesses to cache data structures. While the use of this directive might |
|---|
| 1344 | improve privacy in some cases, we caution that it is NOT in any way a reliable or sufficient mechanism for ensuring privacy. |
|---|
| 1345 | In particular, malicious or compromised caches might not recognize or obey this directive, and communications networks might |
|---|
| 1346 | be vulnerable to eavesdropping. |
|---|
| 1347 | </dd> |
|---|
| 1348 | </dl> |
|---|
| 1349 | <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a> <a id="modifications.of.the.basic.expiration.mechanism" href="#modifications.of.the.basic.expiration.mechanism">Modifications of the Basic Expiration Mechanism</a></h3> |
|---|
| 1350 | <p id="rfc.section.3.2.3.p.1">The expiration time of an entity <em class="bcp14">MAY</em> be specified by the origin server using the Expires header (see <a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section 3.3</a>). Alternatively, it <em class="bcp14">MAY</em> be specified using the max-age directive in a response. When the max-age cache-control directive is present in a cached response, |
|---|
| 1351 | the response is stale if its current age is greater than the age value given (in seconds) at the time of a new request for |
|---|
| 1352 | that resource. The max-age directive on a response implies that the response is cacheable (i.e., "public") unless some other, |
|---|
| 1353 | more restrictive cache directive is also present. |
|---|
| 1354 | </p> |
|---|
| 1355 | <p id="rfc.section.3.2.3.p.2">If a response includes both an Expires header and a max-age directive, the max-age directive overrides the Expires header, |
|---|
| 1356 | even if the Expires header is more restrictive. This rule allows an origin server to provide, for a given response, a longer |
|---|
| 1357 | expiration time to an HTTP/1.1 (or later) cache than to an HTTP/1.0 cache. This might be useful if certain HTTP/1.0 caches |
|---|
| 1358 | improperly calculate ages or expiration times, perhaps due to desynchronized clocks. |
|---|
| 1359 | </p> |
|---|
| 1360 | <p id="rfc.section.3.2.3.p.3">Many HTTP/1.0 cache implementations will treat an Expires value that is less than or equal to the response Date value as being |
|---|
| 1361 | equivalent to the Cache-Control response directive "no-cache". If an HTTP/1.1 cache receives such a response, and the response |
|---|
| 1362 | does not include a Cache-Control header field, it <em class="bcp14">SHOULD</em> consider the response to be non-cacheable in order to retain compatibility with HTTP/1.0 servers. |
|---|
| 1363 | </p> |
|---|
| 1364 | <dl class="empty"> |
|---|
| 1365 | <dd> <b>Note:</b> An origin server might wish to use a relatively new HTTP cache control feature, such as the "private" directive, on a network |
|---|
| 1366 | including older caches that do not understand that feature. The origin server will need to combine the new feature with an |
|---|
| 1367 | Expires field whose value is less than or equal to the Date value. This will prevent older caches from improperly caching |
|---|
| 1368 | the response. |
|---|
| 1369 | </dd> |
|---|
| 1370 | </dl> |
|---|
| 1371 | <p id="rfc.section.3.2.3.p.4"> <span id="rfc.iref.c.8"></span> <span id="rfc.iref.s.3"></span> s-maxage |
|---|
| 1372 | </p> |
|---|
| 1373 | <dl class="empty"> |
|---|
| 1374 | <dd>If a response includes an s-maxage directive, then for a shared cache (but not for a private cache), the maximum age specified |
|---|
| 1375 | by this directive overrides the maximum age specified by either the max-age directive or the Expires header. The s-maxage |
|---|
| 1376 | directive also implies the semantics of the proxy-revalidate directive (see <a href="#cache.revalidation.and.reload.controls" title="Cache Revalidation and Reload Controls">Section 3.2.4</a>), i.e., that the shared cache must not use the entry after it becomes stale to respond to a subsequent request without first |
|---|
| 1377 | revalidating it with the origin server. The s-maxage directive is always ignored by a private cache. |
|---|
| 1378 | </dd> |
|---|
| 1379 | </dl> |
|---|
| 1380 | <p id="rfc.section.3.2.3.p.5">Note that most older caches, not compliant with this specification, do not implement any cache-control directives. An origin |
|---|
| 1381 | server wishing to use a cache-control directive that restricts, but does not prevent, caching by an HTTP/1.1-compliant cache <em class="bcp14">MAY</em> exploit the requirement that the max-age directive overrides the Expires header, and the fact that pre-HTTP/1.1-compliant |
|---|
| 1382 | caches do not observe the max-age directive. |
|---|
| 1383 | </p> |
|---|
| 1384 | <p id="rfc.section.3.2.3.p.6">Other directives allow a user agent to modify the basic expiration mechanism. These directives <em class="bcp14">MAY</em> be specified on a request: |
|---|
| 1385 | </p> |
|---|
| 1386 | <p id="rfc.section.3.2.3.p.7"> <span id="rfc.iref.c.9"></span> <span id="rfc.iref.m.1"></span> max-age |
|---|
| 1387 | </p> |
|---|
| 1388 | <dl class="empty"> |
|---|
| 1389 | <dd>Indicates that the client is willing to accept a response whose age is no greater than the specified time in seconds. Unless |
|---|
| 1390 | max-stale directive is also included, the client is not willing to accept a stale response. |
|---|
| 1391 | </dd> |
|---|
| 1392 | </dl> |
|---|
| 1393 | <p id="rfc.section.3.2.3.p.8"> <span id="rfc.iref.c.10"></span> <span id="rfc.iref.m.2"></span> min-fresh |
|---|
| 1394 | </p> |
|---|
| 1395 | <dl class="empty"> |
|---|
| 1396 | <dd>Indicates that the client is willing to accept a response whose freshness lifetime is no less than its current age plus the |
|---|
| 1397 | specified time in seconds. That is, the client wants a response that will still be fresh for at least the specified number |
|---|
| 1398 | of seconds. |
|---|
| 1399 | </dd> |
|---|
| 1400 | </dl> |
|---|
| 1401 | <p id="rfc.section.3.2.3.p.9"> <span id="rfc.iref.c.11"></span> <span id="rfc.iref.m.3"></span> max-stale |
|---|
| 1402 | </p> |
|---|
| 1403 | <dl class="empty"> |
|---|
| 1404 | <dd>Indicates that the client is willing to accept a response that has exceeded its expiration time. If max-stale is assigned |
|---|
| 1405 | a value, then the client is willing to accept a response that has exceeded its expiration time by no more than the specified |
|---|
| 1406 | number of seconds. If no value is assigned to max-stale, then the client is willing to accept a stale response of any age. |
|---|
| 1407 | </dd> |
|---|
| 1408 | </dl> |
|---|
| 1409 | <p id="rfc.section.3.2.3.p.10">If a cache returns a stale response, either because of a max-stale directive on a request, or because the cache is configured |
|---|
| 1410 | to override the expiration time of a response, the cache <em class="bcp14">MUST</em> attach a Warning header to the stale response, using Warning 110 (Response is stale). |
|---|
| 1411 | </p> |
|---|
| 1412 | <p id="rfc.section.3.2.3.p.11">A cache <em class="bcp14">MAY</em> be configured to return stale responses without validation, but only if this does not conflict with any "MUST"-level requirements |
|---|
| 1413 | concerning cache validation (e.g., a "must-revalidate" cache-control directive). |
|---|
| 1414 | </p> |
|---|
| 1415 | <p id="rfc.section.3.2.3.p.12">If both the new request and the cached entry include "max-age" directives, then the lesser of the two values is used for determining |
|---|
| 1416 | the freshness of the cached entry for that request. |
|---|
| 1417 | </p> |
|---|
| 1418 | <h3 id="rfc.section.3.2.4"><a href="#rfc.section.3.2.4">3.2.4</a> <a id="cache.revalidation.and.reload.controls" href="#cache.revalidation.and.reload.controls">Cache Revalidation and Reload Controls</a></h3> |
|---|
| 1419 | <p id="rfc.section.3.2.4.p.1">Sometimes a user agent might want or need to insist that a cache revalidate its cache entry with the origin server (and not |
|---|
| 1420 | just with the next cache along the path to the origin server), or to reload its cache entry from the origin server. End-to-end |
|---|
| 1421 | revalidation might be necessary if either the cache or the origin server has overestimated the expiration time of the cached |
|---|
| 1422 | response. End-to-end reload may be necessary if the cache entry has become corrupted for some reason. |
|---|
| 1423 | </p> |
|---|
| 1424 | <p id="rfc.section.3.2.4.p.2">End-to-end revalidation may be requested either when the client does not have its own local cached copy, in which case we |
|---|
| 1425 | call it "unspecified end-to-end revalidation", or when the client does have a local cached copy, in which case we call it |
|---|
| 1426 | "specific end-to-end revalidation." |
|---|
| 1427 | </p> |
|---|
| 1428 | <p id="rfc.section.3.2.4.p.3">The client can specify these three kinds of action using Cache-Control request directives:</p> |
|---|
| 1429 | <p id="rfc.section.3.2.4.p.4">End-to-end reload </p> |
|---|
| 1430 | <dl class="empty"> |
|---|
| 1431 | <dd>The request includes a "no-cache" cache-control directive or, for compatibility with HTTP/1.0 clients, "Pragma: no-cache". |
|---|
| 1432 | Field names <em class="bcp14">MUST NOT</em> be included with the no-cache directive in a request. The server <em class="bcp14">MUST NOT</em> use a cached copy when responding to such a request. |
|---|
| 1433 | </dd> |
|---|
| 1434 | </dl> |
|---|
| 1435 | <p id="rfc.section.3.2.4.p.5">Specific end-to-end revalidation </p> |
|---|
| 1436 | <dl class="empty"> |
|---|
| 1437 | <dd>The request includes a "max-age=0" cache-control directive, which forces each cache along the path to the origin server to |
|---|
| 1438 | revalidate its own entry, if any, with the next cache or server. The initial request includes a cache-validating conditional |
|---|
| 1439 | with the client's current validator. |
|---|
| 1440 | </dd> |
|---|
| 1441 | </dl> |
|---|
| 1442 | <p id="rfc.section.3.2.4.p.6">Unspecified end-to-end revalidation </p> |
|---|
| 1443 | <dl class="empty"> |
|---|
| 1444 | <dd>The request includes "max-age=0" cache-control directive, which forces each cache along the path to the origin server to revalidate |
|---|
| 1445 | its own entry, if any, with the next cache or server. The initial request does not include a cache-validating conditional; |
|---|
| 1446 | the first cache along the path (if any) that holds a cache entry for this resource includes a cache-validating conditional |
|---|
| 1447 | with its current validator. |
|---|
| 1448 | </dd> |
|---|
| 1449 | </dl> |
|---|
| 1450 | <p id="rfc.section.3.2.4.p.7"> <span id="rfc.iref.c.12"></span> <span id="rfc.iref.m.4"></span> max-age |
|---|
| 1451 | </p> |
|---|
| 1452 | <dl class="empty"> |
|---|
| 1453 | <dd>When an intermediate cache is forced, by means of a max-age=0 directive, to revalidate its own cache entry, and the client |
|---|
| 1454 | has supplied its own validator in the request, the supplied validator might differ from the validator currently stored with |
|---|
| 1455 | the cache entry. In this case, the cache <em class="bcp14">MAY</em> use either validator in making its own request without affecting semantic transparency. |
|---|
| 1456 | </dd> |
|---|
| 1457 | <dd>However, the choice of validator might affect performance. The best approach is for the intermediate cache to use its own |
|---|
| 1458 | validator when making its request. If the server replies with 304 (Not Modified), then the cache can return its now validated |
|---|
| 1459 | copy to the client with a 200 (OK) response. If the server replies with a new entity and cache validator, however, the intermediate |
|---|
| 1460 | cache can compare the returned validator with the one provided in the client's request, using the strong comparison function. |
|---|
| 1461 | If the client's validator is equal to the origin server's, then the intermediate cache simply returns 304 (Not Modified). |
|---|
| 1462 | Otherwise, it returns the new entity with a 200 (OK) response. |
|---|
| 1463 | </dd> |
|---|
| 1464 | <dd>If a request includes the no-cache directive, it <em class="bcp14">SHOULD NOT</em> include min-fresh, max-stale, or max-age. |
|---|
| 1465 | </dd> |
|---|
| 1466 | </dl> |
|---|
| 1467 | <p id="rfc.section.3.2.4.p.8"> <span id="rfc.iref.c.13"></span> <span id="rfc.iref.o.1"></span> only-if-cached |
|---|
| 1468 | </p> |
|---|
| 1469 | <dl class="empty"> |
|---|
| 1470 | <dd>In some cases, such as times of extremely poor network connectivity, a client may want a cache to return only those responses |
|---|
| 1471 | that it currently has stored, and not to reload or revalidate with the origin server. To do this, the client may include the |
|---|
| 1472 | only-if-cached directive in a request. If it receives this directive, a cache <em class="bcp14">SHOULD</em> either respond using a cached entry that is consistent with the other constraints of the request, or respond with a 504 (Gateway |
|---|
| 1473 | Timeout) status. However, if a group of caches is being operated as a unified system with good internal connectivity, such |
|---|
| 1474 | a request <em class="bcp14">MAY</em> be forwarded within that group of caches. |
|---|
| 1475 | </dd> |
|---|
| 1476 | </dl> |
|---|
| 1477 | <p id="rfc.section.3.2.4.p.9"> <span id="rfc.iref.c.14"></span> <span id="rfc.iref.m.5"></span> must-revalidate |
|---|
| 1478 | </p> |
|---|
| 1479 | <dl class="empty"> |
|---|
| 1480 | <dd>Because a cache <em class="bcp14">MAY</em> be configured to ignore a server's specified expiration time, and because a client request <em class="bcp14">MAY</em> include a max-stale directive (which has a similar effect), the protocol also includes a mechanism for the origin server to |
|---|
| 1481 | require revalidation of a cache entry on any subsequent use. When the must-revalidate directive is present in a response received |
|---|
| 1482 | by a cache, that cache <em class="bcp14">MUST NOT</em> use the entry after it becomes stale to respond to a subsequent request without first revalidating it with the origin server. |
|---|
| 1483 | (I.e., the cache <em class="bcp14">MUST</em> do an end-to-end revalidation every time, if, based solely on the origin server's Expires or max-age value, the cached response |
|---|
| 1484 | is stale.) |
|---|
| 1485 | </dd> |
|---|
| 1486 | <dd>The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances |
|---|
| 1487 | an HTTP/1.1 cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if the cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a 504 (Gateway Timeout) response. |
|---|
| 1488 | </dd> |
|---|
| 1489 | <dd>Servers <em class="bcp14">SHOULD</em> send the must-revalidate directive if and only if failure to revalidate a request on the entity could result in incorrect |
|---|
| 1490 | operation, such as a silently unexecuted financial transaction. Recipients <em class="bcp14">MUST NOT</em> take any automated action that violates this directive, and <em class="bcp14">MUST NOT</em> automatically provide an unvalidated copy of the entity if revalidation fails. |
|---|
| 1491 | </dd> |
|---|
| 1492 | <dd>Although this is not recommended, user agents operating under severe connectivity constraints <em class="bcp14">MAY</em> violate this directive but, if so, <em class="bcp14">MUST</em> explicitly warn the user that an unvalidated response has been provided. The warning <em class="bcp14">MUST</em> be provided on each unvalidated access, and <em class="bcp14">SHOULD</em> require explicit user confirmation. |
|---|
| 1493 | </dd> |
|---|
| 1494 | </dl> |
|---|
| 1495 | <p id="rfc.section.3.2.4.p.10"> <span id="rfc.iref.c.15"></span> <span id="rfc.iref.p.3"></span> proxy-revalidate |
|---|
| 1496 | </p> |
|---|
| 1497 | <dl class="empty"> |
|---|
| 1498 | <dd>The proxy-revalidate directive has the same meaning as the must-revalidate directive, except that it does not apply to non-shared |
|---|
| 1499 | user agent caches. It can be used on a response to an authenticated request to permit the user's cache to store and later |
|---|
| 1500 | return the response without needing to revalidate it (since it has already been authenticated once by that user), while still |
|---|
| 1501 | requiring proxies that service many users to revalidate each time (in order to make sure that each user has been authenticated). |
|---|
| 1502 | Note that such authenticated responses also need the public cache control directive in order to allow them to be cached at |
|---|
| 1503 | all. |
|---|
| 1504 | </dd> |
|---|
| 1505 | </dl> |
|---|
| 1506 | <h3 id="rfc.section.3.2.5"><a href="#rfc.section.3.2.5">3.2.5</a> <a id="no-transform.directive" href="#no-transform.directive">No-Transform Directive</a></h3> |
|---|
| 1507 | <p id="rfc.section.3.2.5.p.1"> <span id="rfc.iref.c.16"></span> <span id="rfc.iref.n.3"></span> no-transform |
|---|
| 1508 | </p> |
|---|
| 1509 | <dl class="empty"> |
|---|
| 1510 | <dd>Implementors of intermediate caches (proxies) have found it useful to convert the media type of certain entity bodies. A non-transparent |
|---|
| 1511 | proxy might, for example, convert between image formats in order to save cache space or to reduce the amount of traffic on |
|---|
| 1512 | a slow link. |
|---|
| 1513 | </dd> |
|---|
| 1514 | <dd>Serious operational problems occur, however, when these transformations are applied to entity bodies intended for certain |
|---|
| 1515 | kinds of applications. For example, applications for medical imaging, scientific data analysis and those using end-to-end |
|---|
| 1516 | authentication, all depend on receiving an entity body that is bit for bit identical to the original entity-body. |
|---|
| 1517 | </dd> |
|---|
| 1518 | <dd>Therefore, if a message includes the no-transform directive, an intermediate cache or proxy <em class="bcp14">MUST NOT</em> change those headers that are listed in <a href="#non-modifiable.headers" title="Non-modifiable Headers">Section 2.5.2</a> as being subject to the no-transform directive. This implies that the cache or proxy <em class="bcp14">MUST NOT</em> change any aspect of the entity-body that is specified by these headers, including the value of the entity-body itself. |
|---|
| 1519 | </dd> |
|---|
| 1520 | </dl> |
|---|
| 1521 | <h3 id="rfc.section.3.2.6"><a href="#rfc.section.3.2.6">3.2.6</a> <a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3> |
|---|
| 1522 | <p id="rfc.section.3.2.6.p.1">The Cache-Control header field can be extended through the use of one or more cache-extension tokens, each with an optional |
|---|
| 1523 | assigned value. Informational extensions (those which do not require a change in cache behavior) <em class="bcp14">MAY</em> be added without changing the semantics of other directives. Behavioral extensions are designed to work by acting as modifiers |
|---|
| 1524 | to the existing base of cache directives. Both the new directive and the standard directive are supplied, such that applications |
|---|
| 1525 | which do not understand the new directive will default to the behavior specified by the standard directive, and those that |
|---|
| 1526 | understand the new directive will recognize it as modifying the requirements associated with the standard directive. In this |
|---|
| 1527 | way, extensions to the cache-control directives can be made without requiring changes to the base protocol. |
|---|
| 1528 | </p> |
|---|
| 1529 | <p id="rfc.section.3.2.6.p.2">This extension mechanism depends on an HTTP cache obeying all of the cache-control directives defined for its native HTTP-version, |
|---|
| 1530 | obeying certain extensions, and ignoring all directives that it does not understand. |
|---|
| 1531 | </p> |
|---|
| 1532 | <p id="rfc.section.3.2.6.p.3">For example, consider a hypothetical new response directive called community which acts as a modifier to the private directive. |
|---|
| 1533 | We define this new directive to mean that, in addition to any non-shared cache, any cache which is shared only by members |
|---|
| 1534 | of the community named within its value may cache the response. An origin server wishing to allow the UCI community to use |
|---|
| 1535 | an otherwise private response in their shared cache(s) could do so by including |
|---|
| 1536 | </p> |
|---|
| 1537 | <div id="rfc.figure.u.12"></div><pre class="text"> Cache-Control: private, community="UCI" |
|---|
| 1538 | </pre><p id="rfc.section.3.2.6.p.5">A cache seeing this header field will act correctly even if the cache does not understand the community cache-extension, since |
|---|
| 1539 | it will also see and understand the private directive and thus default to the safe behavior. |
|---|
| 1540 | </p> |
|---|
| 1541 | <p id="rfc.section.3.2.6.p.6">Unrecognized cache-directives <em class="bcp14">MUST</em> be ignored; it is assumed that any cache-directive likely to be unrecognized by an HTTP/1.1 cache will be combined with standard |
|---|
| 1542 | directives (or the response's default cacheability) such that the cache behavior will remain minimally correct even if the |
|---|
| 1543 | cache does not understand the extension(s). |
|---|
| 1544 | </p> |
|---|
| 1545 | <div id="rfc.iref.e.2"></div> |
|---|
| 1546 | <div id="rfc.iref.h.4"></div> |
|---|
| 1547 | <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a> <a id="header.expires" href="#header.expires">Expires</a></h2> |
|---|
| 1548 | <p id="rfc.section.3.3.p.1">The Expires entity-header field gives the date/time after which the response is considered stale. A stale cache entry may |
|---|
| 1549 | not normally be returned by a cache (either a proxy cache or a user agent cache) unless it is first validated with the origin |
|---|
| 1550 | server (or with an intermediate cache that has a fresh copy of the entity). See <a href="#expiration.model" title="Expiration Model">Section 2.2</a> for further discussion of the expiration model. |
|---|
| 1551 | </p> |
|---|
| 1552 | <p id="rfc.section.3.3.p.2">The presence of an Expires field does not imply that the original resource will change or cease to exist at, before, or after |
|---|
| 1553 | that time. |
|---|
| 1554 | </p> |
|---|
| 1555 | <p id="rfc.section.3.3.p.3">The format is an absolute date and time as defined by HTTP-date in <a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</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>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format. |
|---|
| 1556 | </p> |
|---|
| 1557 | <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span> Expires = "Expires" ":" HTTP-date |
|---|
| 1558 | </pre><p id="rfc.section.3.3.p.5">An example of its use is</p> |
|---|
| 1559 | <div id="rfc.figure.u.14"></div><pre class="text"> Expires: Thu, 01 Dec 1994 16:00:00 GMT |
|---|
| 1560 | </pre><p id="rfc.section.3.3.p.7"> </p> |
|---|
| 1561 | <dl class="empty"> |
|---|
| 1562 | <dd> <b>Note:</b> if a response includes a Cache-Control field with the max-age directive (see <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section 3.2.3</a>), that directive overrides the Expires field. |
|---|
| 1563 | </dd> |
|---|
| 1564 | </dl> |
|---|
| 1565 | <p id="rfc.section.3.3.p.8">HTTP/1.1 clients and caches <em class="bcp14">MUST</em> treat other invalid date formats, especially including the value "0", as in the past (i.e., "already expired"). |
|---|
| 1566 | </p> |
|---|
| 1567 | <p id="rfc.section.3.3.p.9">To mark a response as "already expired," an origin server sends an Expires date that is equal to the Date header value. (See |
|---|
| 1568 | the rules for expiration calculations in <a href="#expiration.calculations" title="Expiration Calculations">Section 2.2.4</a>.) |
|---|
| 1569 | </p> |
|---|
| 1570 | <p id="rfc.section.3.3.p.10">To mark a response as "never expires," an origin server sends an Expires date approximately one year from the time the response |
|---|
| 1571 | is sent. HTTP/1.1 servers <em class="bcp14">SHOULD NOT</em> send Expires dates more than one year in the future. |
|---|
| 1572 | </p> |
|---|
| 1573 | <p id="rfc.section.3.3.p.11">The presence of an Expires header field with a date value of some time in the future on a response that otherwise would by |
|---|
| 1574 | default be non-cacheable indicates that the response is cacheable, unless indicated otherwise by a Cache-Control header field |
|---|
| 1575 | (<a href="#header.cache-control" id="rfc.xref.header.cache-control.9" title="Cache-Control">Section 3.2</a>). |
|---|
| 1576 | </p> |
|---|
| 1577 | <div id="rfc.iref.p.4"></div> |
|---|
| 1578 | <div id="rfc.iref.h.5"></div> |
|---|
| 1579 | <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a> <a id="header.pragma" href="#header.pragma">Pragma</a></h2> |
|---|
| 1580 | <p id="rfc.section.3.4.p.1">The Pragma general-header field is used to include implementation-specific directives that might apply to any recipient along |
|---|
| 1581 | the request/response chain. All pragma directives specify optional behavior from the viewpoint of the protocol; however, some |
|---|
| 1582 | systems <em class="bcp14">MAY</em> require that behavior be consistent with the directives. |
|---|
| 1583 | </p> |
|---|
| 1584 | <div id="rfc.figure.u.15"></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> Pragma = "Pragma" ":" 1#pragma-directive |
|---|
| 1585 | pragma-directive = "no-cache" | extension-pragma |
|---|
| 1586 | extension-pragma = token [ "=" ( token | quoted-string ) ] |
|---|
| 1587 | </pre><p id="rfc.section.3.4.p.3">When the no-cache directive is present in a request message, an application <em class="bcp14">SHOULD</em> forward the request toward the origin server even if it has a cached copy of what is being requested. This pragma directive |
|---|
| 1588 | has the same semantics as the no-cache cache-directive (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.10" title="Cache-Control">Section 3.2</a>) and is defined here for backward compatibility with HTTP/1.0. Clients <em class="bcp14">SHOULD</em> include both header fields when a no-cache request is sent to a server not known to be HTTP/1.1 compliant. |
|---|
| 1589 | </p> |
|---|
| 1590 | <p id="rfc.section.3.4.p.4">Pragma directives <em class="bcp14">MUST</em> be passed through by a proxy or gateway application, regardless of their significance to that application, since the directives |
|---|
| 1591 | might be applicable to all recipients along the request/response chain. It is not possible to specify a pragma for a specific |
|---|
| 1592 | recipient; however, any pragma directive not relevant to a recipient <em class="bcp14">SHOULD</em> be ignored by that recipient. |
|---|
| 1593 | </p> |
|---|
| 1594 | <p id="rfc.section.3.4.p.5">HTTP/1.1 caches <em class="bcp14">SHOULD</em> treat "Pragma: no-cache" as if the client had sent "Cache-Control: no-cache". No new Pragma directives will be defined in |
|---|
| 1595 | HTTP. |
|---|
| 1596 | </p> |
|---|
| 1597 | <dl class="empty"> |
|---|
| 1598 | <dd> <b>Note:</b> because the meaning of "Pragma: no-cache as a response header field is not actually specified, it does not provide a reliable |
|---|
| 1599 | replacement for "Cache-Control: no-cache" in a response |
|---|
| 1600 | </dd> |
|---|
| 1601 | </dl> |
|---|
| 1602 | <div id="rfc.iref.v.2"></div> |
|---|
| 1603 | <div id="rfc.iref.h.6"></div> |
|---|
| 1604 | <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a> <a id="header.vary" href="#header.vary">Vary</a></h2> |
|---|
| 1605 | <p id="rfc.section.3.5.p.1">The Vary field value indicates the set of request-header fields that fully determines, while the response is fresh, whether |
|---|
| 1606 | a cache is permitted to use the response to reply to a subsequent request without revalidation. For uncacheable or stale responses, |
|---|
| 1607 | the Vary field value advises the user agent about the criteria that were used to select the representation. A Vary field value |
|---|
| 1608 | of "*" implies that a cache cannot determine from the request headers of a subsequent request whether this response is the |
|---|
| 1609 | appropriate representation. See <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section 2.6</a> for use of the Vary header field by caches. |
|---|
| 1610 | </p> |
|---|
| 1611 | <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.13"></span> Vary = "Vary" ":" ( "*" | 1#field-name ) |
|---|
| 1612 | </pre><p id="rfc.section.3.5.p.3">An HTTP/1.1 server <em class="bcp14">SHOULD</em> include a Vary header field with any cacheable response that is subject to server-driven negotiation. Doing so allows a cache |
|---|
| 1613 | to properly interpret future requests on that resource and informs the user agent about the presence of negotiation on that |
|---|
| 1614 | resource. A server <em class="bcp14">MAY</em> include a Vary header field with a non-cacheable response that is subject to server-driven negotiation, since this might provide |
|---|
| 1615 | the user agent with useful information about the dimensions over which the response varies at the time of the response. |
|---|
| 1616 | </p> |
|---|
| 1617 | <p id="rfc.section.3.5.p.4">A Vary field value consisting of a list of field-names signals that the representation selected for the response is based |
|---|
| 1618 | on a selection algorithm which considers ONLY the listed request-header field values in selecting the most appropriate representation. |
|---|
| 1619 | A cache <em class="bcp14">MAY</em> assume that the same selection will be made for future requests with the same values for the listed field names, for the duration |
|---|
| 1620 | of time for which the response is fresh. |
|---|
| 1621 | </p> |
|---|
| 1622 | <p id="rfc.section.3.5.p.5">The field-names given are not limited to the set of standard request-header fields defined by this specification. Field names |
|---|
| 1623 | are case-insensitive. |
|---|
| 1624 | </p> |
|---|
| 1625 | <p id="rfc.section.3.5.p.6">A Vary field value of "*" signals that unspecified parameters not limited to the request-headers (e.g., the network address |
|---|
| 1626 | of the client), play a role in the selection of the response representation. The "*" value <em class="bcp14">MUST NOT</em> be generated by a proxy server; it may only be generated by an origin server. |
|---|
| 1627 | </p> |
|---|
| 1628 | <div id="rfc.iref.w.1"></div> |
|---|
| 1629 | <div id="rfc.iref.h.7"></div> |
|---|
| 1630 | <h2 id="rfc.section.3.6"><a href="#rfc.section.3.6">3.6</a> <a id="header.warning" href="#header.warning">Warning</a></h2> |
|---|
| 1631 | <p id="rfc.section.3.6.p.1">The Warning general-header field is used to carry additional information about the status or transformation of a message which |
|---|
| 1632 | might not be reflected in the message. This information is typically used to warn about a possible lack of semantic transparency |
|---|
| 1633 | from caching operations or transformations applied to the entity body of the message. |
|---|
| 1634 | </p> |
|---|
| 1635 | <p id="rfc.section.3.6.p.2">Warning headers are sent with responses using:</p> |
|---|
| 1636 | <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span> Warning = "Warning" ":" 1#warning-value |
|---|
| 1637 | |
|---|
| 1638 | warning-value = warn-code SP warn-agent SP warn-text |
|---|
| 1639 | [SP warn-date] |
|---|
| 1640 | |
|---|
| 1641 | warn-code = 3DIGIT |
|---|
| 1642 | warn-agent = ( host [ ":" port ] ) | pseudonym |
|---|
| 1643 | ; the name or pseudonym of the server adding |
|---|
| 1644 | ; the Warning header, for use in debugging |
|---|
| 1645 | warn-text = quoted-string |
|---|
| 1646 | warn-date = <"> HTTP-date <"> |
|---|
| 1647 | </pre><p id="rfc.section.3.6.p.4">A response <em class="bcp14">MAY</em> carry more than one Warning header. |
|---|
| 1648 | </p> |
|---|
| 1649 | <p id="rfc.section.3.6.p.5">The warn-text <em class="bcp14">SHOULD</em> be in a natural language and character set that is most likely to be intelligible to the human user receiving the response. |
|---|
| 1650 | This decision <em class="bcp14">MAY</em> be based on any available knowledge, such as the location of the cache or user, the Accept-Language field in a request, the |
|---|
| 1651 | Content-Language field in a response, etc. The default language is English and the default character set is ISO-8859-1 (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>). |
|---|
| 1652 | </p> |
|---|
| 1653 | <p id="rfc.section.3.6.p.6">If a character set other than ISO-8859-1 is used, it <em class="bcp14">MUST</em> be encoded in the warn-text using the method described in <a href="#RFC2047" id="rfc.xref.RFC2047.1"><cite title="MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text">[RFC2047]</cite></a>. |
|---|
| 1654 | </p> |
|---|
| 1655 | <p id="rfc.section.3.6.p.7">Warning headers can in general be applied to any message, however some specific warn-codes are specific to caches and can |
|---|
| 1656 | only be applied to response messages. New Warning headers <em class="bcp14">SHOULD</em> be added after any existing Warning headers. A cache <em class="bcp14">MUST NOT</em> delete any Warning header that it received with a message. However, if a cache successfully validates a cache entry, it <em class="bcp14">SHOULD</em> remove any Warning headers previously attached to that entry except as specified for specific Warning codes. It <em class="bcp14">MUST</em> then add any Warning headers received in the validating response. In other words, Warning headers are those that would be |
|---|
| 1657 | attached to the most recent relevant response. |
|---|
| 1658 | </p> |
|---|
| 1659 | <p id="rfc.section.3.6.p.8">When multiple Warning headers are attached to a response, the user agent ought to inform the user of as many of them as possible, |
|---|
| 1660 | in the order that they appear in the response. If it is not possible to inform the user of all of the warnings, the user agent <em class="bcp14">SHOULD</em> follow these heuristics: |
|---|
| 1661 | </p> |
|---|
| 1662 | <ul> |
|---|
| 1663 | <li>Warnings that appear early in the response take priority over those appearing later in the response.</li> |
|---|
| 1664 | <li>Warnings in the user's preferred character set take priority over warnings in other character sets but with identical warn-codes |
|---|
| 1665 | and warn-agents. |
|---|
| 1666 | </li> |
|---|
| 1667 | </ul> |
|---|
| 1668 | <p id="rfc.section.3.6.p.9">Systems that generate multiple Warning headers <em class="bcp14">SHOULD</em> order them with this user agent behavior in mind. |
|---|
| 1669 | </p> |
|---|
| 1670 | <p id="rfc.section.3.6.p.10">Requirements for the behavior of caches with respect to Warnings are stated in <a href="#warnings" title="Warnings">Section 2.1.2</a>. |
|---|
| 1671 | </p> |
|---|
| 1672 | <p id="rfc.section.3.6.p.11">This is a list of the currently-defined warn-codes, each with a recommended warn-text in English, and a description of its |
|---|
| 1673 | meaning. |
|---|
| 1674 | </p> |
|---|
| 1675 | <p id="rfc.section.3.6.p.12">110 Response is stale </p> |
|---|
| 1676 | <dl class="empty"> |
|---|
| 1677 | <dd> <em class="bcp14">MUST</em> be included whenever the returned response is stale. |
|---|
| 1678 | </dd> |
|---|
| 1679 | </dl> |
|---|
| 1680 | <p id="rfc.section.3.6.p.13">111 Revalidation failed </p> |
|---|
| 1681 | <dl class="empty"> |
|---|
| 1682 | <dd> <em class="bcp14">MUST</em> be included if a cache returns a stale response because an attempt to revalidate the response failed, due to an inability |
|---|
| 1683 | to reach the server. |
|---|
| 1684 | </dd> |
|---|
| 1685 | </dl> |
|---|
| 1686 | <p id="rfc.section.3.6.p.14">112 Disconnected operation </p> |
|---|
| 1687 | <dl class="empty"> |
|---|
| 1688 | <dd> <em class="bcp14">SHOULD</em> be included if the cache is intentionally disconnected from the rest of the network for a period of time. |
|---|
| 1689 | </dd> |
|---|
| 1690 | </dl> |
|---|
| 1691 | <p id="rfc.section.3.6.p.15">113 Heuristic expiration </p> |
|---|
| 1692 | <dl class="empty"> |
|---|
| 1693 | <dd> <em class="bcp14">MUST</em> be included if the cache heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater |
|---|
| 1694 | than 24 hours. |
|---|
| 1695 | </dd> |
|---|
| 1696 | </dl> |
|---|
| 1697 | <p id="rfc.section.3.6.p.16">199 Miscellaneous warning </p> |
|---|
| 1698 | <dl class="empty"> |
|---|
| 1699 | <dd>The warning text <em class="bcp14">MAY</em> include arbitrary information to be presented to a human user, or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action, besides presenting the warning to the user. |
|---|
| 1700 | </dd> |
|---|
| 1701 | </dl> |
|---|
| 1702 | <p id="rfc.section.3.6.p.17">214 Transformation applied </p> |
|---|
| 1703 | <dl class="empty"> |
|---|
| 1704 | <dd> <em class="bcp14">MUST</em> be added by an intermediate cache or proxy if it applies any transformation changing the content-coding (as specified in the |
|---|
| 1705 | Content-Encoding header) or media-type (as specified in the Content-Type header) of the response, or the entity-body of the |
|---|
| 1706 | response, unless this Warning code already appears in the response. |
|---|
| 1707 | </dd> |
|---|
| 1708 | </dl> |
|---|
| 1709 | <p id="rfc.section.3.6.p.18">299 Miscellaneous persistent warning </p> |
|---|
| 1710 | <dl class="empty"> |
|---|
| 1711 | <dd>The warning text <em class="bcp14">MAY</em> include arbitrary information to be presented to a human user, or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action. |
|---|
| 1712 | </dd> |
|---|
| 1713 | </dl> |
|---|
| 1714 | <p id="rfc.section.3.6.p.19">If an implementation sends a message with one or more Warning headers whose version is HTTP/1.0 or lower, then the sender <em class="bcp14">MUST</em> include in each warning-value a warn-date that matches the date in the response. |
|---|
| 1715 | </p> |
|---|
| 1716 | <p id="rfc.section.3.6.p.20">If an implementation receives a message with a warning-value that includes a warn-date, and that warn-date is different from |
|---|
| 1717 | the Date value in the response, then that warning-value <em class="bcp14">MUST</em> be deleted from the message before storing, forwarding, or using it. (This prevents bad consequences of naive caching of Warning |
|---|
| 1718 | header fields.) If all of the warning-values are deleted for this reason, the Warning header <em class="bcp14">MUST</em> be deleted as well. |
|---|
| 1719 | </p> |
|---|
| 1720 | <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> |
|---|
| 1721 | <p id="rfc.section.4.p.1">TBD.</p> |
|---|
| 1722 | <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> |
|---|
| 1723 | <p id="rfc.section.5.p.1">Caching proxies provide additional potential vulnerabilities, since the contents of the cache represent an attractive target |
|---|
| 1724 | for malicious exploitation. Because cache contents persist after an HTTP request is complete, an attack on the cache can reveal |
|---|
| 1725 | information long after a user believes that the information has been removed from the network. Therefore, cache contents should |
|---|
| 1726 | be protected as sensitive information. |
|---|
| 1727 | </p> |
|---|
| 1728 | <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> |
|---|
| 1729 | <p id="rfc.section.6.p.1">Much of the content and presentation of the caching design is due to suggestions and comments from individuals including: |
|---|
| 1730 | Shel Kaphan, Paul Leach, Koen Holtman, David Morris, and Larry Masinter. |
|---|
| 1731 | </p> |
|---|
| 1732 | <h1 id="rfc.references"><a id="rfc.section.7" href="#rfc.section.7">7.</a> References |
|---|
| 1733 | </h1> |
|---|
| 1734 | <h2 id="rfc.references.1"><a href="#rfc.section.7.1" id="rfc.section.7.1">7.1</a> Normative References |
|---|
| 1735 | </h2> |
|---|
| 1736 | <table summary="Normative References"> |
|---|
| 1737 | <tr> |
|---|
| 1738 | <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> |
|---|
| 1739 | <td class="top">International Organization for Standardization, “ |
|---|
| 1740 | Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 |
|---|
| 1741 | ”, ISO/IEC 8859-1:1998, 1998. |
|---|
| 1742 | </td> |
|---|
| 1743 | </tr> |
|---|
| 1744 | <tr> |
|---|
| 1745 | <td class="reference"><b id="Part1">[Part1]</b></td> |
|---|
| 1746 | <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), January 2008. |
|---|
| 1747 | </td> |
|---|
| 1748 | </tr> |
|---|
| 1749 | <tr> |
|---|
| 1750 | <td class="reference"><b id="Part2">[Part2]</b></td> |
|---|
| 1751 | <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), January 2008. |
|---|
| 1752 | </td> |
|---|
| 1753 | </tr> |
|---|
| 1754 | <tr> |
|---|
| 1755 | <td class="reference"><b id="Part3">[Part3]</b></td> |
|---|
| 1756 | <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), January 2008. |
|---|
| 1757 | </td> |
|---|
| 1758 | </tr> |
|---|
| 1759 | <tr> |
|---|
| 1760 | <td class="reference"><b id="Part4">[Part4]</b></td> |
|---|
| 1761 | <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), January 2008. |
|---|
| 1762 | </td> |
|---|
| 1763 | </tr> |
|---|
| 1764 | <tr> |
|---|
| 1765 | <td class="reference"><b id="Part5">[Part5]</b></td> |
|---|
| 1766 | <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), January 2008. |
|---|
| 1767 | </td> |
|---|
| 1768 | </tr> |
|---|
| 1769 | <tr> |
|---|
| 1770 | <td class="reference"><b id="Part7">[Part7]</b></td> |
|---|
| 1771 | <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), January 2008. |
|---|
| 1772 | </td> |
|---|
| 1773 | </tr> |
|---|
| 1774 | <tr> |
|---|
| 1775 | <td class="reference"><b id="RFC2119">[RFC2119]</b></td> |
|---|
| 1776 | <td class="top"><a title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997. |
|---|
| 1777 | </td> |
|---|
| 1778 | </tr> |
|---|
| 1779 | </table> |
|---|
| 1780 | <h2 id="rfc.references.2"><a href="#rfc.section.7.2" id="rfc.section.7.2">7.2</a> Informative References |
|---|
| 1781 | </h2> |
|---|
| 1782 | <table summary="Informative References"> |
|---|
| 1783 | <tr> |
|---|
| 1784 | <td class="reference"><b id="RFC2616">[RFC2616]</b></td> |
|---|
| 1785 | <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2616, June 1999. |
|---|
| 1786 | </td> |
|---|
| 1787 | </tr> |
|---|
| 1788 | </table> |
|---|
| 1789 | <h2 id="rfc.references.3"><a href="#rfc.section.7.3" id="rfc.section.7.3">7.3</a> References (to be categorized) |
|---|
| 1790 | </h2> |
|---|
| 1791 | <table summary="References (to be categorized)"> |
|---|
| 1792 | <tr> |
|---|
| 1793 | <td class="reference"><b id="RFC1305">[RFC1305]</b></td> |
|---|
| 1794 | <td class="top"><a title="University of Delaware, Electrical Engineering Department">Mills, D.</a>, “<a href="http://tools.ietf.org/html/rfc1305">Network Time Protocol (Version 3) Specification, Implementation</a>”, RFC 1305, March 1992. |
|---|
| 1795 | </td> |
|---|
| 1796 | </tr> |
|---|
| 1797 | <tr> |
|---|
| 1798 | <td class="reference"><b id="RFC2047">[RFC2047]</b></td> |
|---|
| 1799 | <td class="top"><a title="University of Tennessee">Moore, K.</a>, “<a href="http://tools.ietf.org/html/rfc2047">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</a>”, RFC 2047, November 1996. |
|---|
| 1800 | </td> |
|---|
| 1801 | </tr> |
|---|
| 1802 | </table> |
|---|
| 1803 | <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> |
|---|
| 1804 | <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> |
|---|
| 1805 | (editor) |
|---|
| 1806 | <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Day Software</span><span class="adr"><span class="street-address vcardline">23 Corporate Plaza DR, Suite 280</span><span class="vcardline"><span class="locality">Newport Beach</span>, <span class="region">CA</span> <span class="postal-code">92660</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel">Phone: <a href="tel:+1-949-706-5300"><span class="value">+1-949-706-5300</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1-949-706-5305"><span class="value">+1-949-706-5305</span></a></span><span class="vcardline">EMail: <a><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address> |
|---|
| 1807 | <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">One Laptop per Child</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span> <span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address> |
|---|
| 1808 | <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Hewlett-Packard Company</span><span class="adr"><span class="street-address vcardline">HP Labs, Large Scale Systems Group</span><span class="street-address vcardline">1501 Page Mill Road, MS 1177</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span> <span class="postal-code">94304</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">JeffMogul@acm.org</span></a></span></address> |
|---|
| 1809 | <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span> <span class="postal-code">98052</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">henrikn@microsoft.com</span></a></span></address> |
|---|
| 1810 | <address class="vcard"><span class="vcardline"><span class="fn">Larry Masinter</span><span class="n hidden"><span class="family-name">Masinter</span><span class="given-name">Larry</span></span></span><span class="org vcardline">Adobe Systems, Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span> <span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">LMM@acm.org</span></a></span><span class="vcardline">URI: <a href="http://larry.masinter.net/" class="url">http://larry.masinter.net/</a></span></address> |
|---|
| 1811 | <address class="vcard"><span class="vcardline"><span class="fn">Paul J. Leach</span><span class="n hidden"><span class="family-name">Leach</span><span class="given-name">Paul J.</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span> <span class="postal-code">98052</span></span></span><span class="vcardline">EMail: <a><span class="email">paulle@microsoft.com</span></a></span></address> |
|---|
| 1812 | <address class="vcard"><span class="vcardline"><span class="fn">Tim Berners-Lee</span><span class="n hidden"><span class="family-name">Berners-Lee</span><span class="given-name">Tim</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Computer Science and Artificial Intelligence Laboratory</span><span class="street-address vcardline">The Stata Center, Building 32</span><span class="street-address vcardline">32 Vassar Street</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span> <span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">timbl@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.w3.org/People/Berners-Lee/" class="url">http://www.w3.org/People/Berners-Lee/</a></span></address> |
|---|
| 1813 | <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span> |
|---|
| 1814 | (editor) |
|---|
| 1815 | <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span> <span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">EMail: <a><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address> |
|---|
| 1816 | <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span> |
|---|
| 1817 | (editor) |
|---|
| 1818 | <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address> |
|---|
| 1819 | <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> |
|---|
| 1820 | <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> |
|---|
| 1821 | <p id="rfc.section.A.1.p.1">A case was missed in the Cache-Control model of HTTP/1.1; s-maxage was introduced to add this missing case. (Sections <a href="#response.cacheability" title="Response Cacheability">2.4</a>, <a href="#header.cache-control" id="rfc.xref.header.cache-control.11" title="Cache-Control">3.2</a>, <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">3.2.3</a>) |
|---|
| 1822 | </p> |
|---|
| 1823 | <p id="rfc.section.A.1.p.2">The Cache-Control: max-age directive was not properly defined for responses. (<a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section 3.2.3</a>) |
|---|
| 1824 | </p> |
|---|
| 1825 | <p id="rfc.section.A.1.p.3">Warnings could be cached incorrectly, or not updated appropriately. (Section <a href="#warnings" title="Warnings">2.1.2</a>, <a href="#expiration.calculations" title="Expiration Calculations">2.2.4</a>, <a href="#non-modifiable.headers" title="Non-modifiable Headers">2.5.2</a>, <a href="#combining.headers" title="Combining Headers">2.5.3</a>, <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">3.2.3</a>, and <a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">3.6</a>) Warning also needed to be a general header, as PUT or other methods may have need for it in requests. |
|---|
| 1826 | </p> |
|---|
| 1827 | <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> |
|---|
| 1828 | <p id="rfc.section.A.2.p.1">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Invalidation After Updates or Deletions">Section 2.10</a>) |
|---|
| 1829 | </p> |
|---|
| 1830 | <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> Change Log (to be removed by RFC Editor before publication) |
|---|
| 1831 | </h1> |
|---|
| 1832 | <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a> Since RFC2616 |
|---|
| 1833 | </h2> |
|---|
| 1834 | <p id="rfc.section.B.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. |
|---|
| 1835 | </p> |
|---|
| 1836 | <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a> Since draft-ietf-httpbis-p6-cache-00 |
|---|
| 1837 | </h2> |
|---|
| 1838 | <p id="rfc.section.B.2.p.1">Closed issues: </p> |
|---|
| 1839 | <ul> |
|---|
| 1840 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/9">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/9</a>>: "Trailer" (<<a href="http://purl.org/NET/http-errata#trailer-hop">http://purl.org/NET/http-errata#trailer-hop</a>>) |
|---|
| 1841 | </li> |
|---|
| 1842 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/12">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/12</a>>: "Invalidation after Update or Delete" (<<a href="http://purl.org/NET/http-errata#invalidupd">http://purl.org/NET/http-errata#invalidupd</a>>) |
|---|
| 1843 | </li> |
|---|
| 1844 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/48">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/48</a>>: "Date reference typo" |
|---|
| 1845 | </li> |
|---|
| 1846 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/49">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/49</a>>: "Connection header text" |
|---|
| 1847 | </li> |
|---|
| 1848 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66</a>>: "ISO-8859-1 Reference" |
|---|
| 1849 | </li> |
|---|
| 1850 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/87">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/87</a>>: "typo in 13.2.2" |
|---|
| 1851 | </li> |
|---|
| 1852 | </ul> |
|---|
| 1853 | <p id="rfc.section.B.2.p.2">Other changes: </p> |
|---|
| 1854 | <ul> |
|---|
| 1855 | <li>Start work on categorizing references as "Normative" or "Informative".</li> |
|---|
| 1856 | </ul> |
|---|
| 1857 | <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> |
|---|
| 1858 | <p>Copyright © The IETF Trust (2008).</p> |
|---|
| 1859 | <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the |
|---|
| 1860 | authors retain all their rights. |
|---|
| 1861 | </p> |
|---|
| 1862 | <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION |
|---|
| 1863 | HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE |
|---|
| 1864 | DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN |
|---|
| 1865 | WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
|---|
| 1866 | </p> |
|---|
| 1867 | <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1> |
|---|
| 1868 | <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might |
|---|
| 1869 | be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any |
|---|
| 1870 | license under such rights might or might not be available; nor does it represent that it has made any independent effort to |
|---|
| 1871 | identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and |
|---|
| 1872 | BCP 79. |
|---|
| 1873 | </p> |
|---|
| 1874 | <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result |
|---|
| 1875 | of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users |
|---|
| 1876 | of this specification can be obtained from the IETF on-line IPR repository at <<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>>. |
|---|
| 1877 | </p> |
|---|
| 1878 | <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary |
|---|
| 1879 | rights that may cover technology that may be required to implement this standard. Please address the information to the IETF |
|---|
| 1880 | at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>. |
|---|
| 1881 | </p> |
|---|
| 1882 | <h1>Acknowledgement</h1> |
|---|
| 1883 | <p>Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).</p> |
|---|
| 1884 | <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> |
|---|
| 1885 | <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a> |
|---|
| 1886 | </p> |
|---|
| 1887 | <div class="print2col"> |
|---|
| 1888 | <ul class="ind"> |
|---|
| 1889 | <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind"> |
|---|
| 1890 | <li class="indline1">age <a class="iref" href="#rfc.iref.a.1">1.2</a></li> |
|---|
| 1891 | <li class="indline1">Age header <a class="iref" href="#rfc.iref.a.2"><b>3.1</b></a></li> |
|---|
| 1892 | </ul> |
|---|
| 1893 | </li> |
|---|
| 1894 | <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind"> |
|---|
| 1895 | <li class="indline1">cache <a class="iref" href="#rfc.iref.c.1">1.2</a></li> |
|---|
| 1896 | <li class="indline1">Cache Directives |
|---|
| 1897 | <ul class="ind"> |
|---|
| 1898 | <li class="indline1">max-age <a class="iref" href="#rfc.iref.c.9"><b>3.2.3</b></a>, <a class="iref" href="#rfc.iref.c.12"><b>3.2.4</b></a></li> |
|---|
| 1899 | <li class="indline1">max-stale <a class="iref" href="#rfc.iref.c.11"><b>3.2.3</b></a></li> |
|---|
| 1900 | <li class="indline1">min-fresh <a class="iref" href="#rfc.iref.c.10"><b>3.2.3</b></a></li> |
|---|
| 1901 | <li class="indline1">must-revalidate <a class="iref" href="#rfc.iref.c.14"><b>3.2.4</b></a></li> |
|---|
| 1902 | <li class="indline1">no-cache <a class="iref" href="#rfc.iref.c.6"><b>3.2.1</b></a></li> |
|---|
| 1903 | <li class="indline1">no-store <a class="iref" href="#rfc.iref.c.7"><b>3.2.2</b></a></li> |
|---|
| 1904 | <li class="indline1">no-transform <a class="iref" href="#rfc.iref.c.16"><b>3.2.5</b></a></li> |
|---|
| 1905 | <li class="indline1">only-if-cached <a class="iref" href="#rfc.iref.c.13"><b>3.2.4</b></a></li> |
|---|
| 1906 | <li class="indline1">private <a class="iref" href="#rfc.iref.c.5"><b>3.2.1</b></a></li> |
|---|
| 1907 | <li class="indline1">proxy-revalidate <a class="iref" href="#rfc.iref.c.15"><b>3.2.4</b></a></li> |
|---|
| 1908 | <li class="indline1">public <a class="iref" href="#rfc.iref.c.4"><b>3.2.1</b></a></li> |
|---|
| 1909 | <li class="indline1">s-maxage <a class="iref" href="#rfc.iref.c.8"><b>3.2.3</b></a></li> |
|---|
| 1910 | </ul> |
|---|
| 1911 | </li> |
|---|
| 1912 | <li class="indline1">Cache-Control header <a class="iref" href="#rfc.xref.header.cache-control.1">2.1.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.2">2.1.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.3">2.1.3</a>, <a class="iref" href="#rfc.xref.header.cache-control.4">2.2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.5">2.2.5</a>, <a class="iref" href="#rfc.xref.header.cache-control.6">2.4</a>, <a class="iref" href="#rfc.xref.header.cache-control.7">2.4</a>, <a class="iref" href="#rfc.xref.header.cache-control.8">2.8</a>, <a class="iref" href="#rfc.iref.c.3"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.cache-control.9">3.3</a>, <a class="iref" href="#rfc.xref.header.cache-control.10">3.4</a>, <a class="iref" href="#rfc.xref.header.cache-control.11">A.1</a></li> |
|---|
| 1913 | <li class="indline1">cacheable <a class="iref" href="#rfc.iref.c.2">1.2</a></li> |
|---|
| 1914 | </ul> |
|---|
| 1915 | </li> |
|---|
| 1916 | <li class="indline0"><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul class="ind"> |
|---|
| 1917 | <li class="indline1">Expires header <a class="iref" href="#rfc.xref.header.expires.1">2.4</a>, <a class="iref" href="#rfc.xref.header.expires.2">3.2.3</a>, <a class="iref" href="#rfc.iref.e.2"><b>3.3</b></a></li> |
|---|
| 1918 | <li class="indline1">explicit expiration time <a class="iref" href="#rfc.iref.e.1">1.2</a></li> |
|---|
| 1919 | </ul> |
|---|
| 1920 | </li> |
|---|
| 1921 | <li class="indline0"><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul class="ind"> |
|---|
| 1922 | <li class="indline1">first-hand <a class="iref" href="#rfc.iref.f.1">1.2</a></li> |
|---|
| 1923 | <li class="indline1">fresh <a class="iref" href="#rfc.iref.f.3">1.2</a></li> |
|---|
| 1924 | <li class="indline1">freshness lifetime <a class="iref" href="#rfc.iref.f.2">1.2</a></li> |
|---|
| 1925 | </ul> |
|---|
| 1926 | </li> |
|---|
| 1927 | <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind"> |
|---|
| 1928 | <li class="indline1"><tt>Grammar</tt> |
|---|
| 1929 | <ul class="ind"> |
|---|
| 1930 | <li class="indline1"><tt>Age</tt> <a class="iref" href="#rfc.iref.g.2"><b>3.1</b></a></li> |
|---|
| 1931 | <li class="indline1"><tt>age-value</tt> <a class="iref" href="#rfc.iref.g.3"><b>3.1</b></a></li> |
|---|
| 1932 | <li class="indline1"><tt>Cache-Control</tt> <a class="iref" href="#rfc.iref.g.4"><b>3.2</b></a></li> |
|---|
| 1933 | <li class="indline1"><tt>cache-directive</tt> <a class="iref" href="#rfc.iref.g.5"><b>3.2</b></a></li> |
|---|
| 1934 | <li class="indline1"><tt>cache-extension</tt> <a class="iref" href="#rfc.iref.g.8"><b>3.2</b></a></li> |
|---|
| 1935 | <li class="indline1"><tt>cache-request-directive</tt> <a class="iref" href="#rfc.iref.g.6"><b>3.2</b></a></li> |
|---|
| 1936 | <li class="indline1"><tt>cache-response-directive</tt> <a class="iref" href="#rfc.iref.g.7"><b>3.2</b></a></li> |
|---|
| 1937 | <li class="indline1"><tt>delta-seconds</tt> <a class="iref" href="#rfc.iref.g.1"><b>1.3</b></a></li> |
|---|
| 1938 | <li class="indline1"><tt>Expires</tt> <a class="iref" href="#rfc.iref.g.9"><b>3.3</b></a></li> |
|---|
| 1939 | <li class="indline1"><tt>extension-pragma</tt> <a class="iref" href="#rfc.iref.g.12"><b>3.4</b></a></li> |
|---|
| 1940 | <li class="indline1"><tt>Pragma</tt> <a class="iref" href="#rfc.iref.g.10"><b>3.4</b></a></li> |
|---|
| 1941 | <li class="indline1"><tt>pragma-directive</tt> <a class="iref" href="#rfc.iref.g.11"><b>3.4</b></a></li> |
|---|
| 1942 | <li class="indline1"><tt>Vary</tt> <a class="iref" href="#rfc.iref.g.13"><b>3.5</b></a></li> |
|---|
| 1943 | <li class="indline1"><tt>warn-agent</tt> <a class="iref" href="#rfc.iref.g.17"><b>3.6</b></a></li> |
|---|
| 1944 | <li class="indline1"><tt>warn-code</tt> <a class="iref" href="#rfc.iref.g.16"><b>3.6</b></a></li> |
|---|
| 1945 | <li class="indline1"><tt>warn-date</tt> <a class="iref" href="#rfc.iref.g.19"><b>3.6</b></a></li> |
|---|
| 1946 | <li class="indline1"><tt>warn-text</tt> <a class="iref" href="#rfc.iref.g.18"><b>3.6</b></a></li> |
|---|
| 1947 | <li class="indline1"><tt>Warning</tt> <a class="iref" href="#rfc.iref.g.14"><b>3.6</b></a></li> |
|---|
| 1948 | <li class="indline1"><tt>warning-value</tt> <a class="iref" href="#rfc.iref.g.15"><b>3.6</b></a></li> |
|---|
| 1949 | </ul> |
|---|
| 1950 | </li> |
|---|
| 1951 | </ul> |
|---|
| 1952 | </li> |
|---|
| 1953 | <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind"> |
|---|
| 1954 | <li class="indline1">Headers |
|---|
| 1955 | <ul class="ind"> |
|---|
| 1956 | <li class="indline1">Age <a class="iref" href="#rfc.iref.h.2"><b>3.1</b></a></li> |
|---|
| 1957 | <li class="indline1">Cache-Control <a class="iref" href="#rfc.xref.header.cache-control.1">2.1.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.2">2.1.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.3">2.1.3</a>, <a class="iref" href="#rfc.xref.header.cache-control.4">2.2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.5">2.2.5</a>, <a class="iref" href="#rfc.xref.header.cache-control.6">2.4</a>, <a class="iref" href="#rfc.xref.header.cache-control.7">2.4</a>, <a class="iref" href="#rfc.xref.header.cache-control.8">2.8</a>, <a class="iref" href="#rfc.iref.h.3"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.cache-control.9">3.3</a>, <a class="iref" href="#rfc.xref.header.cache-control.10">3.4</a>, <a class="iref" href="#rfc.xref.header.cache-control.11">A.1</a></li> |
|---|
| 1958 | <li class="indline1">Expires <a class="iref" href="#rfc.xref.header.expires.1">2.4</a>, <a class="iref" href="#rfc.xref.header.expires.2">3.2.3</a>, <a class="iref" href="#rfc.iref.h.4"><b>3.3</b></a></li> |
|---|
| 1959 | <li class="indline1">Pragma <a class="iref" href="#rfc.xref.header.pragma.1">3.2</a>, <a class="iref" href="#rfc.iref.h.5"><b>3.4</b></a></li> |
|---|
| 1960 | <li class="indline1">Vary <a class="iref" href="#rfc.xref.header.vary.1">2.6</a>, <a class="iref" href="#rfc.iref.h.6"><b>3.5</b></a></li> |
|---|
| 1961 | <li class="indline1">Warning <a class="iref" href="#rfc.xref.header.warning.1">2.1.1</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.1.2</a>, <a class="iref" href="#rfc.xref.header.warning.3">2.1.2</a>, <a class="iref" href="#rfc.xref.header.warning.4">2.5.2</a>, <a class="iref" href="#rfc.xref.header.warning.5">2.5.3</a>, <a class="iref" href="#rfc.iref.h.7"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.6">A.1</a></li> |
|---|
| 1962 | </ul> |
|---|
| 1963 | </li> |
|---|
| 1964 | <li class="indline1">heuristic expiration time <a class="iref" href="#rfc.iref.h.1">1.2</a></li> |
|---|
| 1965 | </ul> |
|---|
| 1966 | </li> |
|---|
| 1967 | <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> |
|---|
| 1968 | <li class="indline1"><em>ISO-8859-1</em> <a class="iref" href="#rfc.xref.ISO-8859-1.1">3.6</a>, <a class="iref" href="#ISO-8859-1"><b>7.1</b></a></li> |
|---|
| 1969 | </ul> |
|---|
| 1970 | </li> |
|---|
| 1971 | <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind"> |
|---|
| 1972 | <li class="indline1">max-age |
|---|
| 1973 | <ul class="ind"> |
|---|
| 1974 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.m.1"><b>3.2.3</b></a>, <a class="iref" href="#rfc.iref.m.4"><b>3.2.4</b></a></li> |
|---|
| 1975 | </ul> |
|---|
| 1976 | </li> |
|---|
| 1977 | <li class="indline1">max-stale |
|---|
| 1978 | <ul class="ind"> |
|---|
| 1979 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.m.3"><b>3.2.3</b></a></li> |
|---|
| 1980 | </ul> |
|---|
| 1981 | </li> |
|---|
| 1982 | <li class="indline1">min-fresh |
|---|
| 1983 | <ul class="ind"> |
|---|
| 1984 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.m.2"><b>3.2.3</b></a></li> |
|---|
| 1985 | </ul> |
|---|
| 1986 | </li> |
|---|
| 1987 | <li class="indline1">must-revalidate |
|---|
| 1988 | <ul class="ind"> |
|---|
| 1989 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.m.5"><b>3.2.4</b></a></li> |
|---|
| 1990 | </ul> |
|---|
| 1991 | </li> |
|---|
| 1992 | </ul> |
|---|
| 1993 | </li> |
|---|
| 1994 | <li class="indline0"><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul class="ind"> |
|---|
| 1995 | <li class="indline1">no-cache |
|---|
| 1996 | <ul class="ind"> |
|---|
| 1997 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.n.1"><b>3.2.1</b></a></li> |
|---|
| 1998 | </ul> |
|---|
| 1999 | </li> |
|---|
| 2000 | <li class="indline1">no-store |
|---|
| 2001 | <ul class="ind"> |
|---|
| 2002 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.n.2"><b>3.2.2</b></a></li> |
|---|
| 2003 | </ul> |
|---|
| 2004 | </li> |
|---|
| 2005 | <li class="indline1">no-transform |
|---|
| 2006 | <ul class="ind"> |
|---|
| 2007 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.n.3"><b>3.2.5</b></a></li> |
|---|
| 2008 | </ul> |
|---|
| 2009 | </li> |
|---|
| 2010 | </ul> |
|---|
| 2011 | </li> |
|---|
| 2012 | <li class="indline0"><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul class="ind"> |
|---|
| 2013 | <li class="indline1">only-if-cached |
|---|
| 2014 | <ul class="ind"> |
|---|
| 2015 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.o.1"><b>3.2.4</b></a></li> |
|---|
| 2016 | </ul> |
|---|
| 2017 | </li> |
|---|
| 2018 | </ul> |
|---|
| 2019 | </li> |
|---|
| 2020 | <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> |
|---|
| 2021 | <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">2.2.3</a>, <a class="iref" href="#rfc.xref.Part1.2">2.5.1</a>, <a class="iref" href="#rfc.xref.Part1.3">2.5.2</a>, <a class="iref" href="#rfc.xref.Part1.4">2.5.2</a>, <a class="iref" href="#rfc.xref.Part1.5">2.6</a>, <a class="iref" href="#rfc.xref.Part1.6">3.3</a>, <a class="iref" href="#Part1"><b>7.1</b></a><ul class="ind"> |
|---|
| 2022 | <li class="indline1"><em>Section 3.3.1</em> <a class="iref" href="#rfc.xref.Part1.6">3.3</a></li> |
|---|
| 2023 | <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part1.5">2.6</a></li> |
|---|
| 2024 | <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part1.3">2.5.2</a>, <a class="iref" href="#rfc.xref.Part1.4">2.5.2</a></li> |
|---|
| 2025 | <li class="indline1"><em>Section 8.1</em> <a class="iref" href="#rfc.xref.Part1.2">2.5.1</a></li> |
|---|
| 2026 | <li class="indline1"><em>Section 8.3</em> <a class="iref" href="#rfc.xref.Part1.1">2.2.3</a></li> |
|---|
| 2027 | </ul> |
|---|
| 2028 | </li> |
|---|
| 2029 | <li class="indline1"><em>Part2</em> <a class="iref" href="#rfc.xref.Part2.1">2.9</a>, <a class="iref" href="#Part2"><b>7.1</b></a><ul class="ind"> |
|---|
| 2030 | <li class="indline1"><em>Section 8.1.1</em> <a class="iref" href="#rfc.xref.Part2.1">2.9</a></li> |
|---|
| 2031 | </ul> |
|---|
| 2032 | </li> |
|---|
| 2033 | <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">2.5.2</a>, <a class="iref" href="#rfc.xref.Part3.2">2.6</a>, <a class="iref" href="#Part3"><b>7.1</b></a><ul class="ind"> |
|---|
| 2034 | <li class="indline1"><em>Section 3.2.2</em> <a class="iref" href="#rfc.xref.Part3.1">2.5.2</a></li> |
|---|
| 2035 | <li class="indline1"><em>Section 4.1</em> <a class="iref" href="#rfc.xref.Part3.2">2.6</a></li> |
|---|
| 2036 | </ul> |
|---|
| 2037 | </li> |
|---|
| 2038 | <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1">2.3</a>, <a class="iref" href="#rfc.xref.Part4.2">2.3.2</a>, <a class="iref" href="#rfc.xref.Part4.3">2.3.2</a>, <a class="iref" href="#Part4"><b>7.1</b></a><ul class="ind"> |
|---|
| 2039 | <li class="indline1"><em>Section 2</em> <a class="iref" href="#rfc.xref.Part4.2">2.3.2</a></li> |
|---|
| 2040 | <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part4.1">2.3</a></li> |
|---|
| 2041 | <li class="indline1"><em>Section 6</em> <a class="iref" href="#rfc.xref.Part4.3">2.3.2</a></li> |
|---|
| 2042 | </ul> |
|---|
| 2043 | </li> |
|---|
| 2044 | <li class="indline1"><em>Part5</em> <a class="iref" href="#rfc.xref.Part5.1">2.5.3</a>, <a class="iref" href="#rfc.xref.Part5.2">2.8</a>, <a class="iref" href="#Part5"><b>7.1</b></a><ul class="ind"> |
|---|
| 2045 | <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part5.1">2.5.3</a>, <a class="iref" href="#rfc.xref.Part5.2">2.8</a></li> |
|---|
| 2046 | </ul> |
|---|
| 2047 | </li> |
|---|
| 2048 | <li class="indline1"><em>Part7</em> <a class="iref" href="#rfc.xref.Part7.1">2.4</a>, <a class="iref" href="#rfc.xref.Part7.2">3.2.1</a>, <a class="iref" href="#Part7"><b>7.1</b></a><ul class="ind"> |
|---|
| 2049 | <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part7.1">2.4</a>, <a class="iref" href="#rfc.xref.Part7.2">3.2.1</a></li> |
|---|
| 2050 | </ul> |
|---|
| 2051 | </li> |
|---|
| 2052 | <li class="indline1">Pragma header <a class="iref" href="#rfc.xref.header.pragma.1">3.2</a>, <a class="iref" href="#rfc.iref.p.4"><b>3.4</b></a></li> |
|---|
| 2053 | <li class="indline1">private |
|---|
| 2054 | <ul class="ind"> |
|---|
| 2055 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.p.2"><b>3.2.1</b></a></li> |
|---|
| 2056 | </ul> |
|---|
| 2057 | </li> |
|---|
| 2058 | <li class="indline1">proxy-revalidate |
|---|
| 2059 | <ul class="ind"> |
|---|
| 2060 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.p.3"><b>3.2.4</b></a></li> |
|---|
| 2061 | </ul> |
|---|
| 2062 | </li> |
|---|
| 2063 | <li class="indline1">public |
|---|
| 2064 | <ul class="ind"> |
|---|
| 2065 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.p.1"><b>3.2.1</b></a></li> |
|---|
| 2066 | </ul> |
|---|
| 2067 | </li> |
|---|
| 2068 | </ul> |
|---|
| 2069 | </li> |
|---|
| 2070 | <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"> |
|---|
| 2071 | <li class="indline1"><em>RFC1305</em> <a class="iref" href="#rfc.xref.RFC1305.1">2.2.3</a>, <a class="iref" href="#RFC1305"><b>7.3</b></a></li> |
|---|
| 2072 | <li class="indline1"><em>RFC2047</em> <a class="iref" href="#rfc.xref.RFC2047.1">3.6</a>, <a class="iref" href="#RFC2047"><b>7.3</b></a></li> |
|---|
| 2073 | <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>7.1</b></a></li> |
|---|
| 2074 | <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>7.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">B.1</a></li> |
|---|
| 2075 | </ul> |
|---|
| 2076 | </li> |
|---|
| 2077 | <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind"> |
|---|
| 2078 | <li class="indline1">s-maxage |
|---|
| 2079 | <ul class="ind"> |
|---|
| 2080 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.s.3"><b>3.2.3</b></a></li> |
|---|
| 2081 | </ul> |
|---|
| 2082 | </li> |
|---|
| 2083 | <li class="indline1">semantically transparent <a class="iref" href="#rfc.iref.s.2">1.2</a></li> |
|---|
| 2084 | <li class="indline1">stale <a class="iref" href="#rfc.iref.s.1">1.2</a></li> |
|---|
| 2085 | </ul> |
|---|
| 2086 | </li> |
|---|
| 2087 | <li class="indline0"><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul class="ind"> |
|---|
| 2088 | <li class="indline1">validator <a class="iref" href="#rfc.iref.v.1">1.2</a></li> |
|---|
| 2089 | <li class="indline1">Vary header <a class="iref" href="#rfc.xref.header.vary.1">2.6</a>, <a class="iref" href="#rfc.iref.v.2"><b>3.5</b></a></li> |
|---|
| 2090 | </ul> |
|---|
| 2091 | </li> |
|---|
| 2092 | <li class="indline0"><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul class="ind"> |
|---|
| 2093 | <li class="indline1">Warning header <a class="iref" href="#rfc.xref.header.warning.1">2.1.1</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.1.2</a>, <a class="iref" href="#rfc.xref.header.warning.3">2.1.2</a>, <a class="iref" href="#rfc.xref.header.warning.4">2.5.2</a>, <a class="iref" href="#rfc.xref.header.warning.5">2.5.3</a>, <a class="iref" href="#rfc.iref.w.1"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.6">A.1</a></li> |
|---|
| 2094 | </ul> |
|---|
| 2095 | </li> |
|---|
| 2096 | </ul> |
|---|
| 2097 | </div> |
|---|
| 2098 | </body> |
|---|
| 2099 | </html> |
|---|
![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
