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

Ticket #332 (closed design: fixed)

Opened 2 years ago

Last modified 2 years ago

relax requirements on hypertext in 3/4/5xx error responses

Reported by: julian.reschke@gmx.de Owned by: julian.reschke@gmx.de
Priority: normal Milestone: 19
Component: p2-semantics Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/dv83h79kvnsahi4asf0t49d7phbgcd734q@hive.bjoern.hoehrmann.de

Description (last modified by julian.reschke@gmx.de) (diff)

Bjoern H. notes:

The fallback requirement

Unless the request method was HEAD, the representation of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s), since most user agents do not understand the 308 status code yet. Therefore, the note SHOULD contain the information necessary for a user to repeat the original request on the new URI.

strikes me as a bad idea. It's a transient problem so it should be conditioned and how widely supported this is, and it's only useful if you have some HTML implementation on the other end or an interactive user; a web service not meant for interactive use where you can be sure that the code is supported, because, say, you control the client, is unaffected, and if you add that as another exception you basically end up saying you can do this so your site works better with legacy clients in some situations and making your site work good is probably a good idea, so I'd prefer just saying that. I don't really want to ponder whether I should send this hypertext response in response to an OPTIONS request in 2015, just because your specification says I should.

Attachments

332.diff (2.4 KB) - added by julian.reschke@gmx.de 2 years ago.
proposed change for p2

Change History

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

  • Description modified (diff)

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

From [1508]:

Align description of 307 with 302 (307 isn't "new" anymore) (related to #332)

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

From [1515]:

State that the Content-Type describes the payload only one (related to #332)

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

From [1516]:

demote SHOULD for payload on 201; it doesn't make sense for PUT (related to #332)

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

  • Owner changed from draft-ietf-httpbis-p2-semantics@tools.ietf.org to julian.reschke@gmx.de
  • Milestone changed from unassigned to 19

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

  • Status changed from new to assigned

Changed 2 years ago by julian.reschke@gmx.de

proposed change for p2

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

From [1521]:

relax payload requirements for 301/302/307 (addresses #332)

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

  • Status changed from assigned to closed
  • Resolution set to incorporated

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

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:10 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.