hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Moore (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCLIENT-1353) 303 Redirects Should be Cacheable
Date Wed, 15 May 2013 11:15:16 GMT

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

Jon Moore commented on HTTPCLIENT-1353:

I think it's important to note that HTTP/1.1bis is not really meant to introduce protocol-level
changes in RFC 2616 but rather to clarify the way it is currently implemented and used. If
you read the discussion on this issue it's clear that this particular behavior (303 MUST NOT
be cached) was an unintentional bug. That said, RFC 2616 is quite clear and it's possible
someone has relied on this behavior.

The current patch would have the effect, I believe, of making a 303 only cacheable if it was
marked explicitly so with Cache-Control or Expires. I would be supportive of this patch if
it we could add some unit tests specifying and verifying this new behavior for 303s. I'd also
like to see a configuration option that allows for this on an opt-in basis, at least until
HTTP/1.1bis is officially published.

@Oleg: would that address your concerns?

@James: would you be willing to update your patch in that way?

> 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
>             Fix For: Future
>         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