Closed aljones15 closed 5 years ago
the spec for HTTP Messages does think " " is a valid value for an HTTP Header
That's not my reading of Field Parsing. The value is what is left after all leading- and trailing-whitespace characters are removed. Since multiple OWS characters can exist between the colon and field value, two SP characters after the colon are treated as a single delimiter, and the value ends up as a zero-length string.
Please see #11: Use consistent naming of the specification and highlight this suite aims at v11.
Note I did not do a thorough review of content, so likely there are other inconsistencies I have not seen but at least README and reports (that I could find) are correct.
Please review PR #14 for further improvements to this branch, especially README with more details on how the generator is expected to operate in each mode.
Note this only targets as-is, not extensions/fixes such as #8, #9 or #12. I can provide README updates compliant with the decisions in those issues as needed.
@liamdennehy there are a few false negatives still in this release, but I went ahead and took this and will issue fixes later.
This is the revised code from All tests.
I am currently skipping a few tests: