#60 closed editorial (fixed)
Placement of 13.5.1 and 13.5.2
Reported by: | mnot@… | Owned by: | julian.reschke@… |
---|---|---|---|
Priority: | normal | Milestone: | 10 |
Component: | non-specific | Severity: | Active WG Document |
Keywords: | Cc: |
Description
13.5.1 and 13.5.2 describe how proxies should handle headers, even though it's in a section entitled "Caching in HTTP." People have a hard time finding them. Would it be helpful to try to separate out the purely intermediary-related material from section 13 to a more appropriate place (e.g., section 8, or a new section)?
Change History (13)
comment:1 Changed 15 years ago by mnot@…
- Component set to cache
comment:2 Changed 15 years ago by fielding@…
- Milestone changed from 01 to 02
comment:3 Changed 15 years ago by mnot@…
- Milestone changed from 02 to 03
comment:4 Changed 15 years ago by julian.reschke@…
- Milestone changed from 03 to 04
comment:5 Changed 14 years ago by julian.reschke@…
- Milestone changed from 04 to unassigned
comment:6 Changed 14 years ago by julian.reschke@…
This is related to text that is gone from P6. See http://trac.tools.ietf.org/wg/httpbis/trac/ticket/53#comment:6.
comment:7 Changed 14 years ago by mnot@…
- Component changed from p6-cache to p1-messaging
comment:8 Changed 13 years ago by julian.reschke@…
- Component changed from p1-messaging to non-specific
- Milestone changed from unassigned to 09
- Owner set to julian.reschke@…
- Priority set to normal
- Severity set to Active WG Document
comment:9 Changed 13 years ago by julian.reschke@…
comment:10 Changed 13 years ago by julian.reschke@…
- Milestone changed from 09 to 10
Sections have been restored, but still need to be re-organized.
comment:11 Changed 13 years ago by mnot@…
- Resolution set to fixed
- Status changed from new to closed
..but the core issue is resolved.
comment:12 Changed 13 years ago by mnot@…
comment:13 Changed 13 years ago by julian.reschke@…
This was done in -09. Change [840] has removed the remaining comments.
Note: See
TracTickets for help on using
tickets.
These sections would have been placed in part 1 (messaging) were it not for the fact that they are complete nonsense.
HTTP does not have "hop-by-hop" header fields. It has headers that are listed in Connection and others not listed in Connection and all of the associated requirements involving them are defined by Connection. 13.5.1 should not have been added to 2068 when the (previously separate) caching description was integrated.
HTTP does not have "non-modifiable" headers. It has messages that may become invalid if a header is modified. 13.5.2 is a hopeless over-specification of the general rules on forwarding messages that should be in part 1.