Opened 9 years ago

Closed 8 years ago

#285 closed design (fixed)

Strength of requirements on Accept re: 406

Reported by: mnot@… Owned by: julian.reschke@…
Priority: normal Milestone: 16
Component: p3-payload Severity: Active WG Document
Keywords: Cc:

Description

The definition of the 406 status code allows servers to override the clients' preferences:

Note: HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept header fields sent in the request. In some cases, this might even be preferable to sending a 406 response. User agents are encouraged to inspect the header fields of an incoming response to determine if it is acceptable.

However, this isn't really reflected in the Accept-* header requirements; e.g., for Accept:

If an Accept header field is present, and if the server cannot send a response which is acceptable according to the combined Accept field value, then the server SHOULD send a 406 (Not Acceptable) response.

The SHOULD here needs to either be contextualised (perhaps by pasting in a similar note), and/or relaxed to a MAY. Likewise for other Accept-* headers.

Attachments (1)

285.diff (5.2 KB) - added by julian.reschke@… 8 years ago.
proposed patch for p2 and p3

Download all attachments as: .zip

Change History (7)

comment:1 Changed 8 years ago by mnot@…

  • Owner set to mnot@…
  • Status changed from new to assigned

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

  • Milestone changed from unassigned to 16
  • Owner changed from mnot@… to julian.reschke@…
  • Status changed from assigned to new

Changed 8 years ago by julian.reschke@…

proposed patch for p2 and p3

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

From [1335]:

Tune strength of requirements on Accept re: 406 (see #285)

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

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

comment:5 Changed 8 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:6 Changed 8 years ago by mnot@…

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