Opened 13 years ago
Closed 12 years ago
#199 closed design (fixed)
Status codes and caching
Reported by: | mnot@… | Owned by: | mnot@… |
---|---|---|---|
Priority: | normal | Milestone: | 11 |
Component: | non-specific | Severity: | Active WG Document |
Keywords: | Cc: |
Description
The role of status coded needs to be clearly specified in the caching model.
2616 defines several status codes that are "not cacheable", although it's not clear whether they can be stored but not reused without explicit freshness directives (from the client or server), or whether they just can't be stored.
Change History (13)
comment:1 Changed 13 years ago by mnot@…
comment:2 Changed 13 years ago by mnot@…
- origin changed from http://www.w3.org/mid/000401ca4ba3$b3891b60$1a9b5220$@org to http://www.w3.org/mid/000301ca4ba2$a3d48700$eb7d9500$@org
comment:3 Changed 13 years ago by mnot@…
comment:4 Changed 13 years ago by mnot@…
- Milestone changed from unassigned to 09
comment:5 Changed 13 years ago by mnot@…
- Milestone changed from 09 to 10
comment:6 Changed 13 years ago by julian.reschke@…
- Owner set to mnot@…
comment:7 Changed 13 years ago by julian.reschke@…
Does this require additional changes?
comment:8 Changed 13 years ago by julian.reschke@…
- Milestone changed from 10 to 11
comment:9 Changed 13 years ago by mnot@…
comment:10 Changed 13 years ago by mnot@…
- Resolution set to incorporated
- Status changed from new to closed
comment:11 Changed 13 years ago by julian.reschke@…
comment:12 Changed 12 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:13 Changed 12 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
From [721]:
Caches need to undestand the response status code to store it (see #199)