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

Ticket #310 (closed design: fixed)

Opened 3 years ago

Last modified 2 years ago

clarify 303 redirect on HEAD

Reported by: julian.reschke@gmx.de Owned by: draft-ietf-httpbis-p2-semantics@tools.ietf.org
Priority: normal Milestone: 17
Component: p2-semantics Severity: Active WG Document
Keywords: Cc:
Origin: http:///www.w3.org/mid/89EF3427-888C-45A8-8652-965E4CA52F9D@mnot.net

Description

There's some confusion about what we expect when a HEAD request is redirected with a 303.

The client didn't ask for the payload, so rewriting to GET (even when done correctly with respect to payload handling) seems to be inferior than to stick to HEAD.

Change History

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

From [1421]:

rephrase 303 description (now doesn't imply GET is needed anymore) (see #310)

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

  • Status changed from new to closed
  • Resolution set to incorporated
  • Milestone changed from unassigned to 17

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

See also [1429]

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

  • Status changed from closed to reopened
  • Resolution incorporated deleted

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

  • Status changed from reopened to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.