Opened 15 years ago
Closed 12 years ago
#53 closed editorial (incorporated)
Allow is not in 13.5.2
Reported by: | mnot@… | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 14 |
Component: | p1-messaging | Severity: | Active WG Document |
Keywords: | Cc: |
Description
Section 14.7 states:
"A proxy MUST NOT modify the Allow header field even if it does not understand all the methods specified, since the user agent might have other means of communicating with the origin server."
However, section 13.5.2 (Non-modifiable Headers) makes no mention of Allow. This seems like an error, but I'm not entirely sure what the fix should be -- remove 13.5.2 and push the (not-)modifiable information in the definition of the respective headers, or to maintain 13.5.2 in parallel with all of the header definitions, or to push all the information out of the header definitions into 13.5.2.
The easy fix for now would be to just make a mention of Allow in 13.5.2.
Additionally, Server should also be included.
Change History (8)
comment:1 Changed 15 years ago by mnot@…
- Component set to messaging
- Milestone set to unassigned
comment:2 Changed 15 years ago by fielding@…
- Milestone changed from unassigned 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@…
comment:7 Changed 12 years ago by julian.reschke@…
comment:8 Changed 12 years ago by julian.reschke@…
- Milestone changed from unassigned to 14
- Priority set to normal
- Resolution set to incorporated
- Severity set to Active WG Document
- Status changed from new to closed
Note: the related text is gone from P6. We probably should create a new issue for the current TODO in P6 (end-to-end and hop-by-hop headers, non-modifiable headers removed; re-spec in p1) and then close this issue, noting the new test in P1 is supposed to fix this issue.