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

Jon Moore resolved HTTPCLIENT-1371.
-----------------------------------

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

This has been fixed in SVN trunk for the synchronous httpclient and hence 
should go out in 4.3 Final. I have created HTTPASYNC-53 to track exposing this 
option in the async client. @James: would you mind re-posting your async patch 
there?
                
> Weak ETag Validation is Useful On PUT With If-Match
> ---------------------------------------------------
>
>                 Key: HTTPCLIENT-1371
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1371
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpCache
>    Affects Versions: 4.3 Beta2
>            Reporter: James Leigh
>              Labels: patch
>             Fix For: 4.3 Final
>
>         Attachments: HTTPCLIENT-1371-httpasyncclient.patch, 
> HTTPCLIENT-1371.patch
>
>
> RFC2616 explicitly prohibits the use of weak validators in non-GET requests, 
> however, the HTTPbis working group says while the limitation for weak 
> validators on ranged requests makes sense, weak ETag validation is useful on 
> full non-GET requests; e.g., PUT with If-Match. When HTTPbis working group 
> publishes a clarification to HTTP/1.1, weak validators will be allow for PUT 
> and DELETE requests. HttpClient should make this an config option until 
> HTTP/1.1 is officially clarified.
> http://trac.tools.ietf.org/wg/httpbis/trac/ticket/116

--
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