Roland Weber wrote:
Oleg Kalnichevski (JIRA) wrote:
Why would _anyone_ _ever_ want a different implementation
of the header continuation parsing?
Because they are asked to implement a proxy that maintains
header continuation line breaks when forwarding headers?
What for? If people want to do something completely bizarre, I do not
see a point in going out of our way to help them
This patch adds an _unnecessary_ layer of complexity to a performance
critical execution path and buys us absolutely nothing.
Oleg
Plug in a parser that inserts line breaks instead of spaces
into the headers, and a header value parser that treats
line breaks as whitespace. A formatter that recognizes
line breaks is not needed if you use CRLF in the value.
Making minimal changes to passing data is hardly a far-fetched
requirement. There's also the variant "document everything
that gets changed", followed by a sequence of "is that really
necessary" discussions.
cheers,
Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
