[
https://issues.apache.org/jira/browse/HTTPCLIENT-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657400#comment-13657400
]
James Leigh edited comment on HTTPCLIENT-1353 at 5/14/13 7:18 PM:
------------------------------------------------------------------
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 seen 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.
was (Author: jamesrdf):
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: [email protected]
For additional commands, e-mail: [email protected]
