Comment 2 for bug 1829042

Further testing would indicate this is not a WebOb issue.

The value that is being passed by the client conforms to RFC7231: https://tools.ietf.org/html/rfc7231#section-3.1.1

According to the WebOb issue that was created: https://github.com/Pylons/webob/issues/403
if we want to match on a header that possibly includes key=value pairs behind the content type we have to specifically match on the full value 'application/json;charset=utf-8'

An initial fix would be to split on ; and only pass */* part of the Accept header. We don't seem to care about any other values passed.

A longer term fix would be to compare why certain methods work and others don't and make sure they're all being call consistently.