Bad Accept header results in internal server error #66

Closed
opened 1 year ago by dsprenkels · 2 comments
Owner

See https://hashru.link/Qd_z.

In this case, the client (presumably) provided a bad Accept header. In this case, rushlink should error with an 400 Bad Request error. However, it fails with an internal server error.

See <https://hashru.link/Qd_z>. In this case, the client (presumably) provided a bad `Accept` header. In this case, rushlink should error with an `400 Bad Request` error. However, it fails with an internal server error.
dsprenkels added the
bug
needs-test
good-beginner-bug
labels 1 year ago
Poster
Owner

This error seems to occur when the client's Accept value has a leading white space. By the spec, this should be trimmed however.

This error seems to occur when the client's `Accept` value has a leading white space. By the spec, this should be trimmed however.
Poster
Owner

However, a media-range value '*' is still invalid, I think.

However, a `media-range` value `'*'` is still invalid, I think.
dsprenkels closed this issue 1 year ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.