[
https://issues.apache.org/jira/browse/HTTPASYNC-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754860#comment-13754860
]
Jon Moore edited comment on HTTPASYNC-53 at 8/30/13 4:21 PM:
-------------------------------------------------------------
This just requires a simple fix in the facade constructor to look for and use
the option flag. Fix is blocked waiting on the 4.3 Final release of httpclient
(should be coming imminently), as the option won't be available on CacheConfig
until that release happens.
was (Author: jonm):
This just requires a simple fix in the facade constructor to look for and
use the option flag. Fix is blocked waiting on the 4.3 Final release of
httpclient (should be coming imminently).
> Weak ETag Validation is Useful on PUT with If-Match
> ---------------------------------------------------
>
> Key: HTTPASYNC-53
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-53
> Project: HttpComponents HttpAsyncClient
> Issue Type: Improvement
> Affects Versions: 4.0-beta4
> Reporter: Jon Moore
> Fix For: 4.0-beta5
>
>
> The HTTPbis working group has identified that the restrictions on the use of
> weak etags are too strong in RFC2616. A config option has been added to the
> synchronous httpclient to permit opting into the HTTPbis behavior here; this
> should also be made available to the async caching client.
> See HTTPCLIENT-1371.
--
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]
