[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleg Kalnichevski resolved HTTPCLIENT-1190.
-------------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 4.3 Final)
                   4.3 Alpha1

Francois-Xavier,

I believe the problem has been resolved as a result of refactoring of the 
HttpClient execution pipeline. I am planing to post a summary of the most 
important design and API changes to the dev list in the coming. However, as far 
as this issue is concerned, what is important is that the execution pipeline 
can now be assembled dynamically and the caching executor is now inserted after 
the protocol executor, which enables the cache to work directly with fully 
assembled request messages (except for authentication headers that are 
populated by the main executor) and original, unaltered response messages. 
'Vary: Cookie' should now be working right of the box.

Could you please get the latest SVN snapshot off the trunk and take it for a 
spin? Please note you will need to be using the new (undeprecated) APIs in 
order to exercise the improved execution pipeline. Deprecated classes are most 
left unaltered for the compatibility sake.

Also feel free to critique the new APIs and express your ideas as to what might 
be improved or done better / differently.

Oleg  
                
> "Vary: Cookie" header not working
> ---------------------------------
>
>                 Key: HTTPCLIENT-1190
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1190
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: Cache
>    Affects Versions: 4.1.3, Snapshot
>            Reporter: Francois-Xavier Bonnet
>             Fix For: 4.3 Alpha1
>
>
> When using a CachingHttpClient with a target server that uses a cookie and 
> "Vary: Cookie" header in order to have different variants depending on the 
> value of the cookie, there is only one variant stored in the cache and sent 
> whatever the value of the cookie.
> The problems comes from the cookie header that does not really exist in the 
> request, it is just created by the HttpClient while executing the request. As 
> a result the variant key is always "{cookie=}".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Reply via email to