![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Opened 10 years ago
Closed 10 years ago
#360 closed design (fixed)
enhance considerations for new cache control directives
| Reported by: | julian.reschke@… | Owned by: | draft-ietf-httpbis-p6-cache@… |
|---|---|---|---|
| Priority: | normal | Milestone: | 20 |
| Component: | p6-cache | Severity: | In WG Last Call |
| Keywords: | Cc: |
Description
For new cache control directives, we should recommend to document
- what it means for a directive to be specified multiple times (invalid?)
- what it means for an argument-less directive to have an argument
- what it means for a argument-required directive not to have an argument
Change History (6)
comment:1 Changed 10 years ago by mnot@…
comment:2 Changed 10 years ago by mnot@…
- Resolution set to incorporated
- Status changed from new to closed
comment:3 Changed 10 years ago by julian.reschke@…
comment:4 Changed 10 years ago by julian.reschke@…
- Milestone changed from unassigned to 20
comment:5 Changed 10 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:6 Changed 10 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
From [1701]:
Add considerations for new cache directives. See #360.