Problem: Missing boundary in multipart form data causes unhandled KeyError instead of a proper 400 response
Problem: Missing boundary in multipart form data causes unhandled KeyError instead of a proper 400 response: a task in LegoFlow-SWE (Harbor dataset). When a client sends a multipart/form-data request without the required boundary parameter in the Content-Type header, Starlette raises a KeyError…
The task
When a client sends a `multipart/form-data` request without the required `boundary` parameter in the `Content-Type` header, Starlette raises a `KeyError` with the message `'boundary missing'` instead of returning an HTTP 400 Bad Request response. This results in an unhandled server error (500) rather than a…
Part of Lego-X/LegoFlow-SWE.