You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "James Leigh (JIRA)" <ji...@apache.org> on 2013/06/13 20:47:22 UTC
[jira] [Updated] (HTTPCLIENT-1371) Weak ETag Validation is Useful
On PUT With If-Match
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Leigh updated HTTPCLIENT-1371:
------------------------------------
Attachment: HTTPCLIENT-1371.patch
This patch add a CacheConfig options (disabled by default) to allow weak etag validation.
James
> 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: CacheHttpClient Caching components
> Affects Versions: 4.3 Beta2
> Reporter: James Leigh
> Labels: patch
> Fix For: 4.3 Beta3
>
> Attachments: 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org