Skip to content

Raise a more obvious exception when form data is missing "boundary".#1349

Merged
lovelydinosaur merged 6 commits intoKludex:masterfrom
toxadx:master
Feb 3, 2022
Merged

Raise a more obvious exception when form data is missing "boundary".#1349
lovelydinosaur merged 6 commits intoKludex:masterfrom
toxadx:master

Conversation

@toxadx
Copy link
Contributor

@toxadx toxadx commented Nov 29, 2021

The best strategy is to let KeyError raise when parsing request with missing boundary parameter, so end-user can process KeyError exception in their code.

Closes #1125
Related to #1303

@adriangb adriangb added feature New feature or request refactor Refactor code labels Feb 2, 2022
Copy link
Contributor

@lovelydinosaur lovelydinosaur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Raising a KeyError here isn't perfect, but I'd agree that it's better.
So yup, let's go with this. Thanks!

@lovelydinosaur lovelydinosaur merged commit a6d3d8f into Kludex:master Feb 3, 2022
@lovelydinosaur lovelydinosaur changed the title Raise KeyError at early stage for missing boundary Raise a more obvious exception when form data is missing "boundary". Feb 3, 2022
@Kludex
Copy link
Owner

Kludex commented Feb 3, 2022

We should probably catch that and raise something else from Starlette itself 🤔

@lovelydinosaur
Copy link
Contributor

@Kludex - I'd be okay with that if someone's sufficiently motivated, yup.

(Rolled with this for now, since as @toxadx mentions, this is at least an improvement for now.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature New feature or request refactor Refactor code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Insufficient input validation of content-type 'multipart/form-data'

4 participants