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-1353) 303 Redirects Should be Cacheable
Date Tue, 14 May 2013 19:19:16 GMT

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

James Leigh commented on HTTPCLIENT-1353:

The document is a draft. The latest HTTP/1.1 draft is available here: http://tools.ietf.org/wg/httpbis/

The draft was started in 2007 and has see a lot of progress over the last year and will (soon)
supersede RFC 2616 as the definition of HTTP/1.1.

I believe Chromium can cache 303 responses.
> 303 Redirects Should be Cacheable
> ---------------------------------
>                 Key: HTTPCLIENT-1353
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1353
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>    Affects Versions: 4.2.5
>            Reporter: James Leigh
>         Attachments: HTTPCLIENT-1353.patch
> The current HTTP draft indicates that 303 is actually cacheable after all, if indicated
by the Cache-Control header.
> http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-latest.html#rfc.issue.i70-cacheability-of-303
> org.apache.http.impl.client.cache.ResponseCachingPolicy should be changed so that 303
(See Other) is not included in the uncacheableStatuses.

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

View raw message