Opened 10 years ago

Closed 10 years ago

#43 closed enhancement (fixed)

HSTS: cite draft-reschke-http-status-308 and mention HTTP status code 308 ?

Reported by: jeff.hodges@… Owned by: draft-ietf-websec-strict-transport-sec@…
Priority: minor Milestone:
Component: strict-transport-sec Version:
Severity: In WG Last Call Keywords:
Cc:

Description

[ this issue is forked from ​http://trac.tools.ietf.org/wg/websec/trac/ticket/40 ]

​https://www.ietf.org/mail-archive/web/websec/current/msg01108.html StPeter?

<snip/>

Section 7.2

Does is make sense to mention that status code 308 might be
appropriate in certain circumstances? See draft-reschke-http-status-308.

Change History (2)

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

In a perfect world yes :-) But 308 is new, experimental, not well supported, and introduces an indirect dependency on HTTPbis.

Proposal: rephrase the normative requirement so that sending 308 instead of 301 is *possible* (say "permanent redirect", and list 301 as example).

comment:2 Changed 10 years ago by jeff.hodges@…

  • Resolution set to fixed
  • Status changed from new to closed

fixed in -07

Note: See TracTickets for help on using tickets.