rambulance: Mime::Type::InvalidMimeType
Hi @yuki24 !
I bumped into a new issue after upgrading to rails 6, producing Mime::Type::InvalidMimeType error.
To reproduce, e.g.: curl -D - -H "Accept: image/apng*/*" https://example.com
I have a feeling however that this happens before rambulance gets a chance to do anything? even if I add config.rescue_responses = { "Mime::Type::InvalidMimeType" => :not_acceptable } it doesn’t seem to catch it…
Any tips/thoughts? 😃 thanks in advance!
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 20 (9 by maintainers)
Commits related to this issue
- Sanitize the HTTTP Accept header value if the client sends an invalid value fixes #53 — committed to yuki24/rambulance by yuki24 4 years ago
- refs #53 test with invalid content-type header * added a test to simulate the issue * unfortunately, not entirely sure how to catch this exception and handle it yet ... — committed to gingerlime/rambulance by deleted user 4 years ago
- Handle invalid content-type headers (#55) * refs #53 test with invalid content-type header * added a test to simulate the issue * unfortunately, not entirely sure how to catch this exception and ha... — committed to yuki24/rambulance by deleted user 4 years ago
Let’s move this conversation to https://github.com/yuki24/rambulance/pull/55#issuecomment-634820099
Thanks a lot, @yuki24. So glad to see this resolved. I really appreciate it!
Apologies for the delay. I should be able to look into it on Saturday.
Hey @gingerlime, sorry I didn’t have the time to do so last weekend. Hopefully I can do this tomorrow or the day after.