Handle invalid MIME type on multipart upload
What does this MR do and why?
What
Handle ProtocolError for multipart upload.
Why
When a user sends an invalid Content-Disposition
Go sends a malformed
MIME header
line
and we end up returning a 500 error instead of a 400 error.
Since this is an invalid value that our user sends we need to return a 400 instead of 500, so it doesn't attribute to our error rate, and to indicate the user did something wrong.
Reference: #432533 (closed)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.