* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #70 (closed design: fixed)

Opened 7 years ago

Last modified 7 years ago

Cacheability of 303 response

Reported by: mnot@pobox.com Owned by: julian.reschke@gmx.de
Priority: Milestone: 03
Component: p2-semantics Severity:
Keywords: Cc:
Origin: http://lists.w3.org/Archives/Public/www-tag/2007Jul/0035.html

Description

Section 10.3.4 says that 303 See Other is not cacheable.

Change History

comment:1 Changed 7 years ago by mnot@pobox.com

Proposal as per http://www.w3.org/mid/1FEA959C-00A9-4DE9-9597-B3338A6C915F@gbiv.com

10.3.4. 303 See Other

The server directs the user agent to a different resource, indicated by a URI in the Location header field, that provides an indirect response to the original request. The user agent MAY perform a GET request on the URI in the Location field in order to obtain a representation corresponding to the response, be redirected again, or end with an error status. The Location URI is not a substitute reference for the originally requested resource.

The 303 status is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action to redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response in a form that can be separately identified, bookmarked, and cached independent of the original request.

A 303 response to a GET request indicates that the requested resource does not have a representation of its own that can be transferred by the server over HTTP. The Location URI indicates a resource that is descriptive of the requested resource such that the follow-on representation may be useful without implying that that it adequately represents the previously requested resource. Note that answers to the questions of what can be represented, what representations are adequate, and what might be a useful description are outside the scope of HTTP and thus entirely determined by the resource owner(s).

A 303 response SHOULD NOT be cached unless it is indicated as cacheable by Cache-Control or Expires header fields. Except for responses to a HEAD request, the entity of a 303 response SHOULD contain a short hypertext note with a hyperlink to the Location URI.

comment:2 Changed 7 years ago by mnot@pobox.com

  • Component set to cache
  • Milestone set to unassigned

comment:3 Changed 7 years ago by julian.reschke@gmx.de

  • Owner set to julian.reschke@gmx.de
  • Component changed from p6-cache to p2-semantics

comment:4 Changed 7 years ago by julian.reschke@gmx.de

  • Status changed from new to assigned

See [242].

comment:5 Changed 7 years ago by mnot@pobox.com

  • Status changed from assigned to closed
  • Resolution set to fixed
  • Milestone changed from unassigned to 03

comment:6 Changed 7 years ago by julian.reschke@gmx.de

From [243]:

Fix typo (relates to #70).

Note: See TracTickets for help on using tickets.