| 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 | h3, h4, h5, h6 { |
|---|
| 65 | font-size: 10pt; |
|---|
| 66 | page-break-after: avoid; |
|---|
| 67 | } |
|---|
| 68 | h2 a, h3 a, h4 a, h5 a, h6 a { |
|---|
| 69 | color: black; |
|---|
| 70 | } |
|---|
| 71 | img { |
|---|
| 72 | margin-left: 3em; |
|---|
| 73 | } |
|---|
| 74 | li { |
|---|
| 75 | margin-left: 2em; |
|---|
| 76 | margin-right: 2em; |
|---|
| 77 | } |
|---|
| 78 | ol { |
|---|
| 79 | margin-left: 2em; |
|---|
| 80 | margin-right: 2em; |
|---|
| 81 | } |
|---|
| 82 | ol p { |
|---|
| 83 | margin-left: 0em; |
|---|
| 84 | } |
|---|
| 85 | p { |
|---|
| 86 | margin-left: 2em; |
|---|
| 87 | margin-right: 2em; |
|---|
| 88 | } |
|---|
| 89 | pre { |
|---|
| 90 | margin-left: 3em; |
|---|
| 91 | background-color: lightyellow; |
|---|
| 92 | padding: .25em; |
|---|
| 93 | } |
|---|
| 94 | pre.text2 { |
|---|
| 95 | border-style: dotted; |
|---|
| 96 | border-width: 1px; |
|---|
| 97 | background-color: #f0f0f0; |
|---|
| 98 | width: 69em; |
|---|
| 99 | } |
|---|
| 100 | pre.inline { |
|---|
| 101 | background-color: white; |
|---|
| 102 | padding: 0em; |
|---|
| 103 | } |
|---|
| 104 | pre.text { |
|---|
| 105 | border-style: dotted; |
|---|
| 106 | border-width: 1px; |
|---|
| 107 | background-color: #f8f8f8; |
|---|
| 108 | width: 69em; |
|---|
| 109 | } |
|---|
| 110 | pre.drawing { |
|---|
| 111 | border-style: solid; |
|---|
| 112 | border-width: 1px; |
|---|
| 113 | background-color: #f8f8f8; |
|---|
| 114 | padding: 2em; |
|---|
| 115 | } |
|---|
| 116 | sup { |
|---|
| 117 | font-size: 60%; |
|---|
| 118 | } |
|---|
| 119 | table { |
|---|
| 120 | margin-left: 2em; |
|---|
| 121 | } |
|---|
| 122 | table.tt { |
|---|
| 123 | vertical-align: top; |
|---|
| 124 | } |
|---|
| 125 | table.full { |
|---|
| 126 | border-style: outset; |
|---|
| 127 | border-width: 1px; |
|---|
| 128 | } |
|---|
| 129 | table.headers { |
|---|
| 130 | border-style: outset; |
|---|
| 131 | border-width: 1px; |
|---|
| 132 | } |
|---|
| 133 | table.tt td { |
|---|
| 134 | vertical-align: top; |
|---|
| 135 | } |
|---|
| 136 | table.full td { |
|---|
| 137 | border-style: inset; |
|---|
| 138 | border-width: 1px; |
|---|
| 139 | } |
|---|
| 140 | table.tt th { |
|---|
| 141 | vertical-align: top; |
|---|
| 142 | } |
|---|
| 143 | table.full th { |
|---|
| 144 | border-style: inset; |
|---|
| 145 | border-width: 1px; |
|---|
| 146 | } |
|---|
| 147 | table.headers th { |
|---|
| 148 | border-style: none none inset none; |
|---|
| 149 | border-width: 1px; |
|---|
| 150 | } |
|---|
| 151 | caption { |
|---|
| 152 | caption-side: bottom; |
|---|
| 153 | font-weight: bold; |
|---|
| 154 | font-size: 9pt; |
|---|
| 155 | margin-top: .5em; |
|---|
| 156 | } |
|---|
| 157 | |
|---|
| 158 | table.header { |
|---|
| 159 | width: 95%; |
|---|
| 160 | font-size: 10pt; |
|---|
| 161 | color: white; |
|---|
| 162 | } |
|---|
| 163 | td.top { |
|---|
| 164 | vertical-align: top; |
|---|
| 165 | } |
|---|
| 166 | td.topnowrap { |
|---|
| 167 | vertical-align: top; |
|---|
| 168 | white-space: nowrap; |
|---|
| 169 | } |
|---|
| 170 | td.header { |
|---|
| 171 | background-color: gray; |
|---|
| 172 | width: 50%; |
|---|
| 173 | } |
|---|
| 174 | td.header a { |
|---|
| 175 | color: white; |
|---|
| 176 | } |
|---|
| 177 | td.reference { |
|---|
| 178 | vertical-align: top; |
|---|
| 179 | white-space: nowrap; |
|---|
| 180 | padding-right: 1em; |
|---|
| 181 | } |
|---|
| 182 | thead { |
|---|
| 183 | display:table-header-group; |
|---|
| 184 | } |
|---|
| 185 | ul.toc { |
|---|
| 186 | list-style: none; |
|---|
| 187 | margin-left: 1.5em; |
|---|
| 188 | margin-right: 0em; |
|---|
| 189 | padding-left: 0em; |
|---|
| 190 | } |
|---|
| 191 | li.tocline0 { |
|---|
| 192 | line-height: 150%; |
|---|
| 193 | font-weight: bold; |
|---|
| 194 | font-size: 10pt; |
|---|
| 195 | margin-left: 0em; |
|---|
| 196 | margin-right: 0em; |
|---|
| 197 | } |
|---|
| 198 | li.tocline1 { |
|---|
| 199 | line-height: normal; |
|---|
| 200 | font-weight: normal; |
|---|
| 201 | font-size: 9pt; |
|---|
| 202 | margin-left: 0em; |
|---|
| 203 | margin-right: 0em; |
|---|
| 204 | } |
|---|
| 205 | li.tocline2 { |
|---|
| 206 | font-size: 0pt; |
|---|
| 207 | } |
|---|
| 208 | ul p { |
|---|
| 209 | margin-left: 0em; |
|---|
| 210 | } |
|---|
| 211 | ul.ind { |
|---|
| 212 | list-style: none; |
|---|
| 213 | margin-left: 1.5em; |
|---|
| 214 | margin-right: 0em; |
|---|
| 215 | padding-left: 0em; |
|---|
| 216 | page-break-before: avoid; |
|---|
| 217 | } |
|---|
| 218 | li.indline0 { |
|---|
| 219 | font-weight: bold; |
|---|
| 220 | line-height: 200%; |
|---|
| 221 | margin-left: 0em; |
|---|
| 222 | margin-right: 0em; |
|---|
| 223 | } |
|---|
| 224 | li.indline1 { |
|---|
| 225 | font-weight: normal; |
|---|
| 226 | line-height: 150%; |
|---|
| 227 | margin-left: 0em; |
|---|
| 228 | margin-right: 0em; |
|---|
| 229 | } |
|---|
| 230 | .bcp14 { |
|---|
| 231 | font-style: normal; |
|---|
| 232 | text-transform: lowercase; |
|---|
| 233 | font-variant: small-caps; |
|---|
| 234 | } |
|---|
| 235 | .comment { |
|---|
| 236 | background-color: yellow; |
|---|
| 237 | } |
|---|
| 238 | .center { |
|---|
| 239 | text-align: center; |
|---|
| 240 | } |
|---|
| 241 | .error { |
|---|
| 242 | color: red; |
|---|
| 243 | font-style: italic; |
|---|
| 244 | font-weight: bold; |
|---|
| 245 | } |
|---|
| 246 | .figure { |
|---|
| 247 | font-weight: bold; |
|---|
| 248 | text-align: center; |
|---|
| 249 | font-size: 9pt; |
|---|
| 250 | } |
|---|
| 251 | .filename { |
|---|
| 252 | color: #333333; |
|---|
| 253 | font-weight: bold; |
|---|
| 254 | font-size: 12pt; |
|---|
| 255 | line-height: 21pt; |
|---|
| 256 | text-align: center; |
|---|
| 257 | } |
|---|
| 258 | .fn { |
|---|
| 259 | font-weight: bold; |
|---|
| 260 | } |
|---|
| 261 | .hidden { |
|---|
| 262 | display: none; |
|---|
| 263 | } |
|---|
| 264 | .left { |
|---|
| 265 | text-align: left; |
|---|
| 266 | } |
|---|
| 267 | .right { |
|---|
| 268 | text-align: right; |
|---|
| 269 | } |
|---|
| 270 | .title { |
|---|
| 271 | color: #990000; |
|---|
| 272 | font-size: 18pt; |
|---|
| 273 | line-height: 18pt; |
|---|
| 274 | font-weight: bold; |
|---|
| 275 | text-align: center; |
|---|
| 276 | margin-top: 36pt; |
|---|
| 277 | } |
|---|
| 278 | .vcardline { |
|---|
| 279 | display: block; |
|---|
| 280 | } |
|---|
| 281 | .warning { |
|---|
| 282 | font-size: 14pt; |
|---|
| 283 | background-color: yellow; |
|---|
| 284 | } |
|---|
| 285 | |
|---|
| 286 | |
|---|
| 287 | @media print { |
|---|
| 288 | .noprint { |
|---|
| 289 | display: none; |
|---|
| 290 | } |
|---|
| 291 | |
|---|
| 292 | a { |
|---|
| 293 | color: black; |
|---|
| 294 | text-decoration: none; |
|---|
| 295 | } |
|---|
| 296 | |
|---|
| 297 | table.header { |
|---|
| 298 | width: 90%; |
|---|
| 299 | } |
|---|
| 300 | |
|---|
| 301 | td.header { |
|---|
| 302 | width: 50%; |
|---|
| 303 | color: black; |
|---|
| 304 | background-color: white; |
|---|
| 305 | vertical-align: top; |
|---|
| 306 | font-size: 12pt; |
|---|
| 307 | } |
|---|
| 308 | |
|---|
| 309 | ul.toc a::after { |
|---|
| 310 | content: leader('.') target-counter(attr(href), page); |
|---|
| 311 | } |
|---|
| 312 | |
|---|
| 313 | a.iref { |
|---|
| 314 | content: target-counter(attr(href), page); |
|---|
| 315 | } |
|---|
| 316 | |
|---|
| 317 | .print2col { |
|---|
| 318 | column-count: 2; |
|---|
| 319 | -moz-column-count: 2; |
|---|
| 320 | column-fill: auto; |
|---|
| 321 | } |
|---|
| 322 | } |
|---|
| 323 | |
|---|
| 324 | @page { |
|---|
| 325 | @top-left { |
|---|
| 326 | content: "INTERNET DRAFT"; |
|---|
| 327 | } |
|---|
| 328 | @top-right { |
|---|
| 329 | content: "March 2009"; |
|---|
| 330 | } |
|---|
| 331 | @top-center { |
|---|
| 332 | content: "HTTP/1.1, Part 6"; |
|---|
| 333 | } |
|---|
| 334 | @bottom-left { |
|---|
| 335 | content: "Fielding, et al."; |
|---|
| 336 | } |
|---|
| 337 | @bottom-center { |
|---|
| 338 | content: "Standards Track"; |
|---|
| 339 | } |
|---|
| 340 | @bottom-right { |
|---|
| 341 | content: "[Page " counter(page) "]"; |
|---|
| 342 | } |
|---|
| 343 | } |
|---|
| 344 | |
|---|
| 345 | @page:first { |
|---|
| 346 | @top-left { |
|---|
| 347 | content: normal; |
|---|
| 348 | } |
|---|
| 349 | @top-right { |
|---|
| 350 | content: normal; |
|---|
| 351 | } |
|---|
| 352 | @top-center { |
|---|
| 353 | content: normal; |
|---|
| 354 | } |
|---|
| 355 | } |
|---|
| 356 | </style><link rel="Contents" href="#rfc.toc"> |
|---|
| 357 | <link rel="Author" href="#rfc.authors"> |
|---|
| 358 | <link rel="Copyright" href="#rfc.copyright"> |
|---|
| 359 | <link rel="Index" href="#rfc.index"> |
|---|
| 360 | <link rel="Chapter" title="1 Introduction" href="#rfc.section.1"> |
|---|
| 361 | <link rel="Chapter" title="2 Cache Operation" href="#rfc.section.2"> |
|---|
| 362 | <link rel="Chapter" title="3 Header Field Definitions" href="#rfc.section.3"> |
|---|
| 363 | <link rel="Chapter" title="4 History Lists" href="#rfc.section.4"> |
|---|
| 364 | <link rel="Chapter" title="5 IANA Considerations" href="#rfc.section.5"> |
|---|
| 365 | <link rel="Chapter" title="6 Security Considerations" href="#rfc.section.6"> |
|---|
| 366 | <link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7"> |
|---|
| 367 | <link rel="Chapter" href="#rfc.section.8" title="8 References"> |
|---|
| 368 | <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A"> |
|---|
| 369 | <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> |
|---|
| 370 | <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> |
|---|
| 371 | <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.424, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> |
|---|
| 372 | <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> |
|---|
| 373 | <meta name="DC.Creator" content="Fielding, R."> |
|---|
| 374 | <meta name="DC.Creator" content="Gettys, J."> |
|---|
| 375 | <meta name="DC.Creator" content="Mogul, J."> |
|---|
| 376 | <meta name="DC.Creator" content="Frystyk, H."> |
|---|
| 377 | <meta name="DC.Creator" content="Masinter, L."> |
|---|
| 378 | <meta name="DC.Creator" content="Leach, P."> |
|---|
| 379 | <meta name="DC.Creator" content="Berners-Lee, T."> |
|---|
| 380 | <meta name="DC.Creator" content="Lafon, Y."> |
|---|
| 381 | <meta name="DC.Creator" content="Reschke, J. F."> |
|---|
| 382 | <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> |
|---|
| 383 | <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-03"> |
|---|
| 384 | <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> |
|---|
| 385 | <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. 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."> |
|---|
| 386 | </head> |
|---|
| 387 | <body> |
|---|
| 388 | <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1"> |
|---|
| 389 | <tr> |
|---|
| 390 | <td class="header left">HTTPbis Working Group</td> |
|---|
| 391 | <td class="header right">R. Fielding, Editor</td> |
|---|
| 392 | </tr> |
|---|
| 393 | <tr> |
|---|
| 394 | <td class="header left">Internet Draft</td> |
|---|
| 395 | <td class="header right">Day Software</td> |
|---|
| 396 | </tr> |
|---|
| 397 | <tr> |
|---|
| 398 | <td class="header left"> |
|---|
| 399 | <draft-ietf-httpbis-p6-cache-latest> |
|---|
| 400 | |
|---|
| 401 | </td> |
|---|
| 402 | <td class="header right">J. Gettys</td> |
|---|
| 403 | </tr> |
|---|
| 404 | <tr> |
|---|
| 405 | <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) |
|---|
| 406 | </td> |
|---|
| 407 | <td class="header right">One Laptop per Child</td> |
|---|
| 408 | </tr> |
|---|
| 409 | <tr> |
|---|
| 410 | <td class="header left">Intended status: Standards Track</td> |
|---|
| 411 | <td class="header right">J. Mogul</td> |
|---|
| 412 | </tr> |
|---|
| 413 | <tr> |
|---|
| 414 | <td class="header left">Expires: September 2009</td> |
|---|
| 415 | <td class="header right">HP</td> |
|---|
| 416 | </tr> |
|---|
| 417 | <tr> |
|---|
| 418 | <td class="header left"></td> |
|---|
| 419 | <td class="header right">H. Frystyk</td> |
|---|
| 420 | </tr> |
|---|
| 421 | <tr> |
|---|
| 422 | <td class="header left"></td> |
|---|
| 423 | <td class="header right">Microsoft</td> |
|---|
| 424 | </tr> |
|---|
| 425 | <tr> |
|---|
| 426 | <td class="header left"></td> |
|---|
| 427 | <td class="header right">L. Masinter</td> |
|---|
| 428 | </tr> |
|---|
| 429 | <tr> |
|---|
| 430 | <td class="header left"></td> |
|---|
| 431 | <td class="header right">Adobe Systems</td> |
|---|
| 432 | </tr> |
|---|
| 433 | <tr> |
|---|
| 434 | <td class="header left"></td> |
|---|
| 435 | <td class="header right">P. Leach</td> |
|---|
| 436 | </tr> |
|---|
| 437 | <tr> |
|---|
| 438 | <td class="header left"></td> |
|---|
| 439 | <td class="header right">Microsoft</td> |
|---|
| 440 | </tr> |
|---|
| 441 | <tr> |
|---|
| 442 | <td class="header left"></td> |
|---|
| 443 | <td class="header right">T. Berners-Lee</td> |
|---|
| 444 | </tr> |
|---|
| 445 | <tr> |
|---|
| 446 | <td class="header left"></td> |
|---|
| 447 | <td class="header right">W3C/MIT</td> |
|---|
| 448 | </tr> |
|---|
| 449 | <tr> |
|---|
| 450 | <td class="header left"></td> |
|---|
| 451 | <td class="header right">Y. Lafon, Editor</td> |
|---|
| 452 | </tr> |
|---|
| 453 | <tr> |
|---|
| 454 | <td class="header left"></td> |
|---|
| 455 | <td class="header right">W3C</td> |
|---|
| 456 | </tr> |
|---|
| 457 | <tr> |
|---|
| 458 | <td class="header left"></td> |
|---|
| 459 | <td class="header right">J. F. Reschke, Editor</td> |
|---|
| 460 | </tr> |
|---|
| 461 | <tr> |
|---|
| 462 | <td class="header left"></td> |
|---|
| 463 | <td class="header right">greenbytes</td> |
|---|
| 464 | </tr> |
|---|
| 465 | <tr> |
|---|
| 466 | <td class="header left"></td> |
|---|
| 467 | <td class="header right">March 2, 2009</td> |
|---|
| 468 | </tr> |
|---|
| 469 | </table> |
|---|
| 470 | <p class="title">HTTP/1.1, part 6: Caching<br><span class="filename">draft-ietf-httpbis-p6-cache-latest</span></p> |
|---|
| 471 | <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1> |
|---|
| 472 | <p>This Internet-Draft is submitted to IETF pursuant to, and in full conformance with, the provisions of BCP 78 and BCP 79. This |
|---|
| 473 | document may contain material from IETF Documents or IETF Contributions published or made publicly available before November |
|---|
| 474 | 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to |
|---|
| 475 | allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) |
|---|
| 476 | controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative |
|---|
| 477 | works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate |
|---|
| 478 | it into languages other than English. |
|---|
| 479 | </p> |
|---|
| 480 | <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note |
|---|
| 481 | that other groups may also distribute working documents as Internet-Drafts. |
|---|
| 482 | </p> |
|---|
| 483 | <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other |
|---|
| 484 | documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work |
|---|
| 485 | in progress”. |
|---|
| 486 | </p> |
|---|
| 487 | <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>>. |
|---|
| 488 | </p> |
|---|
| 489 | <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>>. |
|---|
| 490 | </p> |
|---|
| 491 | <p>This Internet-Draft will expire in September 2009.</p> |
|---|
| 492 | <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> |
|---|
| 493 | <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> |
|---|
| 494 | <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date |
|---|
| 495 | of publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. |
|---|
| 496 | </p> |
|---|
| 497 | <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> |
|---|
| 498 | <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information |
|---|
| 499 | systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, |
|---|
| 500 | taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control |
|---|
| 501 | cache behavior or indicate cacheable response messages. |
|---|
| 502 | </p> |
|---|
| 503 | <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> |
|---|
| 504 | <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues |
|---|
| 505 | list is at <<a href="http://tools.ietf.org/wg/httpbis/trac/report/11">http://tools.ietf.org/wg/httpbis/trac/report/11</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. |
|---|
| 506 | </p> |
|---|
| 507 | <p>The changes in this draft are summarized in <a href="#changes.since.04" title="Since draft-ietf-httpbis-p6-cache-04">Appendix C.6</a>. |
|---|
| 508 | </p> |
|---|
| 509 | <hr class="noprint"> |
|---|
| 510 | <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1> |
|---|
| 511 | <ul class="toc"> |
|---|
| 512 | <li class="tocline0">1. <a href="#caching">Introduction</a><ul class="toc"> |
|---|
| 513 | <li class="tocline1">1.1 <a href="#intro.purpose">Purpose</a></li> |
|---|
| 514 | <li class="tocline1">1.2 <a href="#intro.terminology">Terminology</a></li> |
|---|
| 515 | <li class="tocline1">1.3 <a href="#intro.requirements">Requirements</a></li> |
|---|
| 516 | <li class="tocline1">1.4 <a href="#notation">Syntax Notation</a><ul class="toc"> |
|---|
| 517 | <li class="tocline1">1.4.1 <a href="#core.rules">Core Rules</a></li> |
|---|
| 518 | <li class="tocline1">1.4.2 <a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li> |
|---|
| 519 | </ul> |
|---|
| 520 | </li> |
|---|
| 521 | </ul> |
|---|
| 522 | </li> |
|---|
| 523 | <li class="tocline0">2. <a href="#caching.overview">Cache Operation</a><ul class="toc"> |
|---|
| 524 | <li class="tocline1">2.1 <a href="#response.cacheability">Response Cacheability</a><ul class="toc"> |
|---|
| 525 | <li class="tocline1">2.1.1 <a href="#errors.or.incomplete.response.cache.behavior">Storing Incomplete Responses</a></li> |
|---|
| 526 | </ul> |
|---|
| 527 | </li> |
|---|
| 528 | <li class="tocline1">2.2 <a href="#constructing.responses.from.caches">Constructing Responses from Caches</a></li> |
|---|
| 529 | <li class="tocline1">2.3 <a href="#expiration.model">Freshness Model</a><ul class="toc"> |
|---|
| 530 | <li class="tocline1">2.3.1 <a href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a><ul class="toc"> |
|---|
| 531 | <li class="tocline1">2.3.1.1 <a href="#heuristic.freshness">Using Heuristic Freshness</a></li> |
|---|
| 532 | </ul> |
|---|
| 533 | </li> |
|---|
| 534 | <li class="tocline1">2.3.2 <a href="#age.calculations">Calculating Age</a></li> |
|---|
| 535 | <li class="tocline1">2.3.3 <a href="#serving.stale.responses">Serving Stale Responses</a></li> |
|---|
| 536 | </ul> |
|---|
| 537 | </li> |
|---|
| 538 | <li class="tocline1">2.4 <a href="#validation.model">Validation Model</a></li> |
|---|
| 539 | <li class="tocline1">2.5 <a href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></li> |
|---|
| 540 | <li class="tocline1">2.6 <a href="#caching.negotiated.responses">Caching Negotiated Responses</a></li> |
|---|
| 541 | <li class="tocline1">2.7 <a href="#combining.headers">Combining Responses</a></li> |
|---|
| 542 | </ul> |
|---|
| 543 | </li> |
|---|
| 544 | <li class="tocline0">3. <a href="#header.fields">Header Field Definitions</a><ul class="toc"> |
|---|
| 545 | <li class="tocline1">3.1 <a href="#header.age">Age</a></li> |
|---|
| 546 | <li class="tocline1">3.2 <a href="#header.cache-control">Cache-Control</a><ul class="toc"> |
|---|
| 547 | <li class="tocline1">3.2.1 <a href="#cache-request-directive">Request Cache-Control Directives</a></li> |
|---|
| 548 | <li class="tocline1">3.2.2 <a href="#cache-response-directive">Response Cache-Control Directives</a></li> |
|---|
| 549 | <li class="tocline1">3.2.3 <a href="#cache.control.extensions">Cache Control Extensions</a></li> |
|---|
| 550 | </ul> |
|---|
| 551 | </li> |
|---|
| 552 | <li class="tocline1">3.3 <a href="#header.expires">Expires</a></li> |
|---|
| 553 | <li class="tocline1">3.4 <a href="#header.pragma">Pragma</a></li> |
|---|
| 554 | <li class="tocline1">3.5 <a href="#header.vary">Vary</a></li> |
|---|
| 555 | <li class="tocline1">3.6 <a href="#header.warning">Warning</a></li> |
|---|
| 556 | </ul> |
|---|
| 557 | </li> |
|---|
| 558 | <li class="tocline0">4. <a href="#history.lists">History Lists</a></li> |
|---|
| 559 | <li class="tocline0">5. <a href="#IANA.considerations">IANA Considerations</a><ul class="toc"> |
|---|
| 560 | <li class="tocline1">5.1 <a href="#message.header.registration">Message Header Registration</a></li> |
|---|
| 561 | </ul> |
|---|
| 562 | </li> |
|---|
| 563 | <li class="tocline0">6. <a href="#security.considerations">Security Considerations</a></li> |
|---|
| 564 | <li class="tocline0">7. <a href="#ack">Acknowledgments</a></li> |
|---|
| 565 | <li class="tocline0">8. <a href="#rfc.references">References</a><ul class="toc"> |
|---|
| 566 | <li class="tocline1">8.1 <a href="#rfc.references.1">Normative References</a></li> |
|---|
| 567 | <li class="tocline1">8.2 <a href="#rfc.references.2">Informative References</a></li> |
|---|
| 568 | </ul> |
|---|
| 569 | </li> |
|---|
| 570 | <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li> |
|---|
| 571 | <li class="tocline0">A. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc"> |
|---|
| 572 | <li class="tocline1">A.1 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> |
|---|
| 573 | <li class="tocline1">A.2 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> |
|---|
| 574 | </ul> |
|---|
| 575 | </li> |
|---|
| 576 | <li class="tocline0">B. <a href="#collected.abnf">Collected ABNF</a></li> |
|---|
| 577 | <li class="tocline0">C. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> |
|---|
| 578 | <li class="tocline1">C.1 <a href="#rfc.section.C.1">Since RFC2616</a></li> |
|---|
| 579 | <li class="tocline1">C.2 <a href="#rfc.section.C.2">Since draft-ietf-httpbis-p6-cache-00</a></li> |
|---|
| 580 | <li class="tocline1">C.3 <a href="#rfc.section.C.3">Since draft-ietf-httpbis-p6-cache-01</a></li> |
|---|
| 581 | <li class="tocline1">C.4 <a href="#changes.since.02">Since draft-ietf-httpbis-p6-cache-02</a></li> |
|---|
| 582 | <li class="tocline1">C.5 <a href="#changes.since.03">Since draft-ietf-httpbis-p6-cache-03</a></li> |
|---|
| 583 | <li class="tocline1">C.6 <a href="#changes.since.04">Since draft-ietf-httpbis-p6-cache-04</a></li> |
|---|
| 584 | <li class="tocline1">C.7 <a href="#changes.since.05">Since draft-ietf-httpbis-p6-cache-05</a></li> |
|---|
| 585 | </ul> |
|---|
| 586 | </li> |
|---|
| 587 | <li class="tocline0"><a href="#rfc.index">Index</a></li> |
|---|
| 588 | </ul> |
|---|
| 589 | <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a id="caching" href="#caching">Introduction</a></h1> |
|---|
| 590 | <p id="rfc.section.1.p.1">HTTP is typically used for distributed information systems, where performance can be improved by the use of response caches. |
|---|
| 591 | This document defines aspects of HTTP/1.1 related to caching and reusing response messages. |
|---|
| 592 | </p> |
|---|
| 593 | <div id="rfc.iref.c.1"></div> |
|---|
| 594 | <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a> <a id="intro.purpose" href="#intro.purpose">Purpose</a></h2> |
|---|
| 595 | <p id="rfc.section.1.1.p.1">An HTTP <dfn>cache</dfn> is a local store of response messages and the subsystem that controls its message storage, retrieval, and deletion. A cache |
|---|
| 596 | stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent requests. |
|---|
| 597 | Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel. |
|---|
| 598 | </p> |
|---|
| 599 | <p id="rfc.section.1.1.p.2">Caching would be useless if it did not significantly improve performance. The goal of caching in HTTP/1.1 is to reuse a prior |
|---|
| 600 | response message to satisfy a current request. In some cases, a stored response can be reused without the need for a network |
|---|
| 601 | request, reducing latency and network round-trips; a "freshness" mechanism is used for this purpose (see <a href="#expiration.model" title="Freshness Model">Section 2.3</a>). Even when a new request is required, it is often possible to reuse all or parts of the payload of a prior response to satisfy |
|---|
| 602 | the request, thereby reducing network bandwidth usage; a "validation" mechanism is used for this purpose (see <a href="#validation.model" title="Validation Model">Section 2.4</a>). |
|---|
| 603 | </p> |
|---|
| 604 | <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> |
|---|
| 605 | <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, HTTP caching.</p> |
|---|
| 606 | <p id="rfc.section.1.2.p.2"> <span id="rfc.iref.c.2"></span> <dfn>cacheable</dfn> |
|---|
| 607 | </p> |
|---|
| 608 | <dl class="empty"> |
|---|
| 609 | <dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests. |
|---|
| 610 | Even when a response is cacheable, there may be additional constraints on whether a cache can use the cached copy to satisfy |
|---|
| 611 | a particular request. |
|---|
| 612 | </dd> |
|---|
| 613 | </dl> |
|---|
| 614 | <p id="rfc.section.1.2.p.3"> <span id="rfc.iref.e.1"></span> <dfn>explicit expiration time</dfn> |
|---|
| 615 | </p> |
|---|
| 616 | <dl class="empty"> |
|---|
| 617 | <dd>The time at which the origin server intends that an entity should no longer be returned by a cache without further validation.</dd> |
|---|
| 618 | </dl> |
|---|
| 619 | <p id="rfc.section.1.2.p.4"> <span id="rfc.iref.h.1"></span> <dfn>heuristic expiration time</dfn> |
|---|
| 620 | </p> |
|---|
| 621 | <dl class="empty"> |
|---|
| 622 | <dd>An expiration time assigned by a cache when no explicit expiration time is available.</dd> |
|---|
| 623 | </dl> |
|---|
| 624 | <p id="rfc.section.1.2.p.5"> <span id="rfc.iref.a.1"></span> <dfn>age</dfn> |
|---|
| 625 | </p> |
|---|
| 626 | <dl class="empty"> |
|---|
| 627 | <dd>The age of a response is the time since it was sent by, or successfully validated with, the origin server.</dd> |
|---|
| 628 | </dl> |
|---|
| 629 | <p id="rfc.section.1.2.p.6"> <span id="rfc.iref.f.1"></span> <dfn>first-hand</dfn> |
|---|
| 630 | </p> |
|---|
| 631 | <dl class="empty"> |
|---|
| 632 | <dd>A response is first-hand if the freshness model is not in use; i.e., its age is 0.</dd> |
|---|
| 633 | </dl> |
|---|
| 634 | <p id="rfc.section.1.2.p.7"> <span id="rfc.iref.f.2"></span> <dfn>freshness lifetime</dfn> |
|---|
| 635 | </p> |
|---|
| 636 | <dl class="empty"> |
|---|
| 637 | <dd>The length of time between the generation of a response and its expiration time.</dd> |
|---|
| 638 | </dl> |
|---|
| 639 | <p id="rfc.section.1.2.p.8"> <span id="rfc.iref.f.3"></span> <dfn>fresh</dfn> |
|---|
| 640 | </p> |
|---|
| 641 | <dl class="empty"> |
|---|
| 642 | <dd>A response is fresh if its age has not yet exceeded its freshness lifetime.</dd> |
|---|
| 643 | </dl> |
|---|
| 644 | <p id="rfc.section.1.2.p.9"> <span id="rfc.iref.s.1"></span> <dfn>stale</dfn> |
|---|
| 645 | </p> |
|---|
| 646 | <dl class="empty"> |
|---|
| 647 | <dd>A response is stale if its age has passed its freshness lifetime.</dd> |
|---|
| 648 | </dl> |
|---|
| 649 | <p id="rfc.section.1.2.p.10"> <span id="rfc.iref.v.1"></span> <dfn>validator</dfn> |
|---|
| 650 | </p> |
|---|
| 651 | <dl class="empty"> |
|---|
| 652 | <dd>A protocol element (e.g., an entity tag or a Last-Modified time) that is used to find out whether a stored response is an |
|---|
| 653 | equivalent copy of an entity. |
|---|
| 654 | </dd> |
|---|
| 655 | </dl> |
|---|
| 656 | <p id="rfc.section.1.2.p.11"> <span id="rfc.iref.v.2"></span> <dfn>shared cache</dfn> |
|---|
| 657 | </p> |
|---|
| 658 | <dl class="empty"> |
|---|
| 659 | <dd>A cache that is accessible to more than one user. A non-shared cache is dedicated to a single user.</dd> |
|---|
| 660 | </dl> |
|---|
| 661 | <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a> <a id="intro.requirements" href="#intro.requirements">Requirements</a></h2> |
|---|
| 662 | <p id="rfc.section.1.3.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" |
|---|
| 663 | 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>. |
|---|
| 664 | </p> |
|---|
| 665 | <p id="rfc.section.1.3.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." |
|---|
| 666 | </p> |
|---|
| 667 | <h2 id="rfc.section.1.4"><a href="#rfc.section.1.4">1.4</a> <a id="notation" href="#notation">Syntax Notation</a></h2> |
|---|
| 668 | <p id="rfc.section.1.4.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</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>. The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG |
|---|
| 669 | (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character), |
|---|
| 670 | and WSP (whitespace). |
|---|
| 671 | </p> |
|---|
| 672 | <h3 id="rfc.section.1.4.1"><a href="#rfc.section.1.4.1">1.4.1</a> <a id="core.rules" href="#core.rules">Core Rules</a></h3> |
|---|
| 673 | <p id="rfc.section.1.4.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</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>: |
|---|
| 674 | </p> |
|---|
| 675 | <div id="rfc.figure.u.1"></div><pre class="inline"> <a href="#core.rules" class="smpl">quoted-string</a> = <quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>> |
|---|
| 676 | <a href="#core.rules" class="smpl">token</a> = <token, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>> |
|---|
| 677 | <a href="#core.rules" class="smpl">OWS</a> = <OWS, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>> |
|---|
| 678 | </pre><h3 id="rfc.section.1.4.2"><a href="#rfc.section.1.4.2">1.4.2</a> <a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3> |
|---|
| 679 | <p id="rfc.section.1.4.2.p.1">The ABNF rules below are defined in other parts:</p> |
|---|
| 680 | <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">field-name</a> = <field-name, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a>> |
|---|
| 681 | <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.2.1</a>> |
|---|
| 682 | <a href="#abnf.dependencies" class="smpl">port</a> = <port, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.1</a>> |
|---|
| 683 | <a href="#abnf.dependencies" class="smpl">pseudonym</a> = <pseudonym, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a>> |
|---|
| 684 | <a href="#abnf.dependencies" class="smpl">uri-host</a> = <uri-host, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.1</a>> |
|---|
| 685 | </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="caching.overview" href="#caching.overview">Cache Operation</a></h1> |
|---|
| 686 | <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="response.cacheability" href="#response.cacheability">Response Cacheability</a></h2> |
|---|
| 687 | <p id="rfc.section.2.1.p.1">A cache <em class="bcp14">MAY</em> store a response to any request, provided that: |
|---|
| 688 | </p> |
|---|
| 689 | <ul> |
|---|
| 690 | <li>the "no-store" cache directive (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.1" title="Cache-Control">Section 3.2</a>) does not appear in request or response headers. |
|---|
| 691 | </li> |
|---|
| 692 | <li>the cache understands partial responses, if the response is partial or incomplete (see <a href="#errors.or.incomplete.response.cache.behavior" title="Storing Incomplete Responses">Section 2.1.1</a>). |
|---|
| 693 | </li> |
|---|
| 694 | </ul> |
|---|
| 695 | <p id="rfc.section.2.1.p.2">Note that in normal operation, most caches will not store a response that has neither a cache validator nor an explicit expiration |
|---|
| 696 | time, as such responses are not usually useful to store. However, caches are not prohibited from storing such responses. |
|---|
| 697 | </p> |
|---|
| 698 | <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a> <a id="errors.or.incomplete.response.cache.behavior" href="#errors.or.incomplete.response.cache.behavior">Storing Incomplete Responses</a></h3> |
|---|
| 699 | <p id="rfc.section.2.1.1.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 <span class="comment">[rfc.comment.1: Indeed? Is this new? --JRE]</span>. However, the cache <em class="bcp14">MUST</em> treat this as a partial response <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. Partial responses <em class="bcp14">MAY</em> be combined as described in <a href="p5-range.html#combining.byte.ranges" title="Combining 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. |
|---|
| 700 | </p> |
|---|
| 701 | <p id="rfc.section.2.1.1.p.2">A cache that does not support the Range and Content-Range headers <em class="bcp14">MUST NOT</em> store incomplete or partial responses. |
|---|
| 702 | </p> |
|---|
| 703 | <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a> <a id="constructing.responses.from.caches" href="#constructing.responses.from.caches">Constructing Responses from Caches</a></h2> |
|---|
| 704 | <p id="rfc.section.2.2.p.1">For a given request, a non-shared cache <em class="bcp14">MAY</em> return a stored response, provided that: |
|---|
| 705 | </p> |
|---|
| 706 | <ul> |
|---|
| 707 | <li>the presented request-URI and that of the stored response match (see <span class="comment">[rfc.comment.2: TBD]</span>), and |
|---|
| 708 | </li> |
|---|
| 709 | <li>selecting headers nominated by the stored response (if any) match (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section 2.6</a>), and |
|---|
| 710 | </li> |
|---|
| 711 | <li>the stored response is either fresh (see <a href="#expiration.model" title="Freshness Model">Section 2.3</a>) or allowed to be served stale (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section 2.3.3</a>), and |
|---|
| 712 | </li> |
|---|
| 713 | <li>the presented request and stored response are free from directives that would prevent it (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section 3.2</a> and <a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section 3.4</a>). |
|---|
| 714 | </li> |
|---|
| 715 | </ul> |
|---|
| 716 | <p id="rfc.section.2.2.p.2"> <span class="comment">[rfc.comment.3: ISSUE: This doesn't specify whether the request method is part of the cache key.]</span> |
|---|
| 717 | </p> |
|---|
| 718 | <p id="rfc.section.2.2.p.3">A shared cache <em class="bcp14">MAY</em> return a stored response, provided that: |
|---|
| 719 | </p> |
|---|
| 720 | <ul> |
|---|
| 721 | <li>the criteria for non-shared caches above are met (including directives for shared caches; see <a href="#header.cache-control" id="rfc.xref.header.cache-control.3" title="Cache-Control">Section 3.2</a>), and |
|---|
| 722 | </li> |
|---|
| 723 | <li>the stored response was not associated with an authenticated request (see <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>), unless explicitly allowed (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.4" title="Cache-Control">Section 3.2</a>). |
|---|
| 724 | </li> |
|---|
| 725 | </ul> |
|---|
| 726 | <p id="rfc.section.2.2.p.4">All responses satisfied from cache <em class="bcp14">MUST</em> include an appropriate Age header field (<a href="#header.age" id="rfc.xref.header.age.1" title="Age">Section 3.1</a>). |
|---|
| 727 | </p> |
|---|
| 728 | <p id="rfc.section.2.2.p.5">All request methods other than GET and HEAD <em class="bcp14">MUST</em> be written through the cache to the origin server. Note that such requests might invalidate already stored responses; see <a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 2.5</a>. |
|---|
| 729 | </p> |
|---|
| 730 | <p id="rfc.section.2.2.p.6">Caches <em class="bcp14">SHOULD</em> use the most recent response (as determined by the Date header) when more than one applicable response is stored. They <em class="bcp14">MAY</em> also send a request with "Cache-Control: max-age=0" or "Cache-Control: no-cache" to disambiguate which response to use. |
|---|
| 731 | </p> |
|---|
| 732 | <p id="rfc.section.2.2.p.7">In the process of determining whether a stored response is fresh or not, a cache <em class="bcp14">MAY</em> validate that response (see <a href="#validation.model" title="Validation Model">Section 2.4</a>). |
|---|
| 733 | </p> |
|---|
| 734 | <p id="rfc.section.2.2.p.8"> <span class="comment">[rfc.comment.4: TODO: end-to-end and hop-by-hop headers, non-modifiable headers removed; re-spec in p1]</span> |
|---|
| 735 | </p> |
|---|
| 736 | <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a> <a id="expiration.model" href="#expiration.model">Freshness Model</a></h2> |
|---|
| 737 | <p id="rfc.section.2.3.p.1">HTTP caching works best when caches can entirely avoid making requests to the origin server. When a response is "fresh" in |
|---|
| 738 | the cache, it can be used to satisfy subsequent requests without contacting the origin server. This is also referred to as |
|---|
| 739 | "expiration."<span class="comment">[rfc.comment.5: What exactly is called 'expiration'? --JRE]</span>. |
|---|
| 740 | </p> |
|---|
| 741 | <p id="rfc.section.2.3.p.2">Expiration applies only to responses taken from a cache and not to first-hand responses. It cannot be used to force a user |
|---|
| 742 | agent to refresh its display or reload a resource; its semantics apply only to caches. See <a href="#history.lists" title="History Lists">Section 4</a> for an explanation of the difference between caches and history mechanisms. |
|---|
| 743 | </p> |
|---|
| 744 | <p id="rfc.section.2.3.p.3">The primary mechanism for avoiding requests is for an origin server to provide an explicit expiration time in the future, |
|---|
| 745 | using either the Expires header (<a href="#header.expires" id="rfc.xref.header.expires.1" title="Expires">Section 3.3</a>) or the max-age response cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section 3.2.2</a>). Generally, origin servers will assign future explicit expiration times to responses in the belief that the entity is not |
|---|
| 746 | likely to change in a semantically significant way before the expiration time is reached. This normally preserves cache correctness, |
|---|
| 747 | as long as the server's expiration times are carefully chosen. |
|---|
| 748 | </p> |
|---|
| 749 | <p id="rfc.section.2.3.p.4">If an origin server wishes to force a 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, so that caches should validate |
|---|
| 750 | it before using it for subsequent requests. |
|---|
| 751 | </p> |
|---|
| 752 | <p id="rfc.section.2.3.p.5">Since origin servers do not always provide explicit expiration times, HTTP caches may assign heuristic expiration times when |
|---|
| 753 | they are not specified, employing algorithms that use other header values (such as the Last-Modified time) to estimate a plausible |
|---|
| 754 | expiration time. The HTTP/1.1 specification does not provide specific algorithms, but does impose worst-case constraints on |
|---|
| 755 | their results. |
|---|
| 756 | </p> |
|---|
| 757 | <p id="rfc.section.2.3.p.6">The calculation to determine if a response has expired is:</p> |
|---|
| 758 | <div id="rfc.figure.u.3"></div> <pre class="text"> response_is_fresh = (freshness_lifetime > current_age) |
|---|
| 759 | </pre> <p id="rfc.section.2.3.p.8">The freshness_lifetime is defined in <a href="#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a>; the current_age is defined in <a href="#age.calculations" title="Calculating Age">Section 2.3.2</a>. |
|---|
| 760 | </p> |
|---|
| 761 | <p id="rfc.section.2.3.p.9">Additionally, clients may need to influence freshness calculation. They can do this using several request cache directives, |
|---|
| 762 | with the effect of either increasing or loosening constraints on freshness. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section 3.2.1</a>. |
|---|
| 763 | </p> |
|---|
| 764 | <p id="rfc.section.2.3.p.10"> <span class="comment">[rfc.comment.6: ISSUE: there are not requirements directly applying to cache-request-directives and freshness.]</span> |
|---|
| 765 | </p> |
|---|
| 766 | <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a> <a id="calculating.freshness.lifetime" href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a></h3> |
|---|
| 767 | <p id="rfc.section.2.3.1.p.1">A cache can calculate the freshness lifetime (denoted as freshness_lifetime) of a response by using the first match of: </p> |
|---|
| 768 | <ul> |
|---|
| 769 | <li>If the cache is shared and the s-maxage response cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section 3.2.2</a>) is present, use its value, or |
|---|
| 770 | </li> |
|---|
| 771 | <li>If the max-age response cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section 3.2.2</a>) is present, use its value, or |
|---|
| 772 | </li> |
|---|
| 773 | <li>If the Expires response header (<a href="#header.expires" id="rfc.xref.header.expires.2" title="Expires">Section 3.3</a>) is present, use its value minus the value of the Date response header, or |
|---|
| 774 | </li> |
|---|
| 775 | <li>Otherwise, no explicit expiration time is present in the response, but a heuristic may be used; see <a href="#heuristic.freshness" title="Using Heuristic Freshness">Section 2.3.1.1</a>. |
|---|
| 776 | </li> |
|---|
| 777 | </ul> |
|---|
| 778 | <p id="rfc.section.2.3.1.p.2">Note that this calculation is not vulnerable to clock skew, since all of the information comes from the origin server.</p> |
|---|
| 779 | <h4 id="rfc.section.2.3.1.1"><a href="#rfc.section.2.3.1.1">2.3.1.1</a> <a id="heuristic.freshness" href="#heuristic.freshness">Using Heuristic Freshness</a></h4> |
|---|
| 780 | <p id="rfc.section.2.3.1.1.p.1">If no explicit expiration time is present in a stored response that has a status code of 200, 203, 206, 300, 301 or 410, a |
|---|
| 781 | heuristic expiration time <em class="bcp14">MAY</em> be calculated. Heuristics <em class="bcp14">MUST NOT</em> be used for other response status codes. |
|---|
| 782 | </p> |
|---|
| 783 | <p id="rfc.section.2.3.1.1.p.2">When a heuristic is used to calculate freshness lifetime, the cache <em class="bcp14">SHOULD</em> attach a Warning header with a 113 warn-code to the response if its current_age is more than 24 hours and such a warning is |
|---|
| 784 | not already present. |
|---|
| 785 | </p> |
|---|
| 786 | <p id="rfc.section.2.3.1.1.p.3">Also, if the response has a Last-Modified header (<a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 6.6</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>), 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%. |
|---|
| 787 | </p> |
|---|
| 788 | <p id="rfc.section.2.3.1.1.p.4"> <span class="comment">[rfc.comment.7: REVIEW: took away HTTP/1.0 query string heuristic uncacheability.]</span> |
|---|
| 789 | </p> |
|---|
| 790 | <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a> <a id="age.calculations" href="#age.calculations">Calculating Age</a></h3> |
|---|
| 791 | <p id="rfc.section.2.3.2.p.1">HTTP/1.1 uses the Age response-header to convey the estimated age of the response message when obtained from a cache. The |
|---|
| 792 | Age field value is the cache's estimate of the amount of time since the response was generated or validated by the origin |
|---|
| 793 | server. In essence, the Age value is the sum of the time that the response has been resident in each of the caches along the |
|---|
| 794 | path from the origin server, plus the amount of time it has been in transit along network paths. |
|---|
| 795 | </p> |
|---|
| 796 | <p id="rfc.section.2.3.2.p.2">When a response is generated from a stored response, the cache <em class="bcp14">MUST</em> include a single Age header field in the response with a value equal to the stored response's current_age, calculated using |
|---|
| 797 | the algorithm described in this section. |
|---|
| 798 | </p> |
|---|
| 799 | <p id="rfc.section.2.3.2.p.3">The term "age_value" denotes the value of the Age header, in a form appropriate for arithmetic operations.</p> |
|---|
| 800 | <p id="rfc.section.2.3.2.p.4">HTTP/1.1 requires origin servers to send a Date header, if possible, with every response, giving the time at which the response |
|---|
| 801 | was generated (see <a href="p1-messaging.html#header.date" title="Date">Section 8.3</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The term "date_value" denotes the value of the Date header, in a form appropriate for arithmetic operations. |
|---|
| 802 | </p> |
|---|
| 803 | <p id="rfc.section.2.3.2.p.5">The term "now" means "the current value of the clock at the host performing the calculation." Hosts that use HTTP, but especially |
|---|
| 804 | 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. |
|---|
| 805 | </p> |
|---|
| 806 | <p id="rfc.section.2.3.2.p.6">A response's age can be calculated in two entirely independent ways: </p> |
|---|
| 807 | <ol> |
|---|
| 808 | <li>now minus date_value, if the local clock is reasonably well synchronized to the origin server's clock. If the result is negative, |
|---|
| 809 | the result is replaced by zero. |
|---|
| 810 | </li> |
|---|
| 811 | <li>age_value, if all of the caches along the response path implement HTTP/1.1.</li> |
|---|
| 812 | </ol> |
|---|
| 813 | <p id="rfc.section.2.3.2.p.7">These are combined as</p> |
|---|
| 814 | <div id="rfc.figure.u.4"></div> <pre class="text"> corrected_received_age = max(now - date_value, age_value) |
|---|
| 815 | </pre> <p id="rfc.section.2.3.2.p.9">When an Age 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. |
|---|
| 816 | </p> |
|---|
| 817 | <div id="rfc.figure.u.5"></div> <pre class="text"> corrected_initial_age = corrected_received_age |
|---|
| 818 | + (now - request_time) |
|---|
| 819 | </pre> <p id="rfc.section.2.3.2.p.11">where "request_time" is the time (according to the local clock) when the request that elicited this response was sent.</p> |
|---|
| 820 | <p id="rfc.section.2.3.2.p.12">The current_age of a stored response can then be calculated by adding the amount of time (in seconds) since the stored response |
|---|
| 821 | was last validated by the origin server to the corrected_initial_age. |
|---|
| 822 | </p> |
|---|
| 823 | <p id="rfc.section.2.3.2.p.13">In summary:</p> |
|---|
| 824 | <div id="rfc.figure.u.6"></div> <pre class="text"> /* |
|---|
| 825 | * age_value |
|---|
| 826 | * is the value of Age: header received by the cache with |
|---|
| 827 | * this response. |
|---|
| 828 | * date_value |
|---|
| 829 | * is the value of the origin server's Date: header |
|---|
| 830 | * request_time |
|---|
| 831 | * is the (local) time when the cache made the request |
|---|
| 832 | * that resulted in this stored response |
|---|
| 833 | * response_time |
|---|
| 834 | * is the (local) time when the cache received the |
|---|
| 835 | * response |
|---|
| 836 | * now |
|---|
| 837 | * is the current (local) time |
|---|
| 838 | */ |
|---|
| 839 | |
|---|
| 840 | apparent_age = max(0, response_time - date_value); |
|---|
| 841 | corrected_received_age = max(apparent_age, age_value); |
|---|
| 842 | response_delay = response_time - request_time; |
|---|
| 843 | corrected_initial_age = corrected_received_age + response_delay; |
|---|
| 844 | resident_time = now - response_time; |
|---|
| 845 | current_age = corrected_initial_age + resident_time; |
|---|
| 846 | </pre> <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a> <a id="serving.stale.responses" href="#serving.stale.responses">Serving Stale Responses</a></h3> |
|---|
| 847 | <p id="rfc.section.2.3.3.p.1">A "stale" response is one that either has explicit expiry information, or is allowed to have heuristic expiry calculated, |
|---|
| 848 | but is not fresh according to the calculations in <a href="#expiration.model" title="Freshness Model">Section 2.3</a>. |
|---|
| 849 | </p> |
|---|
| 850 | <p id="rfc.section.2.3.3.p.2">Caches <em class="bcp14">MUST NOT</em> return a stale response if it is prohibited by an explicit in-protocol directive (e.g., by a "no-store" or "no-cache" cache |
|---|
| 851 | directive, a "must-revalidate" cache-response-directive, or an applicable "s-maxage" or "proxy-revalidate" cache-response-directive; |
|---|
| 852 | see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section 3.2.2</a>). |
|---|
| 853 | </p> |
|---|
| 854 | <p id="rfc.section.2.3.3.p.3">Caches <em class="bcp14">MAY</em> return a stale response if disconnected or explicitly allowed (e.g., the max-stale request directive; see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section 3.2.1</a>). |
|---|
| 855 | </p> |
|---|
| 856 | <p id="rfc.section.2.3.3.p.4">Otherwise, caches <em class="bcp14">SHOULD NOT</em> return stale responses. |
|---|
| 857 | </p> |
|---|
| 858 | <p id="rfc.section.2.3.3.p.5">Stale responses <em class="bcp14">SHOULD</em> have a Warning header with the 110 warn-code (see <a href="#header.warning" id="rfc.xref.header.warning.1" title="Warning">Section 3.6</a>). |
|---|
| 859 | </p> |
|---|
| 860 | <p id="rfc.section.2.3.3.p.6">If a cache receives a first-hand response (either an entire response, or a 304 (Not Modified) response) that it would normally |
|---|
| 861 | forward 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 validate a response simply because that response became stale in transit. |
|---|
| 862 | </p> |
|---|
| 863 | <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a> <a id="validation.model" href="#validation.model">Validation Model</a></h2> |
|---|
| 864 | <p id="rfc.section.2.4.p.1">When a cache has a stale response that it would like to use, it <em class="bcp14">SHOULD</em> first check with the origin server (or possibly an intermediate cache with a fresh response) to see if it is still usable. |
|---|
| 865 | This is called "validating" or "revalidating" the stored response. |
|---|
| 866 | </p> |
|---|
| 867 | <p id="rfc.section.2.4.p.2">HTTP's conditional request mechanism, defined in <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, is used to avoid retransmitting the response payload when the stored response is valid. When a stored response includes |
|---|
| 868 | one or more "cache validators", such as the field values of an ETag or Last-Modified header field, then a validating GET request <em class="bcp14">SHOULD</em> be made conditional to those field values. The server checks the conditional request's validator against the current state |
|---|
| 869 | of the requested resource and, if they match, the server responds with a 304 (Not Modified) status code to indicate that the |
|---|
| 870 | stored response can be refreshed and reused without retransmitting the response payload. If the validator does not match the |
|---|
| 871 | current state of the requested resource, then the server returns a full response, including payload, so that the request can |
|---|
| 872 | be satisfied and the stored response supplanted without the need for an additional network round-trip. |
|---|
| 873 | </p> |
|---|
| 874 | <p id="rfc.section.2.4.p.3">See <a href="#combining.headers" title="Combining Responses">Section 2.7</a> regarding combining cached headers with those in a 304 response. |
|---|
| 875 | </p> |
|---|
| 876 | <p id="rfc.section.2.4.p.4">If a cache receives a 5xx response while attempting to validate a response, 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 stored response includes the "must-revalidate" cache directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section 3.2.2</a>). |
|---|
| 877 | </p> |
|---|
| 878 | <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a> <a id="invalidation.after.updates.or.deletions" href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></h2> |
|---|
| 879 | <p id="rfc.section.2.5.p.1">Because unsafe methods <a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a> have the potential for changing state on the origin server, intervening caches have the opportunity to use them to keep their |
|---|
| 880 | contents up-to-date. |
|---|
| 881 | </p> |
|---|
| 882 | <p id="rfc.section.2.5.p.2">The following HTTP methods <em class="bcp14">MUST</em> cause a cache to invalidate the Request-URI as well as the Location and Content-Location headers (if present): |
|---|
| 883 | </p> |
|---|
| 884 | <ul> |
|---|
| 885 | <li>PUT</li> |
|---|
| 886 | <li>DELETE</li> |
|---|
| 887 | <li>POST</li> |
|---|
| 888 | </ul> |
|---|
| 889 | <p id="rfc.section.2.5.p.3">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 |
|---|
| 890 | attacks. |
|---|
| 891 | </p> |
|---|
| 892 | <p id="rfc.section.2.5.p.4"> <span class="comment">[rfc.comment.8: TODO: "host part" needs to be specified better.]</span> |
|---|
| 893 | </p> |
|---|
| 894 | <p id="rfc.section.2.5.p.5">A cache that passes through requests for methods it does not understand <em class="bcp14">SHOULD</em> invalidate the Request-URI. |
|---|
| 895 | </p> |
|---|
| 896 | <p id="rfc.section.2.5.p.6">Here, "invalidate" means that the cache will either remove all stored responses related to the Request-URI, or will mark these |
|---|
| 897 | as "invalid" and in need of a mandatory validation before they can be returned in response to a subsequent request. |
|---|
| 898 | </p> |
|---|
| 899 | <p id="rfc.section.2.5.p.7">Note that this does not guarantee that all appropriate responses are invalidated. For example, the request that caused the |
|---|
| 900 | change at the origin server might not have gone through the cache where a response is stored. |
|---|
| 901 | </p> |
|---|
| 902 | <p id="rfc.section.2.5.p.8"> <span class="comment">[rfc.comment.9: TODO: specify that only successful (2xx, 3xx?) responses invalidate.]</span> |
|---|
| 903 | </p> |
|---|
| 904 | <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> |
|---|
| 905 | <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.1"><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 (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section 3.5</a>) in a response, alters the conditions and procedure by which a cache can use the response for subsequent requests. |
|---|
| 906 | </p> |
|---|
| 907 | <p id="rfc.section.2.6.p.2">When the cache receives a subsequent request which may be satisfied by a stored responses that include a Vary header field, |
|---|
| 908 | it <em class="bcp14">MUST NOT</em> use it to satisfy the request unless all of the selecting request-headers present in the new request match the corresponding |
|---|
| 909 | stored request-headers from the original request. |
|---|
| 910 | </p> |
|---|
| 911 | <p id="rfc.section.2.6.p.3">The selecting request-headers from two requests are defined to match if and only if the selecting request-headers in the first |
|---|
| 912 | request can be transformed to the selecting request-headers in the second request by adding or removing linear white space <span class="comment">[rfc.comment.10: [ref]]</span> at places where this is allowed by the corresponding ABNF, and/or combining multiple message-header fields with the same field |
|---|
| 913 | 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.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. |
|---|
| 914 | </p> |
|---|
| 915 | <p id="rfc.section.2.6.p.4">A Vary header field-value of "*" always fails to match, and subsequent requests on that resource can only be properly interpreted |
|---|
| 916 | by the origin server. |
|---|
| 917 | </p> |
|---|
| 918 | <p id="rfc.section.2.6.p.5">If the selecting request header fields for the stored response do not match the selecting request header fields of the new |
|---|
| 919 | request, then the cache <em class="bcp14">MUST NOT</em> use the stored response to satisfy the request unless it first relays the new request to the origin server in a conditional |
|---|
| 920 | request and the server responds with 304 (Not Modified), including an entity tag or Content-Location that indicates the entity |
|---|
| 921 | to be used. |
|---|
| 922 | </p> |
|---|
| 923 | <p id="rfc.section.2.6.p.6">If one or more applicable stored response has an entity tag, the forwarded request <em class="bcp14">SHOULD</em> be conditional and include all of these entity tags in an If-None-Match header field. This conveys to the server the set of |
|---|
| 924 | entities currently stored by the cache, so that if any one of these entities matches the requested entity, the server can |
|---|
| 925 | use the ETag header field in its 304 (Not Modified) response to tell the cache which stored response is appropriate. If the |
|---|
| 926 | entity-tag of the new response matches that of an existing stored resopnse, the new response <em class="bcp14">SHOULD</em> be used to update its header fields, and the result <em class="bcp14">MUST</em> be returned to the client. |
|---|
| 927 | </p> |
|---|
| 928 | <p id="rfc.section.2.6.p.7">If any of the existing stored responses 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 stored |
|---|
| 929 | response. |
|---|
| 930 | </p> |
|---|
| 931 | <p id="rfc.section.2.6.p.8">If a cache receives a successful response whose Content-Location field matches that of an existing stored response for the |
|---|
| 932 | same Request-URI, whose entity-tag differs from that of the existing stored response, and whose Date is more recent than that |
|---|
| 933 | of the existing response, the existing response <em class="bcp14">SHOULD NOT</em> be returned in response to future requests and <em class="bcp14">SHOULD</em> be deleted from the cache. |
|---|
| 934 | </p> |
|---|
| 935 | <p id="rfc.section.2.6.p.9"> <span class="comment">[rfc.comment.11: TODO: this still needs work.]</span> |
|---|
| 936 | </p> |
|---|
| 937 | <h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a> <a id="combining.headers" href="#combining.headers">Combining Responses</a></h2> |
|---|
| 938 | <p id="rfc.section.2.7.p.1">When a cache receives a 304 (Not Modified) response or a 206 (Partial Content) response, it needs to update the stored response |
|---|
| 939 | with the new one, so that the updated response can be sent to the client. |
|---|
| 940 | </p> |
|---|
| 941 | <p id="rfc.section.2.7.p.2">If the status code is 304 (Not Modified), the cache <em class="bcp14">SHOULD</em> use the stored entity-body as the updated entity-body. If the status code is 206 (Partial Content) and the ETag or Last-Modified |
|---|
| 942 | headers match exactly, the cache <em class="bcp14">MAY</em> combine the stored entity-body in the stored response with the updated entity-body received in the response and use the result |
|---|
| 943 | as the updated entity-body (see <a href="p5-range.html#combining.byte.ranges" title="Combining Ranges">Section 4</a> of <a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>). |
|---|
| 944 | </p> |
|---|
| 945 | <p id="rfc.section.2.7.p.3">The stored response headers are used for the updated response, except that </p> |
|---|
| 946 | <ul> |
|---|
| 947 | <li>any stored Warning headers with warn-code 1xx (see <a href="#header.warning" id="rfc.xref.header.warning.2" title="Warning">Section 3.6</a>) <em class="bcp14">MUST</em> be deleted from the stored response and the forwarded response. |
|---|
| 948 | </li> |
|---|
| 949 | <li>any stored Warning headers with warn-code 2xx <em class="bcp14">MUST</em> be retained in the stored response and the forwarded response. |
|---|
| 950 | </li> |
|---|
| 951 | <li>any headers provided in the 304 or 206 response <em class="bcp14">MUST</em> replace the corresponding headers from the stored response. |
|---|
| 952 | </li> |
|---|
| 953 | </ul> |
|---|
| 954 | <p id="rfc.section.2.7.p.4">A cache <em class="bcp14">MUST</em> also replace stored headers with corresponding headers received in the incoming response, except for Warning headers as described |
|---|
| 955 | immediately above. If a header field-name in the incoming response matches more than one header in the stored response, all |
|---|
| 956 | such old headers <em class="bcp14">MUST</em> be replaced. it <em class="bcp14">MAY</em> store the combined entity-body. |
|---|
| 957 | </p> |
|---|
| 958 | <p id="rfc.section.2.7.p.5"><span class="comment">[rfc.comment.12: ISSUE: discuss how to handle HEAD updates]</span></p> |
|---|
| 959 | <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1> |
|---|
| 960 | <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to caching.</p> |
|---|
| 961 | <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 |
|---|
| 962 | receives the entity. |
|---|
| 963 | </p> |
|---|
| 964 | <div id="rfc.iref.a.2"></div> |
|---|
| 965 | <div id="rfc.iref.h.2"></div> |
|---|
| 966 | <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> |
|---|
| 967 | <p id="rfc.section.3.1.p.1">The response-header field "Age" conveys the sender's estimate of the amount of time since the response (or its validation) |
|---|
| 968 | was generated at the origin server. Age values are calculated as specified in <a href="#age.calculations" title="Calculating Age">Section 2.3.2</a>. |
|---|
| 969 | </p> |
|---|
| 970 | <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span> <a href="#header.age" class="smpl">Age</a> = "Age" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.age" class="smpl">Age-v</a> |
|---|
| 971 | <a href="#header.age" class="smpl">Age-v</a> = <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> |
|---|
| 972 | </pre><div id="rule.delta-seconds"> |
|---|
| 973 | <p id="rfc.section.3.1.p.3"> Age field-values are non-negative decimal integers, representing time in seconds.</p> |
|---|
| 974 | </div> |
|---|
| 975 | <div id="rfc.figure.u.8"></div> <pre class="inline"><span id="rfc.iref.g.3"></span> <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> = 1*<a href="#notation" class="smpl">DIGIT</a> |
|---|
| 976 | </pre> <p id="rfc.section.3.1.p.5">If a cache receives a value larger than the largest positive integer it can represent, or if any of its age calculations overflows, |
|---|
| 977 | it <em class="bcp14">MUST</em> transmit an Age header with a field-value of 2147483648 (2<sup>31</sup>). Caches <em class="bcp14">SHOULD</em> use an arithmetic type of at least 31 bits of range. |
|---|
| 978 | </p> |
|---|
| 979 | <p id="rfc.section.3.1.p.6">The presence of an Age header field in a response implies that a response is not first-hand. However, the converse is not |
|---|
| 980 | true, since HTTP/1.0 caches may not implement the Age header field. |
|---|
| 981 | </p> |
|---|
| 982 | <div id="rfc.iref.c.3"></div> |
|---|
| 983 | <div id="rfc.iref.h.3"></div> |
|---|
| 984 | <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> |
|---|
| 985 | <p id="rfc.section.3.2.p.1">The general-header field "Cache-Control" is used to specify directives that <em class="bcp14">MUST</em> be obeyed by all caches along the request/response chain. The directives specify behavior intended to prevent caches from |
|---|
| 986 | adversely interfering with the request or response. Cache directives are unidirectional in that the presence of a directive |
|---|
| 987 | in a request does not imply that the same directive is to be given in the response. |
|---|
| 988 | </p> |
|---|
| 989 | <dl class="empty"> |
|---|
| 990 | <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.2" title="Pragma">Section 3.4</a>). |
|---|
| 991 | </dd> |
|---|
| 992 | </dl> |
|---|
| 993 | <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 |
|---|
| 994 | might be applicable to all recipients along the request/response chain. It is not possible to target a directive to a specific |
|---|
| 995 | cache. |
|---|
| 996 | </p> |
|---|
| 997 | <div id="rfc.figure.u.9"></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> <a href="#header.cache-control" class="smpl">Cache-Control</a> = "Cache-Control" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.cache-control" class="smpl">Cache-Control-v</a> |
|---|
| 998 | <a href="#header.cache-control" class="smpl">Cache-Control-v</a> = 1#<a href="#header.cache-control" class="smpl">cache-directive</a> |
|---|
| 999 | |
|---|
| 1000 | <a href="#header.cache-control" class="smpl">cache-directive</a> = <a href="#header.cache-control" class="smpl">cache-request-directive</a> |
|---|
| 1001 | / <a href="#header.cache-control" class="smpl">cache-response-directive</a> |
|---|
| 1002 | |
|---|
| 1003 | <a href="#header.cache-control" class="smpl">cache-extension</a> = <a href="#core.rules" class="smpl">token</a> [ "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> ) ] |
|---|
| 1004 | </pre><h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a> <a id="cache-request-directive" href="#cache-request-directive">Request Cache-Control Directives</a></h3> |
|---|
| 1005 | <div id="rfc.figure.u.10"></div> <pre class="inline"><span id="rfc.iref.g.7"></span> <a href="#header.cache-control" class="smpl">cache-request-directive</a> = |
|---|
| 1006 | "no-cache" |
|---|
| 1007 | / "no-store" |
|---|
| 1008 | / "max-age" "=" <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> |
|---|
| 1009 | / "max-stale" [ "=" <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> ] |
|---|
| 1010 | / "min-fresh" "=" <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> |
|---|
| 1011 | / "no-transform" |
|---|
| 1012 | / "only-if-cached" |
|---|
| 1013 | / <a href="#header.cache-control" class="smpl">cache-extension</a> |
|---|
| 1014 | </pre> <p id="rfc.section.3.2.1.p.2"> <span id="rfc.iref.c.4"></span> <span id="rfc.iref.n.1"></span> no-cache |
|---|
| 1015 | </p> |
|---|
| 1016 | <dl class="empty"> |
|---|
| 1017 | <dd>The no-cache request directive indicates that a stored response <em class="bcp14">MUST NOT</em> be used to satisfy the request without successful validation on the origin server. |
|---|
| 1018 | </dd> |
|---|
| 1019 | </dl> |
|---|
| 1020 | <p id="rfc.section.3.2.1.p.3"> <span id="rfc.iref.c.5"></span> <span id="rfc.iref.n.2"></span> no-store |
|---|
| 1021 | </p> |
|---|
| 1022 | <dl class="empty"> |
|---|
| 1023 | <dd>The no-store request directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either this request or any response to it. This directive applies to both non-shared and shared caches. |
|---|
| 1024 | "<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. |
|---|
| 1025 | </dd> |
|---|
| 1026 | <dd>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches |
|---|
| 1027 | might not recognize or obey this directive, and communications networks may be vulnerable to eavesdropping. |
|---|
| 1028 | </dd> |
|---|
| 1029 | </dl> |
|---|
| 1030 | <p id="rfc.section.3.2.1.p.4"> <span id="rfc.iref.c.6"></span> <span id="rfc.iref.m.1"></span> max-age |
|---|
| 1031 | </p> |
|---|
| 1032 | <dl class="empty"> |
|---|
| 1033 | <dd>The max-age request directive indicates that the client is willing to accept a response whose age is no greater than the specified |
|---|
| 1034 | time in seconds. Unless max-stale directive is also included, the client is not willing to accept a stale response. |
|---|
| 1035 | </dd> |
|---|
| 1036 | </dl> |
|---|
| 1037 | <p id="rfc.section.3.2.1.p.5"> <span id="rfc.iref.c.7"></span> <span id="rfc.iref.m.2"></span> max-stale |
|---|
| 1038 | </p> |
|---|
| 1039 | <dl class="empty"> |
|---|
| 1040 | <dd>The max-stale request directive indicates that the client is willing to accept a response that has exceeded its expiration |
|---|
| 1041 | time. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its expiration time |
|---|
| 1042 | by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing to accept |
|---|
| 1043 | a stale response of any age. |
|---|
| 1044 | </dd> |
|---|
| 1045 | </dl> |
|---|
| 1046 | <p id="rfc.section.3.2.1.p.6"> <span id="rfc.iref.c.8"></span> <span id="rfc.iref.m.3"></span> min-fresh |
|---|
| 1047 | </p> |
|---|
| 1048 | <dl class="empty"> |
|---|
| 1049 | <dd>The min-fresh request directive indicates that the client is willing to accept a response whose freshness lifetime is no less |
|---|
| 1050 | than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh for |
|---|
| 1051 | at least the specified number of seconds. |
|---|
| 1052 | </dd> |
|---|
| 1053 | </dl> |
|---|
| 1054 | <p id="rfc.section.3.2.1.p.7"> <span id="rfc.iref.c.9"></span> <span id="rfc.iref.n.3"></span> no-transform |
|---|
| 1055 | </p> |
|---|
| 1056 | <dl class="empty"> |
|---|
| 1057 | <dd>The no-transform request directive indicates that an intermediate cache or proxy <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type request headers, nor the request entity-body. |
|---|
| 1058 | </dd> |
|---|
| 1059 | </dl> |
|---|
| 1060 | <p id="rfc.section.3.2.1.p.8"> <span id="rfc.iref.c.10"></span> <span id="rfc.iref.o.1"></span> only-if-cached |
|---|
| 1061 | </p> |
|---|
| 1062 | <dl class="empty"> |
|---|
| 1063 | <dd>The only-if-cached request directive indicates that the client only wishes to return a stored response. If it receives this |
|---|
| 1064 | directive, a cache <em class="bcp14">SHOULD</em> either respond using a stored response that is consistent with the other constraints of the request, or respond with a 504 |
|---|
| 1065 | (Gateway Timeout) status. If a group of caches is being operated as a unified system with good internal connectivity, such |
|---|
| 1066 | a request <em class="bcp14">MAY</em> be forwarded within that group of caches. |
|---|
| 1067 | </dd> |
|---|
| 1068 | </dl> |
|---|
| 1069 | <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a> <a id="cache-response-directive" href="#cache-response-directive">Response Cache-Control Directives</a></h3> |
|---|
| 1070 | <div id="rfc.figure.u.11"></div> <pre class="inline"><span id="rfc.iref.g.8"></span> <a href="#header.cache-control" class="smpl">cache-response-directive</a> = |
|---|
| 1071 | "public" |
|---|
| 1072 | / "private" [ "=" <a href="#notation" class="smpl">DQUOTE</a> 1#<a href="#abnf.dependencies" class="smpl">field-name</a> <a href="#notation" class="smpl">DQUOTE</a> ] |
|---|
| 1073 | / "no-cache" [ "=" <a href="#notation" class="smpl">DQUOTE</a> 1#<a href="#abnf.dependencies" class="smpl">field-name</a> <a href="#notation" class="smpl">DQUOTE</a> ] |
|---|
| 1074 | / "no-store" |
|---|
| 1075 | / "no-transform" |
|---|
| 1076 | / "must-revalidate" |
|---|
| 1077 | / "proxy-revalidate" |
|---|
| 1078 | / "max-age" "=" <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> |
|---|
| 1079 | / "s-maxage" "=" <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> |
|---|
| 1080 | / <a href="#header.cache-control" class="smpl">cache-extension</a> |
|---|
| 1081 | </pre> <p id="rfc.section.3.2.2.p.2"> <span id="rfc.iref.c.11"></span> <span id="rfc.iref.p.1"></span> public |
|---|
| 1082 | </p> |
|---|
| 1083 | <dl class="empty"> |
|---|
| 1084 | <dd>The public response directive indicates that the response <em class="bcp14">MAY</em> be cached, even if it would normally be non-cacheable or cacheable only within a non-shared cache. (See also 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.) |
|---|
| 1085 | </dd> |
|---|
| 1086 | </dl> |
|---|
| 1087 | <p id="rfc.section.3.2.2.p.3"> <span id="rfc.iref.c.12"></span> <span id="rfc.iref.p.2"></span> private |
|---|
| 1088 | </p> |
|---|
| 1089 | <dl class="empty"> |
|---|
| 1090 | <dd>The private response directive indicates that the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be stored by a shared cache. A private (non-shared) cache <em class="bcp14">MAY</em> store the response. |
|---|
| 1091 | </dd> |
|---|
| 1092 | <dd>If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated |
|---|
| 1093 | with the listed response headers. That is, the specified field-names(s) <em class="bcp14">MUST NOT</em> be stored by a shared cache, whereas the remainder of the response message <em class="bcp14">MAY</em> be. |
|---|
| 1094 | </dd> |
|---|
| 1095 | <dd> <b>Note:</b> This usage of the word private only controls where the response may be stored, and cannot ensure the privacy of the message |
|---|
| 1096 | content. |
|---|
| 1097 | </dd> |
|---|
| 1098 | </dl> |
|---|
| 1099 | <p id="rfc.section.3.2.2.p.4"> <span id="rfc.iref.c.13"></span> <span id="rfc.iref.n.4"></span> no-cache |
|---|
| 1100 | </p> |
|---|
| 1101 | <dl class="empty"> |
|---|
| 1102 | <dd>The no-cache response directive indicates that a response <em class="bcp14">MUST NOT</em> be used to satisfy a subsequent request without successful validation on the origin server. This allows an origin server to |
|---|
| 1103 | prevent caching even by caches that have been configured to return stale responses. |
|---|
| 1104 | </dd> |
|---|
| 1105 | <dd>If the no-cache response directive specifies one or more field-names, this requirement is limited to the field-values assosicated |
|---|
| 1106 | with the listed response headers. That is, the specified field-name(s) <em class="bcp14">MUST NOT</em> be sent in the response to a subsequent request without successful validation on the origin server. This allows an origin |
|---|
| 1107 | server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response. |
|---|
| 1108 | </dd> |
|---|
| 1109 | <dd> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. |
|---|
| 1110 | </dd> |
|---|
| 1111 | </dl> |
|---|
| 1112 | <p id="rfc.section.3.2.2.p.5"> <span id="rfc.iref.c.14"></span> <span id="rfc.iref.n.5"></span> no-store |
|---|
| 1113 | </p> |
|---|
| 1114 | <dl class="empty"> |
|---|
| 1115 | <dd>The no-store response directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either the immediate request or response. This directive applies to both non-shared and shared 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. |
|---|
| 1116 | </dd> |
|---|
| 1117 | <dd>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches |
|---|
| 1118 | might not recognize or obey this directive, and communications networks may be vulnerable to eavesdropping. |
|---|
| 1119 | </dd> |
|---|
| 1120 | </dl> |
|---|
| 1121 | <p id="rfc.section.3.2.2.p.6"> <span id="rfc.iref.c.15"></span> <span id="rfc.iref.m.4"></span> must-revalidate |
|---|
| 1122 | </p> |
|---|
| 1123 | <dl class="empty"> |
|---|
| 1124 | <dd>The must-revalidate response directive indicates that validation is required before the response is used by a cache to satisfy |
|---|
| 1125 | any request. |
|---|
| 1126 | </dd> |
|---|
| 1127 | <dd>When the present, caches <em class="bcp14">MUST NOT</em> use a stored after it becomes stale to respond to a subsequent request without first validating it with the origin server. |
|---|
| 1128 | </dd> |
|---|
| 1129 | <dd>The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances |
|---|
| 1130 | 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. |
|---|
| 1131 | </dd> |
|---|
| 1132 | <dd>Servers <em class="bcp14">SHOULD</em> send the must-revalidate directive if and only if failure to validate a request on the entity could result in incorrect operation, |
|---|
| 1133 | such as a silently unexecuted financial transaction. |
|---|
| 1134 | </dd> |
|---|
| 1135 | </dl> |
|---|
| 1136 | <p id="rfc.section.3.2.2.p.7"> <span id="rfc.iref.c.16"></span> <span id="rfc.iref.p.3"></span> proxy-revalidate |
|---|
| 1137 | </p> |
|---|
| 1138 | <dl class="empty"> |
|---|
| 1139 | <dd>The proxy-revalidate response directive has the same meaning as the must-revalidate response directive, except that it does |
|---|
| 1140 | not apply to non-shared caches. |
|---|
| 1141 | </dd> |
|---|
| 1142 | </dl> |
|---|
| 1143 | <p id="rfc.section.3.2.2.p.8"> <span id="rfc.iref.c.17"></span> <span id="rfc.iref.m.5"></span> max-age |
|---|
| 1144 | </p> |
|---|
| 1145 | <dl class="empty"> |
|---|
| 1146 | <dd>The max-age response directive indicates that response is to be considered stale after its age is greater than the specified |
|---|
| 1147 | number of seconds. |
|---|
| 1148 | </dd> |
|---|
| 1149 | </dl> |
|---|
| 1150 | <p id="rfc.section.3.2.2.p.9"> <span id="rfc.iref.c.18"></span> <span id="rfc.iref.s.2"></span> s-maxage |
|---|
| 1151 | </p> |
|---|
| 1152 | <dl class="empty"> |
|---|
| 1153 | <dd>The s-maxage response directive indicates that, in shared caches, the maximum age specified by this directive overrides the |
|---|
| 1154 | maximum age specified by either the max-age directive or the Expires header. The s-maxage directive also implies the semantics |
|---|
| 1155 | of the proxy-revalidate response directive. |
|---|
| 1156 | </dd> |
|---|
| 1157 | </dl> |
|---|
| 1158 | <p id="rfc.section.3.2.2.p.10"> <span id="rfc.iref.c.19"></span> <span id="rfc.iref.n.6"></span> no-transform |
|---|
| 1159 | </p> |
|---|
| 1160 | <dl class="empty"> |
|---|
| 1161 | <dd>The no-transform response directive indicates that an intermediate cache or proxy <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type response headers, nor the response entity-body. |
|---|
| 1162 | </dd> |
|---|
| 1163 | </dl> |
|---|
| 1164 | <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a> <a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3> |
|---|
| 1165 | <p id="rfc.section.3.2.3.p.1">The Cache-Control header field can be extended through the use of one or more cache-extension tokens, each with an optional |
|---|
| 1166 | 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 |
|---|
| 1167 | to the existing base of cache directives. Both the new directive and the standard directive are supplied, such that applications |
|---|
| 1168 | which do not understand the new directive will default to the behavior specified by the standard directive, and those that |
|---|
| 1169 | understand the new directive will recognize it as modifying the requirements associated with the standard directive. In this |
|---|
| 1170 | way, extensions to the cache-control directives can be made without requiring changes to the base protocol. |
|---|
| 1171 | </p> |
|---|
| 1172 | <p id="rfc.section.3.2.3.p.2">This extension mechanism depends on an HTTP cache obeying all of the cache-control directives defined for its native HTTP-version, |
|---|
| 1173 | obeying certain extensions, and ignoring all directives that it does not understand. |
|---|
| 1174 | </p> |
|---|
| 1175 | <p id="rfc.section.3.2.3.p.3">For example, consider a hypothetical new response directive called "community" which acts as a modifier to the private directive. |
|---|
| 1176 | We define this new directive to mean that, in addition to any non-shared cache, any cache which is shared only by members |
|---|
| 1177 | of the community named within its value may cache the response. An origin server wishing to allow the UCI community to use |
|---|
| 1178 | an otherwise private response in their shared cache(s) could do so by including |
|---|
| 1179 | </p> |
|---|
| 1180 | <div id="rfc.figure.u.12"></div> <pre class="text"> Cache-Control: private, community="UCI" |
|---|
| 1181 | </pre> <p id="rfc.section.3.2.3.p.5">A cache seeing this header field will act correctly even if the cache does not understand the community cache-extension, since |
|---|
| 1182 | it will also see and understand the private directive and thus default to the safe behavior. |
|---|
| 1183 | </p> |
|---|
| 1184 | <p id="rfc.section.3.2.3.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 |
|---|
| 1185 | directives (or the response's default cacheability) such that the cache behavior will remain minimally correct even if the |
|---|
| 1186 | cache does not understand the extension(s). |
|---|
| 1187 | </p> |
|---|
| 1188 | <div id="rfc.iref.e.2"></div> |
|---|
| 1189 | <div id="rfc.iref.h.4"></div> |
|---|
| 1190 | <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> |
|---|
| 1191 | <p id="rfc.section.3.3.p.1">The entity-header field "Expires" gives the date/time after which the response is considered stale. See <a href="#expiration.model" title="Freshness Model">Section 2.3</a> for further discussion of the expiration model. |
|---|
| 1192 | </p> |
|---|
| 1193 | <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 |
|---|
| 1194 | that time. |
|---|
| 1195 | </p> |
|---|
| 1196 | <p id="rfc.section.3.3.p.3">The field-value is an absolute date and time as defined by HTTP-date in <a href="p1-messaging.html#full.date" title="Full Date">Section 3.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format. |
|---|
| 1197 | </p> |
|---|
| 1198 | <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> <a href="#header.expires" class="smpl">Expires</a> = "Expires" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.expires" class="smpl">Expires-v</a> |
|---|
| 1199 | <a href="#header.expires" class="smpl">Expires-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a> |
|---|
| 1200 | </pre><p id="rfc.section.3.3.p.5">For example</p> |
|---|
| 1201 | <div id="rfc.figure.u.14"></div> <pre class="text"> Expires: Thu, 01 Dec 1994 16:00:00 GMT |
|---|
| 1202 | </pre> <p id="rfc.section.3.3.p.7"> </p> |
|---|
| 1203 | <dl class="empty"> |
|---|
| 1204 | <dd> <b>Note:</b> if a response includes a Cache-Control field with the max-age directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section 3.2.2</a>), that directive overrides the Expires field. |
|---|
| 1205 | </dd> |
|---|
| 1206 | </dl> |
|---|
| 1207 | <p id="rfc.section.3.3.p.8">HTTP/1.1 servers <em class="bcp14">SHOULD NOT</em> send Expires dates more than one year in the future. |
|---|
| 1208 | </p> |
|---|
| 1209 | <p id="rfc.section.3.3.p.9">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"). |
|---|
| 1210 | </p> |
|---|
| 1211 | <div id="rfc.iref.p.4"></div> |
|---|
| 1212 | <div id="rfc.iref.h.5"></div> |
|---|
| 1213 | <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> |
|---|
| 1214 | <p id="rfc.section.3.4.p.1">The general-header field "Pragma" is used to include implementation-specific directives that might apply to any recipient |
|---|
| 1215 | along the request/response chain. All pragma directives specify optional behavior from the viewpoint of the protocol; however, |
|---|
| 1216 | some systems <em class="bcp14">MAY</em> require that behavior be consistent with the directives. |
|---|
| 1217 | </p> |
|---|
| 1218 | <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span> <a href="#header.pragma" class="smpl">Pragma</a> = "Pragma" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.pragma" class="smpl">Pragma-v</a> |
|---|
| 1219 | <a href="#header.pragma" class="smpl">Pragma-v</a> = 1#<a href="#header.pragma" class="smpl">pragma-directive</a> |
|---|
| 1220 | <a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / <a href="#header.pragma" class="smpl">extension-pragma</a> |
|---|
| 1221 | <a href="#header.pragma" class="smpl">extension-pragma</a> = <a href="#core.rules" class="smpl">token</a> [ "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> ) ] |
|---|
| 1222 | </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 |
|---|
| 1223 | has the same semantics as the no-cache response directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section 3.2.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. HTTP/1.1 caches <em class="bcp14">SHOULD</em> treat "Pragma: no-cache" as if the client had sent "Cache-Control: no-cache". |
|---|
| 1224 | </p> |
|---|
| 1225 | <p id="rfc.section.3.4.p.4"> </p> |
|---|
| 1226 | <dl class="empty"> |
|---|
| 1227 | <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 |
|---|
| 1228 | replacement for "Cache-Control: no-cache" in a response. |
|---|
| 1229 | </dd> |
|---|
| 1230 | </dl> |
|---|
| 1231 | <p id="rfc.section.3.4.p.5">This mechanism is deprecated; no new Pragma directives will be defined in HTTP.</p> |
|---|
| 1232 | <div id="rfc.iref.v.3"></div> |
|---|
| 1233 | <div id="rfc.iref.h.6"></div> |
|---|
| 1234 | <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> |
|---|
| 1235 | <p id="rfc.section.3.5.p.1">The "Vary" response-header field's value indicates the set of request-header fields that fully determines, while the response |
|---|
| 1236 | is fresh, whether a cache is permitted to use the response to reply to a subsequent request without validation. For uncacheable |
|---|
| 1237 | or stale responses, the Vary field value advises the user agent about the criteria that were used to select the representation. |
|---|
| 1238 | A Vary field value of "*" implies that a cache cannot determine from the request headers of a subsequent request whether this |
|---|
| 1239 | response is the 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. |
|---|
| 1240 | </p> |
|---|
| 1241 | <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span> <a href="#header.vary" class="smpl">Vary</a> = "Vary" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.vary" class="smpl">Vary-v</a> |
|---|
| 1242 | <a href="#header.vary" class="smpl">Vary-v</a> = "*" / 1#<a href="#abnf.dependencies" class="smpl">field-name</a> |
|---|
| 1243 | </pre><p id="rfc.section.3.5.p.3">The set of header fields named by the Vary field value is known as the "selecting" request-headers.</p> |
|---|
| 1244 | <p id="rfc.section.3.5.p.4">Servers <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 |
|---|
| 1245 | to properly interpret future requests on that resource and informs the user agent about the presence of negotiation on that |
|---|
| 1246 | 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 |
|---|
| 1247 | the user agent with useful information about the dimensions over which the response varies at the time of the response. |
|---|
| 1248 | </p> |
|---|
| 1249 | <p id="rfc.section.3.5.p.5">A Vary field value of "*" signals that unspecified parameters not limited to the request-headers (e.g., the network address |
|---|
| 1250 | 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. |
|---|
| 1251 | </p> |
|---|
| 1252 | <p id="rfc.section.3.5.p.6">The field-names given are not limited to the set of standard request-header fields defined by this specification. Field names |
|---|
| 1253 | are case-insensitive. |
|---|
| 1254 | </p> |
|---|
| 1255 | <div id="rfc.iref.w.1"></div> |
|---|
| 1256 | <div id="rfc.iref.h.7"></div> |
|---|
| 1257 | <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> |
|---|
| 1258 | <p id="rfc.section.3.6.p.1">The general-header field "Warning" is used to carry additional information about the status or transformation of a message |
|---|
| 1259 | which might not be reflected in the message. This information is typically used to warn about possible incorrectness introduced |
|---|
| 1260 | by caching operations or transformations applied to the entity body of the message. |
|---|
| 1261 | </p> |
|---|
| 1262 | <p id="rfc.section.3.6.p.2">Warnings can be used for other purposes, both cache-related and otherwise. The use of a warning, rather than an error status |
|---|
| 1263 | code, distinguish these responses from true failures. |
|---|
| 1264 | </p> |
|---|
| 1265 | <p id="rfc.section.3.6.p.3">Warning headers can in general be applied to any message, however some warn-codes are specific to caches and can only be applied |
|---|
| 1266 | to response messages. |
|---|
| 1267 | </p> |
|---|
| 1268 | <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> <a href="#header.warning" class="smpl">Warning</a> = "Warning" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.warning" class="smpl">Warning-v</a> |
|---|
| 1269 | <a href="#header.warning" class="smpl">Warning-v</a> = 1#<a href="#header.warning" class="smpl">warning-value</a> |
|---|
| 1270 | |
|---|
| 1271 | <a href="#header.warning" class="smpl">warning-value</a> = <a href="#header.warning" class="smpl">warn-code</a> <a href="#notation" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-agent</a> <a href="#notation" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-text</a> |
|---|
| 1272 | [<a href="#notation" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-date</a>] |
|---|
| 1273 | |
|---|
| 1274 | <a href="#header.warning" class="smpl">warn-code</a> = 3<a href="#notation" class="smpl">DIGIT</a> |
|---|
| 1275 | <a href="#header.warning" class="smpl">warn-agent</a> = ( <a href="#abnf.dependencies" class="smpl">uri-host</a> [ ":" <a href="#abnf.dependencies" class="smpl">port</a> ] ) / <a href="#abnf.dependencies" class="smpl">pseudonym</a> |
|---|
| 1276 | ; the name or pseudonym of the server adding |
|---|
| 1277 | ; the Warning header, for use in debugging |
|---|
| 1278 | <a href="#header.warning" class="smpl">warn-text</a> = <a href="#core.rules" class="smpl">quoted-string</a> |
|---|
| 1279 | <a href="#header.warning" class="smpl">warn-date</a> = <a href="#notation" class="smpl">DQUOTE</a> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> <a href="#notation" class="smpl">DQUOTE</a> |
|---|
| 1280 | </pre><p id="rfc.section.3.6.p.5">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. |
|---|
| 1281 | For example, a server might provide the same warning with texts in both English and Basque. |
|---|
| 1282 | </p> |
|---|
| 1283 | <p id="rfc.section.3.6.p.6">When this occurs, the user agent <em class="bcp14">SHOULD</em> inform the user of as many of them as possible, in the order that they appear in the response. If it is not possible to inform |
|---|
| 1284 | the user of all of the warnings, the user agent <em class="bcp14">SHOULD</em> follow these heuristics: |
|---|
| 1285 | </p> |
|---|
| 1286 | <ul> |
|---|
| 1287 | <li>Warnings that appear early in the response take priority over those appearing later in the response.</li> |
|---|
| 1288 | <li>Warnings in the user's preferred character set take priority over warnings in other character sets but with identical warn-codes |
|---|
| 1289 | and warn-agents. |
|---|
| 1290 | </li> |
|---|
| 1291 | </ul> |
|---|
| 1292 | <p id="rfc.section.3.6.p.7">Systems that generate multiple Warning headers <em class="bcp14">SHOULD</em> order them with this user agent behavior in mind. New Warning headers <em class="bcp14">SHOULD</em> be added after any existing Warning headers. |
|---|
| 1293 | </p> |
|---|
| 1294 | <p id="rfc.section.3.6.p.8">Warnings are assigned three digit warn-codes. The first digit indicates whether the Warning is required to be deleted from |
|---|
| 1295 | a stored response after validation: |
|---|
| 1296 | </p> |
|---|
| 1297 | <ul> |
|---|
| 1298 | <li>1xx Warnings that describe the freshness or validation status of the response, and so <em class="bcp14">MUST</em> be deleted by caches after validation. They <em class="bcp14">MUST NOT</em> be generated by a cache except when validating a cached entry, and <em class="bcp14">MUST NOT</em> be generated by clients. |
|---|
| 1299 | </li> |
|---|
| 1300 | <li>2xx Warnings that describe some aspect of the entity body or entity headers that is not rectified by a validation (for example, |
|---|
| 1301 | a lossy compression of the entity bodies) and which <em class="bcp14">MUST NOT</em> be deleted by caches after validation, unless a full response is returned, in which case they <em class="bcp14">MUST</em> be. |
|---|
| 1302 | </li> |
|---|
| 1303 | </ul> |
|---|
| 1304 | <p id="rfc.section.3.6.p.9">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. |
|---|
| 1305 | This decision can be based on any available knowledge, such as the location of the cache or user, the Accept-Language field |
|---|
| 1306 | in a request, the Content-Language field in a response, etc. The default language is English and the default character set |
|---|
| 1307 | 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>). |
|---|
| 1308 | </p> |
|---|
| 1309 | <p id="rfc.section.3.6.p.10">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>. |
|---|
| 1310 | </p> |
|---|
| 1311 | <p id="rfc.section.3.6.p.11">If an implementation sends a message with one or more Warning headers to a receiver whose version is HTTP/1.0 or lower, then |
|---|
| 1312 | the sender <em class="bcp14">MUST</em> include in each warning-value a warn-date that matches the Date header in the message. |
|---|
| 1313 | </p> |
|---|
| 1314 | <p id="rfc.section.3.6.p.12">If an implementation receives a message with a warning-value that includes a warn-date, and that warn-date is different from |
|---|
| 1315 | 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. (preventing the consequences of naive caching of Warning |
|---|
| 1316 | 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. |
|---|
| 1317 | </p> |
|---|
| 1318 | <p id="rfc.section.3.6.p.13">The following warn-codes are defined by this specification, each with a recommended warn-text in English, and a description |
|---|
| 1319 | of its meaning. |
|---|
| 1320 | </p> |
|---|
| 1321 | <p id="rfc.section.3.6.p.14">110 Response is stale </p> |
|---|
| 1322 | <dl class="empty"> |
|---|
| 1323 | <dd><em class="bcp14">SHOULD</em> be included whenever the returned response is stale. |
|---|
| 1324 | </dd> |
|---|
| 1325 | </dl> |
|---|
| 1326 | <p id="rfc.section.3.6.p.15">111 Revalidation failed </p> |
|---|
| 1327 | <dl class="empty"> |
|---|
| 1328 | <dd><em class="bcp14">SHOULD</em> be included if a cache returns a stale response because an attempt to validate the response failed, due to an inability to |
|---|
| 1329 | reach the server. |
|---|
| 1330 | </dd> |
|---|
| 1331 | </dl> |
|---|
| 1332 | <p id="rfc.section.3.6.p.16">112 Disconnected operation </p> |
|---|
| 1333 | <dl class="empty"> |
|---|
| 1334 | <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. |
|---|
| 1335 | </dd> |
|---|
| 1336 | </dl> |
|---|
| 1337 | <p id="rfc.section.3.6.p.17">113 Heuristic expiration </p> |
|---|
| 1338 | <dl class="empty"> |
|---|
| 1339 | <dd><em class="bcp14">SHOULD</em> be included if the cache heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater |
|---|
| 1340 | than 24 hours. |
|---|
| 1341 | </dd> |
|---|
| 1342 | </dl> |
|---|
| 1343 | <p id="rfc.section.3.6.p.18">199 Miscellaneous warning </p> |
|---|
| 1344 | <dl class="empty"> |
|---|
| 1345 | <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. |
|---|
| 1346 | </dd> |
|---|
| 1347 | </dl> |
|---|
| 1348 | <p id="rfc.section.3.6.p.19">214 Transformation applied </p> |
|---|
| 1349 | <dl class="empty"> |
|---|
| 1350 | <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 |
|---|
| 1351 | Content-Encoding header) or media-type (as specified in the Content-Type header) of the response, or the entity-body of the |
|---|
| 1352 | response, unless this Warning code already appears in the response. |
|---|
| 1353 | </dd> |
|---|
| 1354 | </dl> |
|---|
| 1355 | <p id="rfc.section.3.6.p.20">299 Miscellaneous persistent warning </p> |
|---|
| 1356 | <dl class="empty"> |
|---|
| 1357 | <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. |
|---|
| 1358 | </dd> |
|---|
| 1359 | </dl> |
|---|
| 1360 | <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="history.lists" href="#history.lists">History Lists</a></h1> |
|---|
| 1361 | <p id="rfc.section.4.p.1">User agents often have history mechanisms, such as "Back" buttons and history lists, which can be used to redisplay an entity |
|---|
| 1362 | retrieved earlier in a session. |
|---|
| 1363 | </p> |
|---|
| 1364 | <p id="rfc.section.4.p.2">History mechanisms and caches are different. In particular history mechanisms <em class="bcp14">SHOULD NOT</em> try to show a correct view of the current state of a resource. Rather, a history mechanism is meant to show exactly what the |
|---|
| 1365 | user saw at the time when the resource was retrieved. |
|---|
| 1366 | </p> |
|---|
| 1367 | <p id="rfc.section.4.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 |
|---|
| 1368 | documents. |
|---|
| 1369 | </p> |
|---|
| 1370 | <p id="rfc.section.4.p.4">This is not to be construed to prohibit the history mechanism from telling the user that a view might be stale. </p> |
|---|
| 1371 | <dl class="empty"> |
|---|
| 1372 | <dd> <b>Note:</b> if history list mechanisms unnecessarily prevent users from viewing stale resources, this will tend to force service authors |
|---|
| 1373 | to avoid using HTTP expiration controls and cache controls when they would otherwise like to. Service authors may consider |
|---|
| 1374 | it important that users not be presented with error messages or warning messages when they use navigation controls (such as |
|---|
| 1375 | BACK) to view previously fetched resources. Even though sometimes such resources ought not be cached, or ought to expire quickly, |
|---|
| 1376 | user interface considerations may force service authors to resort to other means of preventing caching (e.g. "once-only" URLs) |
|---|
| 1377 | in order not to suffer the effects of improperly functioning history mechanisms. |
|---|
| 1378 | </dd> |
|---|
| 1379 | </dl> |
|---|
| 1380 | <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> |
|---|
| 1381 | <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a> <a id="message.header.registration" href="#message.header.registration">Message Header Registration</a></h2> |
|---|
| 1382 | <p id="rfc.section.5.1.p.1">The Message Header Registry located at <<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>> should be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>): |
|---|
| 1383 | </p> |
|---|
| 1384 | <div id="rfc.table.1"> |
|---|
| 1385 | <div id="iana.header.registration.table"></div> |
|---|
| 1386 | <table summary="" class="tt full" cellpadding="3" cellspacing="0"> |
|---|
| 1387 | <thead> |
|---|
| 1388 | <tr> |
|---|
| 1389 | <th>Header Field Name</th> |
|---|
| 1390 | <th>Protocol</th> |
|---|
| 1391 | <th>Status</th> |
|---|
| 1392 | <th>Reference</th> |
|---|
| 1393 | </tr> |
|---|
| 1394 | </thead> |
|---|
| 1395 | <tbody> |
|---|
| 1396 | <tr> |
|---|
| 1397 | <td>Age</td> |
|---|
| 1398 | <td>http</td> |
|---|
| 1399 | <td>standard</td> |
|---|
| 1400 | <td> <a href="#header.age" id="rfc.xref.header.age.2" title="Age">Section 3.1</a> |
|---|
| 1401 | </td> |
|---|
| 1402 | </tr> |
|---|
| 1403 | <tr> |
|---|
| 1404 | <td>Cache-Control</td> |
|---|
| 1405 | <td>http</td> |
|---|
| 1406 | <td>standard</td> |
|---|
| 1407 | <td> <a href="#header.cache-control" id="rfc.xref.header.cache-control.5" title="Cache-Control">Section 3.2</a> |
|---|
| 1408 | </td> |
|---|
| 1409 | </tr> |
|---|
| 1410 | <tr> |
|---|
| 1411 | <td>Expires</td> |
|---|
| 1412 | <td>http</td> |
|---|
| 1413 | <td>standard</td> |
|---|
| 1414 | <td> <a href="#header.expires" id="rfc.xref.header.expires.3" title="Expires">Section 3.3</a> |
|---|
| 1415 | </td> |
|---|
| 1416 | </tr> |
|---|
| 1417 | <tr> |
|---|
| 1418 | <td>Pragma</td> |
|---|
| 1419 | <td>http</td> |
|---|
| 1420 | <td>standard</td> |
|---|
| 1421 | <td> <a href="#header.pragma" id="rfc.xref.header.pragma.3" title="Pragma">Section 3.4</a> |
|---|
| 1422 | </td> |
|---|
| 1423 | </tr> |
|---|
| 1424 | <tr> |
|---|
| 1425 | <td>Vary</td> |
|---|
| 1426 | <td>http</td> |
|---|
| 1427 | <td>standard</td> |
|---|
| 1428 | <td> <a href="#header.vary" id="rfc.xref.header.vary.2" title="Vary">Section 3.5</a> |
|---|
| 1429 | </td> |
|---|
| 1430 | </tr> |
|---|
| 1431 | <tr> |
|---|
| 1432 | <td>Warning</td> |
|---|
| 1433 | <td>http</td> |
|---|
| 1434 | <td>standard</td> |
|---|
| 1435 | <td> <a href="#header.warning" id="rfc.xref.header.warning.3" title="Warning">Section 3.6</a> |
|---|
| 1436 | </td> |
|---|
| 1437 | </tr> |
|---|
| 1438 | </tbody> |
|---|
| 1439 | </table> |
|---|
| 1440 | </div> |
|---|
| 1441 | <p id="rfc.section.5.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> |
|---|
| 1442 | <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> |
|---|
| 1443 | <p id="rfc.section.6.p.1">Caches expose additional potential vulnerabilities, since the contents of the cache represent an attractive target for malicious |
|---|
| 1444 | exploitation. Because cache contents persist after an HTTP request is complete, an attack on the cache can reveal information |
|---|
| 1445 | long after a user believes that the information has been removed from the network. Therefore, cache contents should be protected |
|---|
| 1446 | as sensitive information. |
|---|
| 1447 | </p> |
|---|
| 1448 | <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> |
|---|
| 1449 | <p id="rfc.section.7.p.1">Much of the content and presentation of the caching design is due to suggestions and comments from individuals including: |
|---|
| 1450 | Shel Kaphan, Paul Leach, Koen Holtman, David Morris, and Larry Masinter. |
|---|
| 1451 | </p> |
|---|
| 1452 | <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References |
|---|
| 1453 | </h1> |
|---|
| 1454 | <h2 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References |
|---|
| 1455 | </h2> |
|---|
| 1456 | <table summary="Normative References"> |
|---|
| 1457 | <tr> |
|---|
| 1458 | <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> |
|---|
| 1459 | <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1”, ISO/IEC 8859-1:1998, 1998.</td> |
|---|
| 1460 | </tr> |
|---|
| 1461 | <tr> |
|---|
| 1462 | <td class="reference"><b id="Part1">[Part1]</b></td> |
|---|
| 1463 | <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), March 2009. |
|---|
| 1464 | </td> |
|---|
| 1465 | </tr> |
|---|
| 1466 | <tr> |
|---|
| 1467 | <td class="reference"><b id="Part2">[Part2]</b></td> |
|---|
| 1468 | <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), March 2009. |
|---|
| 1469 | </td> |
|---|
| 1470 | </tr> |
|---|
| 1471 | <tr> |
|---|
| 1472 | <td class="reference"><b id="Part3">[Part3]</b></td> |
|---|
| 1473 | <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), March 2009. |
|---|
| 1474 | </td> |
|---|
| 1475 | </tr> |
|---|
| 1476 | <tr> |
|---|
| 1477 | <td class="reference"><b id="Part4">[Part4]</b></td> |
|---|
| 1478 | <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), March 2009. |
|---|
| 1479 | </td> |
|---|
| 1480 | </tr> |
|---|
| 1481 | <tr> |
|---|
| 1482 | <td class="reference"><b id="Part5">[Part5]</b></td> |
|---|
| 1483 | <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), March 2009. |
|---|
| 1484 | </td> |
|---|
| 1485 | </tr> |
|---|
| 1486 | <tr> |
|---|
| 1487 | <td class="reference"><b id="Part7">[Part7]</b></td> |
|---|
| 1488 | <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), March 2009. |
|---|
| 1489 | </td> |
|---|
| 1490 | </tr> |
|---|
| 1491 | <tr> |
|---|
| 1492 | <td class="reference"><b id="RFC2047">[RFC2047]</b></td> |
|---|
| 1493 | <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. |
|---|
| 1494 | </td> |
|---|
| 1495 | </tr> |
|---|
| 1496 | <tr> |
|---|
| 1497 | <td class="reference"><b id="RFC2119">[RFC2119]</b></td> |
|---|
| 1498 | <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. |
|---|
| 1499 | </td> |
|---|
| 1500 | </tr> |
|---|
| 1501 | <tr> |
|---|
| 1502 | <td class="reference"><b id="RFC5234">[RFC5234]</b></td> |
|---|
| 1503 | <td class="top"><a title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD 68, RFC 5234, January 2008. |
|---|
| 1504 | </td> |
|---|
| 1505 | </tr> |
|---|
| 1506 | </table> |
|---|
| 1507 | <h2 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References |
|---|
| 1508 | </h2> |
|---|
| 1509 | <table summary="Informative References"> |
|---|
| 1510 | <tr> |
|---|
| 1511 | <td class="reference"><b id="RFC1305">[RFC1305]</b></td> |
|---|
| 1512 | <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. |
|---|
| 1513 | </td> |
|---|
| 1514 | </tr> |
|---|
| 1515 | <tr> |
|---|
| 1516 | <td class="reference"><b id="RFC2616">[RFC2616]</b></td> |
|---|
| 1517 | <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. |
|---|
| 1518 | </td> |
|---|
| 1519 | </tr> |
|---|
| 1520 | <tr> |
|---|
| 1521 | <td class="reference"><b id="RFC3864">[RFC3864]</b></td> |
|---|
| 1522 | <td class="top"><a title="Nine by Nine">Klyne, G.</a>, <a title="BEA Systems">Nottingham, M.</a>, and <a title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP 90, RFC 3864, September 2004. |
|---|
| 1523 | </td> |
|---|
| 1524 | </tr> |
|---|
| 1525 | </table> |
|---|
| 1526 | <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> |
|---|
| 1527 | <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> |
|---|
| 1528 | (editor) |
|---|
| 1529 | <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> |
|---|
| 1530 | <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> |
|---|
| 1531 | <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> |
|---|
| 1532 | <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> |
|---|
| 1533 | <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> |
|---|
| 1534 | <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> |
|---|
| 1535 | <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> |
|---|
| 1536 | <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span> |
|---|
| 1537 | (editor) |
|---|
| 1538 | <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> |
|---|
| 1539 | <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span> |
|---|
| 1540 | (editor) |
|---|
| 1541 | <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> |
|---|
| 1542 | <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> |
|---|
| 1543 | <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> |
|---|
| 1544 | <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.1</a>, <a href="#header.cache-control" id="rfc.xref.header.cache-control.6" title="Cache-Control">3.2</a>). |
|---|
| 1545 | </p> |
|---|
| 1546 | <p id="rfc.section.A.1.p.2">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow |
|---|
| 1547 | for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are |
|---|
| 1548 | computed. (see also <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) |
|---|
| 1549 | </p> |
|---|
| 1550 | <p id="rfc.section.A.1.p.3">Proxies should be able to add Content-Length when appropriate.</p> |
|---|
| 1551 | <p id="rfc.section.A.1.p.4">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send |
|---|
| 1552 | needed headers in a 206 response, this problem can be avoided. (<a href="#combining.headers" title="Combining Responses">Section 2.7</a>) |
|---|
| 1553 | </p> |
|---|
| 1554 | <p id="rfc.section.A.1.p.5">The Cache-Control: max-age directive was not properly defined for responses.</p> |
|---|
| 1555 | <p id="rfc.section.A.1.p.6">Warnings could be cached incorrectly, or not updated appropriately. <a href="#expiration.model" title="Freshness Model">2.3</a>, <a href="#combining.headers" title="Combining Responses">2.7</a>, <a href="#header.cache-control" id="rfc.xref.header.cache-control.7" title="Cache-Control">3.2</a>, and <a href="#header.warning" id="rfc.xref.header.warning.4" 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. |
|---|
| 1556 | </p> |
|---|
| 1557 | <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> |
|---|
| 1558 | <p id="rfc.section.A.2.p.1">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 2.5</a>) |
|---|
| 1559 | </p> |
|---|
| 1560 | <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> |
|---|
| 1561 | <div id="rfc.figure.u.18"></div> <pre class="inline"><a href="#header.age" class="smpl">Age</a> = "Age:" OWS Age-v |
|---|
| 1562 | <a href="#header.age" class="smpl">Age-v</a> = delta-seconds |
|---|
| 1563 | |
|---|
| 1564 | <a href="#header.cache-control" class="smpl">Cache-Control</a> = "Cache-Control:" OWS Cache-Control-v |
|---|
| 1565 | <a href="#header.cache-control" class="smpl">Cache-Control-v</a> = *( "," OWS ) cache-directive *( OWS "," [ OWS |
|---|
| 1566 | cache-directive ] ) |
|---|
| 1567 | |
|---|
| 1568 | <a href="#header.expires" class="smpl">Expires</a> = "Expires:" OWS Expires-v |
|---|
| 1569 | <a href="#header.expires" class="smpl">Expires-v</a> = HTTP-date |
|---|
| 1570 | |
|---|
| 1571 | <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 3.2.1> |
|---|
| 1572 | |
|---|
| 1573 | <a href="#core.rules" class="smpl">OWS</a> = <OWS, defined in [Part1], Section 1.2.2> |
|---|
| 1574 | |
|---|
| 1575 | <a href="#header.pragma" class="smpl">Pragma</a> = "Pragma:" OWS Pragma-v |
|---|
| 1576 | <a href="#header.pragma" class="smpl">Pragma-v</a> = *( "," OWS ) pragma-directive *( OWS "," [ OWS |
|---|
| 1577 | pragma-directive ] ) |
|---|
| 1578 | |
|---|
| 1579 | <a href="#header.vary" class="smpl">Vary</a> = "Vary:" OWS Vary-v |
|---|
| 1580 | <a href="#header.vary" class="smpl">Vary-v</a> = "*" / ( *( "," OWS ) field-name *( OWS "," [ OWS field-name |
|---|
| 1581 | ] ) ) |
|---|
| 1582 | |
|---|
| 1583 | <a href="#header.warning" class="smpl">Warning</a> = "Warning:" OWS Warning-v |
|---|
| 1584 | <a href="#header.warning" class="smpl">Warning-v</a> = *( "," OWS ) warning-value *( OWS "," [ OWS warning-value |
|---|
| 1585 | ] ) |
|---|
| 1586 | |
|---|
| 1587 | <a href="#header.cache-control" class="smpl">cache-directive</a> = cache-request-directive / cache-response-directive |
|---|
| 1588 | <a href="#header.cache-control" class="smpl">cache-extension</a> = token [ "=" ( token / quoted-string ) ] |
|---|
| 1589 | <a href="#header.cache-control" class="smpl">cache-request-directive</a> = "no-cache" / "no-store" / ( "max-age=" |
|---|
| 1590 | delta-seconds ) / ( "max-stale" [ "=" delta-seconds ] ) / ( |
|---|
| 1591 | "min-fresh=" delta-seconds ) / "no-transform" / "only-if-cached" / |
|---|
| 1592 | cache-extension |
|---|
| 1593 | <a href="#header.cache-control" class="smpl">cache-response-directive</a> = "public" / ( "private" [ "=" DQUOTE *( "," |
|---|
| 1594 | OWS ) field-name *( OWS "," [ OWS field-name ] ) DQUOTE ] ) / ( |
|---|
| 1595 | "no-cache" [ "=" DQUOTE *( "," OWS ) field-name *( OWS "," [ OWS |
|---|
| 1596 | field-name ] ) DQUOTE ] ) / "no-store" / "no-transform" / |
|---|
| 1597 | "must-revalidate" / "proxy-revalidate" / ( "max-age=" delta-seconds |
|---|
| 1598 | ) / ( "s-maxage=" delta-seconds ) / cache-extension |
|---|
| 1599 | |
|---|
| 1600 | <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> = 1*DIGIT |
|---|
| 1601 | |
|---|
| 1602 | <a href="#header.pragma" class="smpl">extension-pragma</a> = token [ "=" ( token / quoted-string ) ] |
|---|
| 1603 | |
|---|
| 1604 | <a href="#abnf.dependencies" class="smpl">field-name</a> = <field-name, defined in [Part1], Section 4.2> |
|---|
| 1605 | |
|---|
| 1606 | <a href="#abnf.dependencies" class="smpl">port</a> = <port, defined in [Part1], Section 2.1> |
|---|
| 1607 | <a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / extension-pragma |
|---|
| 1608 | <a href="#abnf.dependencies" class="smpl">pseudonym</a> = <pseudonym, defined in [Part1], Section 8.9> |
|---|
| 1609 | |
|---|
| 1610 | <a href="#core.rules" class="smpl">quoted-string</a> = <quoted-string, defined in [Part1], Section 1.2.2> |
|---|
| 1611 | |
|---|
| 1612 | <a href="#core.rules" class="smpl">token</a> = <token, defined in [Part1], Section 1.2.2> |
|---|
| 1613 | |
|---|
| 1614 | <a href="#abnf.dependencies" class="smpl">uri-host</a> = <uri-host, defined in [Part1], Section 2.1> |
|---|
| 1615 | |
|---|
| 1616 | <a href="#header.warning" class="smpl">warn-agent</a> = ( uri-host [ ":" port ] ) / pseudonym |
|---|
| 1617 | <a href="#header.warning" class="smpl">warn-code</a> = 3DIGIT |
|---|
| 1618 | <a href="#header.warning" class="smpl">warn-date</a> = DQUOTE HTTP-date DQUOTE |
|---|
| 1619 | <a href="#header.warning" class="smpl">warn-text</a> = quoted-string |
|---|
| 1620 | <a href="#header.warning" class="smpl">warning-value</a> = warn-code SP warn-agent SP warn-text [ SP warn-date |
|---|
| 1621 | ] |
|---|
| 1622 | |
|---|
| 1623 | |
|---|
| 1624 | </pre> <div id="rfc.figure.u.19"></div> |
|---|
| 1625 | <p>ABNF diagnostics:</p><pre class="inline">; Age defined but not used |
|---|
| 1626 | ; Cache-Control defined but not used |
|---|
| 1627 | ; Expires defined but not used |
|---|
| 1628 | ; Pragma defined but not used |
|---|
| 1629 | ; Vary defined but not used |
|---|
| 1630 | ; Warning defined but not used |
|---|
| 1631 | </pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> |
|---|
| 1632 | <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a> Since RFC2616 |
|---|
| 1633 | </h2> |
|---|
| 1634 | <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. |
|---|
| 1635 | </p> |
|---|
| 1636 | <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a> Since draft-ietf-httpbis-p6-cache-00 |
|---|
| 1637 | </h2> |
|---|
| 1638 | <p id="rfc.section.C.2.p.1">Closed issues: </p> |
|---|
| 1639 | <ul> |
|---|
| 1640 | <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>>) |
|---|
| 1641 | </li> |
|---|
| 1642 | <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>>) |
|---|
| 1643 | </li> |
|---|
| 1644 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>>: "Normative and Informative references" |
|---|
| 1645 | </li> |
|---|
| 1646 | <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" |
|---|
| 1647 | </li> |
|---|
| 1648 | <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" |
|---|
| 1649 | </li> |
|---|
| 1650 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65</a>>: "Informative references" |
|---|
| 1651 | </li> |
|---|
| 1652 | <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" |
|---|
| 1653 | </li> |
|---|
| 1654 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86</a>>: "Normative up-to-date references" |
|---|
| 1655 | </li> |
|---|
| 1656 | <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" |
|---|
| 1657 | </li> |
|---|
| 1658 | </ul> |
|---|
| 1659 | <p id="rfc.section.C.2.p.2">Other changes: </p> |
|---|
| 1660 | <ul> |
|---|
| 1661 | <li>Use names of RFC4234 core rules DQUOTE and HTAB (work in progress on <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>>) |
|---|
| 1662 | </li> |
|---|
| 1663 | </ul> |
|---|
| 1664 | <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a> Since draft-ietf-httpbis-p6-cache-01 |
|---|
| 1665 | </h2> |
|---|
| 1666 | <p id="rfc.section.C.3.p.1">Closed issues: </p> |
|---|
| 1667 | <ul> |
|---|
| 1668 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/82">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/82</a>>: "rel_path not used" |
|---|
| 1669 | </li> |
|---|
| 1670 | </ul> |
|---|
| 1671 | <p id="rfc.section.C.3.p.2">Other changes: </p> |
|---|
| 1672 | <ul> |
|---|
| 1673 | <li>Get rid of duplicate BNF rule names ("host" -> "uri-host") (work in progress on <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>>) |
|---|
| 1674 | </li> |
|---|
| 1675 | <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li> |
|---|
| 1676 | </ul> |
|---|
| 1677 | <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a> <a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p6-cache-02</a></h2> |
|---|
| 1678 | <p id="rfc.section.C.4.p.1">Ongoing work on IANA Message Header Registration (<<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/40">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/40</a>>): |
|---|
| 1679 | </p> |
|---|
| 1680 | <ul> |
|---|
| 1681 | <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li> |
|---|
| 1682 | </ul> |
|---|
| 1683 | <h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a> <a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p6-cache-03</a></h2> |
|---|
| 1684 | <p id="rfc.section.C.5.p.1">Closed issues: </p> |
|---|
| 1685 | <ul> |
|---|
| 1686 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/106">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/106</a>>: "Vary header classification" |
|---|
| 1687 | </li> |
|---|
| 1688 | </ul> |
|---|
| 1689 | <h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a> <a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p6-cache-04</a></h2> |
|---|
| 1690 | <h2 id="rfc.section.C.7"><a href="#rfc.section.C.7">C.7</a> <a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p6-cache-05</a></h2> |
|---|
| 1691 | <p id="rfc.section.C.7.p.1">This is a total rewrite.</p> |
|---|
| 1692 | <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> |
|---|
| 1693 | <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> |
|---|
| 1694 | </p> |
|---|
| 1695 | <div class="print2col"> |
|---|
| 1696 | <ul class="ind"> |
|---|
| 1697 | <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind"> |
|---|
| 1698 | <li class="indline1">age <a class="iref" href="#rfc.iref.a.1">1.2</a></li> |
|---|
| 1699 | <li class="indline1">Age header <a class="iref" href="#rfc.xref.header.age.1">2.2</a>, <a class="iref" href="#rfc.iref.a.2"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.header.age.2">5.1</a></li> |
|---|
| 1700 | </ul> |
|---|
| 1701 | </li> |
|---|
| 1702 | <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind"> |
|---|
| 1703 | <li class="indline1">cache <a class="iref" href="#rfc.iref.c.1">1.1</a></li> |
|---|
| 1704 | <li class="indline1">Cache Directives |
|---|
| 1705 | <ul class="ind"> |
|---|
| 1706 | <li class="indline1">max-age <a class="iref" href="#rfc.iref.c.6"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.c.17"><b>3.2.2</b></a></li> |
|---|
| 1707 | <li class="indline1">max-stale <a class="iref" href="#rfc.iref.c.7"><b>3.2.1</b></a></li> |
|---|
| 1708 | <li class="indline1">min-fresh <a class="iref" href="#rfc.iref.c.8"><b>3.2.1</b></a></li> |
|---|
| 1709 | <li class="indline1">must-revalidate <a class="iref" href="#rfc.iref.c.15"><b>3.2.2</b></a></li> |
|---|
| 1710 | <li class="indline1">no-cache <a class="iref" href="#rfc.iref.c.4"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.c.13"><b>3.2.2</b></a></li> |
|---|
| 1711 | <li class="indline1">no-store <a class="iref" href="#rfc.iref.c.5"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.c.14"><b>3.2.2</b></a></li> |
|---|
| 1712 | <li class="indline1">no-transform <a class="iref" href="#rfc.iref.c.9"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.c.19"><b>3.2.2</b></a></li> |
|---|
| 1713 | <li class="indline1">only-if-cached <a class="iref" href="#rfc.iref.c.10"><b>3.2.1</b></a></li> |
|---|
| 1714 | <li class="indline1">private <a class="iref" href="#rfc.iref.c.12"><b>3.2.2</b></a></li> |
|---|
| 1715 | <li class="indline1">proxy-revalidate <a class="iref" href="#rfc.iref.c.16"><b>3.2.2</b></a></li> |
|---|
| 1716 | <li class="indline1">public <a class="iref" href="#rfc.iref.c.11"><b>3.2.2</b></a></li> |
|---|
| 1717 | <li class="indline1">s-maxage <a class="iref" href="#rfc.iref.c.18"><b>3.2.2</b></a></li> |
|---|
| 1718 | </ul> |
|---|
| 1719 | </li> |
|---|
| 1720 | <li class="indline1">Cache-Control header <a class="iref" href="#rfc.xref.header.cache-control.1">2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.2">2.2</a>, <a class="iref" href="#rfc.xref.header.cache-control.3">2.2</a>, <a class="iref" href="#rfc.xref.header.cache-control.4">2.2</a>, <a class="iref" href="#rfc.iref.c.3"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.cache-control.5">5.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.6">A.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.7">A.1</a></li> |
|---|
| 1721 | <li class="indline1">cacheable <a class="iref" href="#rfc.iref.c.2">1.2</a></li> |
|---|
| 1722 | </ul> |
|---|
| 1723 | </li> |
|---|
| 1724 | <li class="indline0"><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul class="ind"> |
|---|
| 1725 | <li class="indline1">Expires header <a class="iref" href="#rfc.xref.header.expires.1">2.3</a>, <a class="iref" href="#rfc.xref.header.expires.2">2.3.1</a>, <a class="iref" href="#rfc.iref.e.2"><b>3.3</b></a>, <a class="iref" href="#rfc.xref.header.expires.3">5.1</a></li> |
|---|
| 1726 | <li class="indline1">explicit expiration time <a class="iref" href="#rfc.iref.e.1">1.2</a></li> |
|---|
| 1727 | </ul> |
|---|
| 1728 | </li> |
|---|
| 1729 | <li class="indline0"><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul class="ind"> |
|---|
| 1730 | <li class="indline1">first-hand <a class="iref" href="#rfc.iref.f.1">1.2</a></li> |
|---|
| 1731 | <li class="indline1">fresh <a class="iref" href="#rfc.iref.f.3">1.2</a></li> |
|---|
| 1732 | <li class="indline1">freshness lifetime <a class="iref" href="#rfc.iref.f.2">1.2</a></li> |
|---|
| 1733 | </ul> |
|---|
| 1734 | </li> |
|---|
| 1735 | <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind"> |
|---|
| 1736 | <li class="indline1"><tt>Grammar</tt> |
|---|
| 1737 | <ul class="ind"> |
|---|
| 1738 | <li class="indline1"><tt>Age</tt> <a class="iref" href="#rfc.iref.g.1"><b>3.1</b></a></li> |
|---|
| 1739 | <li class="indline1"><tt>Age-v</tt> <a class="iref" href="#rfc.iref.g.2"><b>3.1</b></a></li> |
|---|
| 1740 | <li class="indline1"><tt>Cache-Control</tt> <a class="iref" href="#rfc.iref.g.4"><b>3.2</b></a></li> |
|---|
| 1741 | <li class="indline1"><tt>Cache-Control-v</tt> <a class="iref" href="#rfc.iref.g.5"><b>3.2</b></a></li> |
|---|
| 1742 | <li class="indline1"><tt>cache-extension</tt> <a class="iref" href="#rfc.iref.g.6"><b>3.2</b></a></li> |
|---|
| 1743 | <li class="indline1"><tt>cache-request-directive</tt> <a class="iref" href="#rfc.iref.g.7"><b>3.2.1</b></a></li> |
|---|
| 1744 | <li class="indline1"><tt>cache-response-directive</tt> <a class="iref" href="#rfc.iref.g.8"><b>3.2.2</b></a></li> |
|---|
| 1745 | <li class="indline1"><tt>delta-seconds</tt> <a class="iref" href="#rfc.iref.g.3"><b>3.1</b></a></li> |
|---|
| 1746 | <li class="indline1"><tt>Expires</tt> <a class="iref" href="#rfc.iref.g.9"><b>3.3</b></a></li> |
|---|
| 1747 | <li class="indline1"><tt>Expires-v</tt> <a class="iref" href="#rfc.iref.g.10"><b>3.3</b></a></li> |
|---|
| 1748 | <li class="indline1"><tt>extension-pragma</tt> <a class="iref" href="#rfc.iref.g.14"><b>3.4</b></a></li> |
|---|
| 1749 | <li class="indline1"><tt>Pragma</tt> <a class="iref" href="#rfc.iref.g.11"><b>3.4</b></a></li> |
|---|
| 1750 | <li class="indline1"><tt>pragma-directive</tt> <a class="iref" href="#rfc.iref.g.13"><b>3.4</b></a></li> |
|---|
| 1751 | <li class="indline1"><tt>Pragma-v</tt> <a class="iref" href="#rfc.iref.g.12"><b>3.4</b></a></li> |
|---|
| 1752 | <li class="indline1"><tt>Vary</tt> <a class="iref" href="#rfc.iref.g.15"><b>3.5</b></a></li> |
|---|
| 1753 | <li class="indline1"><tt>Vary-v</tt> <a class="iref" href="#rfc.iref.g.16"><b>3.5</b></a></li> |
|---|
| 1754 | <li class="indline1"><tt>warn-agent</tt> <a class="iref" href="#rfc.iref.g.21"><b>3.6</b></a></li> |
|---|
| 1755 | <li class="indline1"><tt>warn-code</tt> <a class="iref" href="#rfc.iref.g.20"><b>3.6</b></a></li> |
|---|
| 1756 | <li class="indline1"><tt>warn-date</tt> <a class="iref" href="#rfc.iref.g.23"><b>3.6</b></a></li> |
|---|
| 1757 | <li class="indline1"><tt>warn-text</tt> <a class="iref" href="#rfc.iref.g.22"><b>3.6</b></a></li> |
|---|
| 1758 | <li class="indline1"><tt>Warning</tt> <a class="iref" href="#rfc.iref.g.17"><b>3.6</b></a></li> |
|---|
| 1759 | <li class="indline1"><tt>Warning-v</tt> <a class="iref" href="#rfc.iref.g.18"><b>3.6</b></a></li> |
|---|
| 1760 | <li class="indline1"><tt>warning-value</tt> <a class="iref" href="#rfc.iref.g.19"><b>3.6</b></a></li> |
|---|
| 1761 | </ul> |
|---|
| 1762 | </li> |
|---|
| 1763 | </ul> |
|---|
| 1764 | </li> |
|---|
| 1765 | <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind"> |
|---|
| 1766 | <li class="indline1">Headers |
|---|
| 1767 | <ul class="ind"> |
|---|
| 1768 | <li class="indline1">Age <a class="iref" href="#rfc.xref.header.age.1">2.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.header.age.2">5.1</a></li> |
|---|
| 1769 | <li class="indline1">Cache-Control <a class="iref" href="#rfc.xref.header.cache-control.1">2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.2">2.2</a>, <a class="iref" href="#rfc.xref.header.cache-control.3">2.2</a>, <a class="iref" href="#rfc.xref.header.cache-control.4">2.2</a>, <a class="iref" href="#rfc.iref.h.3"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.cache-control.5">5.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.6">A.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.7">A.1</a></li> |
|---|
| 1770 | <li class="indline1">Expires <a class="iref" href="#rfc.xref.header.expires.1">2.3</a>, <a class="iref" href="#rfc.xref.header.expires.2">2.3.1</a>, <a class="iref" href="#rfc.iref.h.4"><b>3.3</b></a>, <a class="iref" href="#rfc.xref.header.expires.3">5.1</a></li> |
|---|
| 1771 | <li class="indline1">Pragma <a class="iref" href="#rfc.xref.header.pragma.1">2.2</a>, <a class="iref" href="#rfc.xref.header.pragma.2">3.2</a>, <a class="iref" href="#rfc.iref.h.5"><b>3.4</b></a>, <a class="iref" href="#rfc.xref.header.pragma.3">5.1</a></li> |
|---|
| 1772 | <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>, <a class="iref" href="#rfc.xref.header.vary.2">5.1</a></li> |
|---|
| 1773 | <li class="indline1">Warning <a class="iref" href="#rfc.xref.header.warning.1">2.3.3</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.7</a>, <a class="iref" href="#rfc.iref.h.7"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.3">5.1</a>, <a class="iref" href="#rfc.xref.header.warning.4">A.1</a></li> |
|---|
| 1774 | </ul> |
|---|
| 1775 | </li> |
|---|
| 1776 | <li class="indline1">heuristic expiration time <a class="iref" href="#rfc.iref.h.1">1.2</a></li> |
|---|
| 1777 | </ul> |
|---|
| 1778 | </li> |
|---|
| 1779 | <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> |
|---|
| 1780 | <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>8.1</b></a></li> |
|---|
| 1781 | </ul> |
|---|
| 1782 | </li> |
|---|
| 1783 | <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind"> |
|---|
| 1784 | <li class="indline1">max-age |
|---|
| 1785 | <ul class="ind"> |
|---|
| 1786 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.m.1"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.m.5"><b>3.2.2</b></a></li> |
|---|
| 1787 | </ul> |
|---|
| 1788 | </li> |
|---|
| 1789 | <li class="indline1">max-stale |
|---|
| 1790 | <ul class="ind"> |
|---|
| 1791 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.m.2"><b>3.2.1</b></a></li> |
|---|
| 1792 | </ul> |
|---|
| 1793 | </li> |
|---|
| 1794 | <li class="indline1">min-fresh |
|---|
| 1795 | <ul class="ind"> |
|---|
| 1796 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.m.3"><b>3.2.1</b></a></li> |
|---|
| 1797 | </ul> |
|---|
| 1798 | </li> |
|---|
| 1799 | <li class="indline1">must-revalidate |
|---|
| 1800 | <ul class="ind"> |
|---|
| 1801 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.m.4"><b>3.2.2</b></a></li> |
|---|
| 1802 | </ul> |
|---|
| 1803 | </li> |
|---|
| 1804 | </ul> |
|---|
| 1805 | </li> |
|---|
| 1806 | <li class="indline0"><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul class="ind"> |
|---|
| 1807 | <li class="indline1">no-cache |
|---|
| 1808 | <ul class="ind"> |
|---|
| 1809 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.n.1"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.n.4"><b>3.2.2</b></a></li> |
|---|
| 1810 | </ul> |
|---|
| 1811 | </li> |
|---|
| 1812 | <li class="indline1">no-store |
|---|
| 1813 | <ul class="ind"> |
|---|
| 1814 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.n.2"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.n.5"><b>3.2.2</b></a></li> |
|---|
| 1815 | </ul> |
|---|
| 1816 | </li> |
|---|
| 1817 | <li class="indline1">no-transform |
|---|
| 1818 | <ul class="ind"> |
|---|
| 1819 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.n.3"><b>3.2.1</b></a>, <a class="iref" href="#rfc.iref.n.6"><b>3.2.2</b></a></li> |
|---|
| 1820 | </ul> |
|---|
| 1821 | </li> |
|---|
| 1822 | </ul> |
|---|
| 1823 | </li> |
|---|
| 1824 | <li class="indline0"><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul class="ind"> |
|---|
| 1825 | <li class="indline1">only-if-cached |
|---|
| 1826 | <ul class="ind"> |
|---|
| 1827 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.o.1"><b>3.2.1</b></a></li> |
|---|
| 1828 | </ul> |
|---|
| 1829 | </li> |
|---|
| 1830 | </ul> |
|---|
| 1831 | </li> |
|---|
| 1832 | <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> |
|---|
| 1833 | <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1.4</a>, <a class="iref" href="#rfc.xref.Part1.2">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.7">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.8">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.11">2.3.2</a>, <a class="iref" href="#rfc.xref.Part1.12">2.6</a>, <a class="iref" href="#rfc.xref.Part1.13">3.3</a>, <a class="iref" href="#Part1"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.Part1.14">A.1</a><ul class="ind"> |
|---|
| 1834 | <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.1">1.4</a></li> |
|---|
| 1835 | <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.4.1</a></li> |
|---|
| 1836 | <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.8">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.4.2</a></li> |
|---|
| 1837 | <li class="indline1"><em>Section 3.2.1</em> <a class="iref" href="#rfc.xref.Part1.7">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.13">3.3</a></li> |
|---|
| 1838 | <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part1.6">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.12">2.6</a></li> |
|---|
| 1839 | <li class="indline1"><em>Section 8.3</em> <a class="iref" href="#rfc.xref.Part1.11">2.3.2</a></li> |
|---|
| 1840 | <li class="indline1"><em>Section 8.9</em> <a class="iref" href="#rfc.xref.Part1.9">1.4.2</a></li> |
|---|
| 1841 | </ul> |
|---|
| 1842 | </li> |
|---|
| 1843 | <li class="indline1"><em>Part2</em> <a class="iref" href="#rfc.xref.Part2.1">2.5</a>, <a class="iref" href="#Part2"><b>8.1</b></a><ul class="ind"> |
|---|
| 1844 | <li class="indline1"><em>Section 7.1.1</em> <a class="iref" href="#rfc.xref.Part2.1">2.5</a></li> |
|---|
| 1845 | </ul> |
|---|
| 1846 | </li> |
|---|
| 1847 | <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">2.6</a>, <a class="iref" href="#Part3"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.Part3.2">A.1</a><ul class="ind"> |
|---|
| 1848 | <li class="indline1"><em>Section 4.1</em> <a class="iref" href="#rfc.xref.Part3.1">2.6</a></li> |
|---|
| 1849 | </ul> |
|---|
| 1850 | </li> |
|---|
| 1851 | <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1">2.3.1.1</a>, <a class="iref" href="#rfc.xref.Part4.2">2.4</a>, <a class="iref" href="#Part4"><b>8.1</b></a><ul class="ind"> |
|---|
| 1852 | <li class="indline1"><em>Section 6.6</em> <a class="iref" href="#rfc.xref.Part4.1">2.3.1.1</a></li> |
|---|
| 1853 | </ul> |
|---|
| 1854 | </li> |
|---|
| 1855 | <li class="indline1"><em>Part5</em> <a class="iref" href="#rfc.xref.Part5.1">2.1.1</a>, <a class="iref" href="#rfc.xref.Part5.2">2.1.1</a>, <a class="iref" href="#rfc.xref.Part5.3">2.7</a>, <a class="iref" href="#Part5"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.Part5.4">A.1</a><ul class="ind"> |
|---|
| 1856 | <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part5.2">2.1.1</a>, <a class="iref" href="#rfc.xref.Part5.3">2.7</a></li> |
|---|
| 1857 | </ul> |
|---|
| 1858 | </li> |
|---|
| 1859 | <li class="indline1"><em>Part7</em> <a class="iref" href="#rfc.xref.Part7.1">2.2</a>, <a class="iref" href="#rfc.xref.Part7.2">3.2.2</a>, <a class="iref" href="#Part7"><b>8.1</b></a><ul class="ind"> |
|---|
| 1860 | <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part7.1">2.2</a>, <a class="iref" href="#rfc.xref.Part7.2">3.2.2</a></li> |
|---|
| 1861 | </ul> |
|---|
| 1862 | </li> |
|---|
| 1863 | <li class="indline1">Pragma header <a class="iref" href="#rfc.xref.header.pragma.1">2.2</a>, <a class="iref" href="#rfc.xref.header.pragma.2">3.2</a>, <a class="iref" href="#rfc.iref.p.4"><b>3.4</b></a>, <a class="iref" href="#rfc.xref.header.pragma.3">5.1</a></li> |
|---|
| 1864 | <li class="indline1">private |
|---|
| 1865 | <ul class="ind"> |
|---|
| 1866 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.p.2"><b>3.2.2</b></a></li> |
|---|
| 1867 | </ul> |
|---|
| 1868 | </li> |
|---|
| 1869 | <li class="indline1">proxy-revalidate |
|---|
| 1870 | <ul class="ind"> |
|---|
| 1871 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.p.3"><b>3.2.2</b></a></li> |
|---|
| 1872 | </ul> |
|---|
| 1873 | </li> |
|---|
| 1874 | <li class="indline1">public |
|---|
| 1875 | <ul class="ind"> |
|---|
| 1876 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.p.1"><b>3.2.2</b></a></li> |
|---|
| 1877 | </ul> |
|---|
| 1878 | </li> |
|---|
| 1879 | </ul> |
|---|
| 1880 | </li> |
|---|
| 1881 | <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"> |
|---|
| 1882 | <li class="indline1"><em>RFC1305</em> <a class="iref" href="#rfc.xref.RFC1305.1">2.3.2</a>, <a class="iref" href="#RFC1305"><b>8.2</b></a></li> |
|---|
| 1883 | <li class="indline1"><em>RFC2047</em> <a class="iref" href="#rfc.xref.RFC2047.1">3.6</a>, <a class="iref" href="#RFC2047"><b>8.1</b></a></li> |
|---|
| 1884 | <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.3</a>, <a class="iref" href="#RFC2119"><b>8.1</b></a></li> |
|---|
| 1885 | <li class="indline1"><em>RFC2616</em> <a class="iref" href="#RFC2616"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">C.1</a></li> |
|---|
| 1886 | <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1">5.1</a>, <a class="iref" href="#RFC3864"><b>8.2</b></a></li> |
|---|
| 1887 | <li class="indline1"><em>RFC5234</em> <a class="iref" href="#rfc.xref.RFC5234.1">1.4</a>, <a class="iref" href="#RFC5234"><b>8.1</b></a><ul class="ind"> |
|---|
| 1888 | <li class="indline1"><em>Appendix B.1</em> <a class="iref" href="#rfc.xref.RFC5234.1">1.4</a></li> |
|---|
| 1889 | </ul> |
|---|
| 1890 | </li> |
|---|
| 1891 | </ul> |
|---|
| 1892 | </li> |
|---|
| 1893 | <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind"> |
|---|
| 1894 | <li class="indline1">s-maxage |
|---|
| 1895 | <ul class="ind"> |
|---|
| 1896 | <li class="indline1">Cache Directive <a class="iref" href="#rfc.iref.s.2"><b>3.2.2</b></a></li> |
|---|
| 1897 | </ul> |
|---|
| 1898 | </li> |
|---|
| 1899 | <li class="indline1">stale <a class="iref" href="#rfc.iref.s.1">1.2</a></li> |
|---|
| 1900 | </ul> |
|---|
| 1901 | </li> |
|---|
| 1902 | <li class="indline0"><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul class="ind"> |
|---|
| 1903 | <li class="indline1">validator <a class="iref" href="#rfc.iref.v.1">1.2</a>, <a class="iref" href="#rfc.iref.v.2">1.2</a></li> |
|---|
| 1904 | <li class="indline1">Vary header <a class="iref" href="#rfc.xref.header.vary.1">2.6</a>, <a class="iref" href="#rfc.iref.v.3"><b>3.5</b></a>, <a class="iref" href="#rfc.xref.header.vary.2">5.1</a></li> |
|---|
| 1905 | </ul> |
|---|
| 1906 | </li> |
|---|
| 1907 | <li class="indline0"><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul class="ind"> |
|---|
| 1908 | <li class="indline1">Warning header <a class="iref" href="#rfc.xref.header.warning.1">2.3.3</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.7</a>, <a class="iref" href="#rfc.iref.w.1"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.3">5.1</a>, <a class="iref" href="#rfc.xref.header.warning.4">A.1</a></li> |
|---|
| 1909 | </ul> |
|---|
| 1910 | </li> |
|---|
| 1911 | </ul> |
|---|
| 1912 | </div> |
|---|
| 1913 | </body> |
|---|
| 1914 | </html> |
|---|
![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
