Opened 11 years ago
Closed 10 years ago
#317 closed design (fixed)
Cache-Control directive case sensitivity
| Reported by: | mnot@… | Owned by: | draft-ietf-httpbis-p6-cache@… |
|---|---|---|---|
| Priority: | normal | Milestone: | 17 |
| Component: | p6-cache | Severity: | Active WG Document |
| Keywords: | Cc: |
Description
Currently, all of the cache-control directives (e.g., max-age) are defined as BNF strings, which means that they're case-insensitive.
However, theoretically someone could define a directive without using a string (as we do for some other constructs, e.g., the HTTP version identifier), which means that it'd be case-sensitive.
It seems that having such exceptions would be surprising, and that the most straightforward thing to do would be to define CC directive names as case-insensitive.
Change History (5)
comment:1 Changed 11 years ago by mnot@…
comment:2 Changed 11 years ago by mnot@…
- Resolution set to incorporated
- Status changed from new to closed
comment:3 Changed 11 years ago by mnot@…
- Milestone changed from unassigned to 17
comment:4 Changed 10 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:5 Changed 10 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
From [1449]:
Clarify case insensitivity of CC directives. Addresses #317.