![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Opened 11 years ago
Closed 11 years ago
#261 closed design (wontfix)
Check for requirements backing test cases
| Reported by: | mnot@… | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | unassigned |
| Component: | content-disp | Severity: | In WG Last Call |
| Keywords: | Cc: |
Description
Adam says that the following test cases don't have requirements backing them:
http://greenbytes.de/tech/tc2231/#attwithasciifnescapedquote http://greenbytes.de/tech/tc2231/#attwithasciifilenamenqws http://greenbytes.de/tech/tc2231/#attwithutf8fnplain http://greenbytes.de/tech/tc2231/#attwithfnrawpctenca http://greenbytes.de/tech/tc2231/#attwith2filenames http://greenbytes.de/tech/tc2231/#attfnbrokentoken http://greenbytes.de/tech/tc2231/#attbrokenquotedfn
We need to determine whether each needs a requirement, or isn't necessary.
Change History (2)
comment:1 Changed 11 years ago by julian.reschke@…
comment:2 Changed 11 years ago by julian.reschke@…
- Resolution set to wontfix
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
1) The test cases aren't part of the spec.
2) I believe Adam wanted the spec to actually specify behavior for invalid headers (see http://lists.w3.org/Archives/Public/ietf-http-wg/2010OctDec/0336.html)
That being said, I have sent email explaining why the tests are there, and how their outcome is presented (http://lists.w3.org/Archives/Public/ietf-http-wg/2010OctDec/0340.html).
I believe that this issue should be closed; if we want to pursue the question of whether we want to specify handling of invalid header fields this should go into a separate issue.