Samit,
I think it is a good idea to fail on the smallest entity possible. That
means if the overall Set-Cookie2 header is malformed and we are unable
to parse it, then discard it.
If however only one of the cookies is malformed (like missing path
attribute) but cookies can be told appart correctly, only reject that
one cookie.
Odi
Samit Jain wrote:
Hi,
Currently HttpClient rejects the Set-Cookie header entirely if there
is a problem in parsing one of the cookies in the header. I doubt if
it is the right behavior for old or new specification. I think if
there is a problem in parsing a cookie, only that cookie should be
rejected. Any suggestions on this? I am going to implement it this way
for RFC 2965.
-Samit
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
