1

Resolved

Content negotiation returns 406 on missing accept header

description

Using DefaultContentNegotiator (at least with excludematchontype = true) returns a 406 for all requests without an accept header.

Http spec says that a missing accept header means the client will accept anything, i.e., everything is acceptable.

Web api should respect the spec.

comments