electricdusk/rushlink
3
3 Fork 3
Code Issues 21 Pull Requests 2 Releases Activity

Bad Accept header results in internal server error #66

New Issue
Closed
opened 2020-06-28 14:43:55 +02:00 by electricdusk · 2 comments
electricdusk commented 2020-06-28 14:43:55 +02:00
Owner
Copy link
Copy source

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 bugneeds-testgood-beginner-bug labels 2020-06-28 14:43:55 +02:00
electricdusk commented 2020-07-06 17:53:17 +02:00
Author
Owner
Copy link
Copy source

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.
electricdusk commented 2020-07-06 17:56:03 +02:00
Author
Owner
Copy link
Copy source

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 Branch/Tag Specified
Labels
Clear labels
bug
Uninteded behaviour
 feature
Request for a feature to be implemented
 good-beginner-bug
Bugs are probably easy to fix
 needs-test
Needs a regression test
 question
Question about the software
 wontfix
Wont be resolved
No labels bug good-beginner-bug needs-test
Milestone
No items
No Milestone
Assignees
Clear assignees
mara minnozz (Bart Schuurmans) mrngm electricdusk (Amber Sprenkels)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: electricdusk/rushlink#66