[
https://issues.apache.org/jira/browse/TS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan M. Carroll resolved TS-4155.
---------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 7.0.0)
There has been much discussion about this. My final view is that this is not a
bug, this is expected behavior. The concensus was that rather than being
strict, ATS should follow the recommendation in the HTTPbis specification and
allow a single LF to terminate a field.
> HTTP header parse should error on LF field terminator
> -----------------------------------------------------
>
> Key: TS-4155
> URL: https://issues.apache.org/jira/browse/TS-4155
> Project: Traffic Server
> Issue Type: Improvement
> Components: HTTP
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
> Labels: incompatible
>
> If an HTTP request header terminates one of the fields with just a line feed
> ATS will parse it as if the header terminated at the end of the previous
> line. I think I understand why this was done but in my opinion that is
> obsolete and ATS should instead generate a parse error. Such a request in my
> reading clearly violates the HTTP specification and should therefore generate
> a parse error. Another option is to treat the line feed as a proper line
> terminator which, while I think would be better than the current behavior
> would still be wrong. General usage has advanced sufficiently that ATS should
> require properly formatted request headers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
