diff options
| author | Edouard CHIN <edouard.chin@shopify.com> | 2019-03-25 21:51:22 +0100 |
|---|---|---|
| committer | Edouard CHIN <edouard.chin@shopify.com> | 2019-03-26 02:03:47 +0100 |
| commit | 378b4fedb1d4b55e642e82d0a7b273803118ca30 (patch) | |
| tree | 7d6b9d4297d5e7ad1bfe728504142efc266140db /yarn.lock | |
| parent | 15ca8ad0c1e94d11d0deb02535bc286e077d43ce (diff) | |
| download | rails-378b4fedb1d4b55e642e82d0a7b273803118ca30.tar.gz rails-378b4fedb1d4b55e642e82d0a7b273803118ca30.tar.bz2 rails-378b4fedb1d4b55e642e82d0a7b273803118ca30.zip | |
Add the `Mime::Type::InvalidMimeType` error in the default rescue_response:
- https://github.com/rails/rails/pull/35604 introduced a vulnerability fix
to raise an error in case the `HTTP_ACCEPT` headers contains malformated
mime type.
This will cause applications to throw a 500 if a User Agent sends an
invalid header.
This PR adds the `InvalidMimeType` in the default `rescue_responses` from
the ExceptionWrapper and will return a 406. I looked up the HTTP/1.1
RFC and it doesn't stand what should be returned when the UA
sends malformated mime type. Decided to get 406 as it seemed to be the
status the better suited for this.
Diffstat (limited to 'yarn.lock')
0 files changed, 0 insertions, 0 deletions