Bad Accept header results in internal server error #66

Closed
opened 2020-06-28 14:43:55 +02:00 by electricdusk · 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.
electricdusk added the
bug
needs-test
good-beginner-bug
labels 2020-06-28 14:43:55 +02:00
Author
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.
Author
Owner

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

However, a `media-range` value `'*'` is still invalid, I think.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: electricdusk/rushlink#66
No description provided.