[
https://issues.apache.org/jira/browse/HTTPCLIENT-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683426#comment-13683426
]
Jon Moore commented on HTTPCLIENT-1371:
---------------------------------------
What are people's thoughts about the following paths:
(a) continue adding feature-specific options for various differences between
RFC2616 and the evolving HTTPbis spec
(b) having a single "follow HTTPbis" flag to opt into all the features at once
My suggestion would be to follow (a) until the new RFC was published, then
deprecate those and replace them with (b). Other comments?
> 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-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]
