OLD | NEW |
(Empty) | |
| 1 ## HTTP Caching Tests |
| 2 |
| 3 These tests cover HTTP-specified behaviours for caches, primarily from |
| 4 [RFC7234](http://httpwg.org/specs/rfc7234.html), but as seen through the |
| 5 lens of Fetch. |
| 6 |
| 7 A few notes: |
| 8 |
| 9 * By its nature, caching is optional; some tests expecting a response to be |
| 10 cached might fail because the client chose not to cache it, or chose to |
| 11 race the cache with a network request. |
| 12 |
| 13 * Likewise, some tests might fail because there is a separate document-level |
| 14 cache that's ill-defined; see [this |
| 15 issue](https://github.com/whatwg/fetch/issues/354). |
| 16 |
| 17 * [Partial content tests](partial.html) (a.k.a. Range requests) are not specifie
d |
| 18 in Fetch; tests are included here for interest only. |
| 19 |
| 20 * Some browser caches will behave differently when reloading / |
| 21 shift-reloading, despite the `cache mode` staying the same. |
| 22 |
| 23 * At the moment, Edge doesn't appear to using HTTP caching in conjunction |
| 24 with Fetch at all. |
OLD | NEW |