hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Moore (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HTTPCLIENT-998) cache should use both Last-Modified and ETag for validations when available
Date Tue, 21 Sep 2010 15:56:34 GMT

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

Jonathan Moore updated HTTPCLIENT-998:

    Attachment: use-all-validators.patch

The attached patch addresses this issue, and is contributed to the ASF with the permission
of my employer.

> cache should use both Last-Modified and ETag for validations when available
> ---------------------------------------------------------------------------
>                 Key: HTTPCLIENT-998
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-998
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: Cache
>    Affects Versions: 4.1 Alpha2
>            Reporter: Jonathan Moore
>         Attachments: use-all-validators.patch
> This is a protocol recommendation:
> "[HTTP/1.1 clients], if both an entity tag and a Last-Modified value have been provided
by the origin server, SHOULD use both validators in cache-conditional requests. This allows
both HTTP/1.0 and HTTP/1.1 caches to respond appropriately."
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.3.4
> The current implementation only uses the ETag when conditionally validating an entry,
so HTTP/1.0 caches can't currently reply to us with a 304 (Not Modified), even if that would
be appropriate.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

View raw message