Unexpected behavior after adding support for images without extension

[eortiz-tracktik]

Describe the bug
If for some reason the request is on the Default (base64 encoded JSON) and it get truncated making the JSON invalid, ImageRequest.parseRequestType() will return Thumbor instead of throwing a 400 RequestTypeError, (the new regular expression for matchThumbor added on version v5.2.0 will match the truncated Base64 encoded request)
This will produce at the end a 404 error on the final response, because it will try to find an image that doesn't exists using the first configured bucket and the truncated request as the key.

To Reproduce
truncated/incomplete Default request type:
GET https://serverless-image-handler.your-server.com/eyJidWNrZXQiOiJidWNrZXQiLCJrZXkiOiJpbWFnZS5wbmciLCJlZGl0cyI6eyJyZXNpemUi
Response: 404 Not Found

Expected behavior
Response: 400 RequestTypeError

Please complete the following information about the solution:

• Version: v5.2.0
• Region: all
• Was the solution modified from the version published on this repository?
• If the answer to the previous question was yes, are the changes available on GitHub?
• Have you checked your service quotas for the sevices this solution uses?
• Were there any errors in the CloudWatch Logs?

Screenshots

Additional context

[gattasrikanth]

Thanks for reporting the issue. We are looking into this issue.

[fisenkodv]

@eortiz-tracktik we have updated our solution, the issue has been fixed. If you still see the issue with the latest version (v6.0.0), please feel free to reopen the issue.

You can refer to the recent changes here.