ok2c commented on PR #900:
URL:
https://github.com/apache/httpcomponents-client/pull/900#issuecomment-6295689602
@dxbjavid @arturobernalg Can we take a step back and take at the problem
from a broader view.
But first, I really do not like this
> On the classic transport the header is serialised from the raw buffer of
the BufferedHeader rather than its getValue()
Does that mean the async transport behaves differently in that regard? If
so, this needs to be fixed first and foremost.
Then, is this problem really specific to RFC6265 cookie spec? Should not it
be fixed at at the HTTP/1.1 connection layer for headers of any type?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]