[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917580#action_12917580
 ] 

Oleg Kalnichevski commented on HTTPCLIENT-1006:
-----------------------------------------------

> What would be the difference between BrowserCompatSpec and "IE/Firefox cookie 
> spec"?

BrowserCompatSpec was never meant to emulate a particular browser or browser 
version. It is basically a collection of workarounds for crazy stuff common to 
most of so called popular browser. If that is not enough in your case, you may 
want to consider creating cookie specs that emulate the exact behavior of a 
specific browser or browser version (IE55, IE60, FF3 and so on)

> I don't understand the ambiguity you mention

I do not think I can help here, then

> Where do the expectations in 
> org.apache.http.impl.cookie.TestBrowserCompatSpec come from? 

Accumulated over years based on users' feedback and bug reports

> Btw: what have you done to the HttpClient jar that forbid Eclipse to set 
> breakpoints? 

Huh? Torture and intimidation, I guess.

Oleg

> BrowserCompatSpec: don't trim " around cookie value
> ---------------------------------------------------
>
>                 Key: HTTPCLIENT-1006
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1006
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpCookie
>    Affects Versions: 4.0.2
>            Reporter: Marc Guillemot
>
> If the server sends a cookie header like:
> Set-Cookie: first="hello world"
> then HttpClient parses it as cookie with value >hello world<, wrongly 
> removing the leading and trailing quotes. The incorrect quote removal occurs 
> in BasicHeaderValueParser.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to