Opened 8 years ago

Closed 7 years ago

#310 closed design (fixed)

clarify 303 redirect on HEAD

Reported by: julian.reschke@… Owned by: draft-ietf-httpbis-p2-semantics@…
Priority: normal Milestone: 17
Component: p2-semantics Severity: Active WG Document
Keywords: Cc:

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 (5)

comment:1 Changed 8 years ago by julian.reschke@…

From [1421]:

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

comment:2 Changed 8 years ago by julian.reschke@…

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

comment:3 Changed 8 years ago by julian.reschke@…

See also [1429]

comment:4 Changed 7 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:5 Changed 7 years ago by mnot@…

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