hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Leigh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCLIENT-1371) Weak ETag Validation is Useful On PUT With If-Match
Date Fri, 14 Jun 2013 15:47:20 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683460#comment-13683460
] 

James Leigh commented on HTTPCLIENT-1371:
-----------------------------------------

Make sense. Once we have multiple HTTP/1.1 RFCs it makes sense to use the RFC as the choice
(as is done with http-cookie config options). However, once RFC2616 is revised and clarified,
who is going to want to use the obsolete version? The new RFC that HTTPbis is working better
reflects how HTTP/1.1 is actually used today.

The biggest changes to HTTP clients are backwards compatible: allow relative location headers,
allow 303 responses to be cached, allow weak etag in non-GET requests, expect 100-continue
in the request maybe be ignored, it is okay to send the same credentials following a 403 response,
and proxies no longer have to process Warning headers.

http://trac.tools.ietf.org/wg/httpbis/trac/report/20

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-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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message