You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Parse media types in the Content-Type header correctly (#964)
* Parse media types in the Content-Type header correctly
Ensures that Content-Type calculation is based on the extracted Content-Type
from the media type, rather than the raw Media Type value. Changes behavior
in the Thrift HTTP endpoint and Zipkin V1 and V2 HTTP endpoints.
Signed-off-by: Chris Zelenak <chris@zelenak.me>
* Ensure Content-Type parse errors are visible
Make sure that callers are informed of errors if they provide an
incorrect media type.
Signed-off-by: Chris Zelenak <chris@zelenak.me>
{body: []byte("[]"), code: http.StatusBadRequest, headers: map[string]string{"Content-Encoding": "gzip"}, resBody: "Unable to process request body: unexpected EOF\n"},
251
267
{body: []byte("not good"), code: http.StatusBadRequest, resBody: "Unable to process request body: invalid character 'o' in literal null (expecting 'u')\n"},
252
268
{body: []byte("[{}]"), code: http.StatusBadRequest, resBody: "Unable to process request body: validation failure list:\nid in body is required\ntraceId in body is required\n"},
0 commit comments