-
-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support filename*
#52
Comments
Because C# has encoded |
Sure, I don't see why we can't do this. Happy to accept a PR. |
I'm working with an Axum application (holiday coding 🎄 🎉) and hit a similar issue as this when a client sent I'm thinking it may not be correct behavior for clients to set extended field names but some definitely do this. See RFC 7578 Section 4.2 and this rationale. I'm also thinking it's okay to be permissive about it on the server side. I dove down the rabbit hole and tackled parsing extended fields (i.e. I added tests for the new functionality, fixed a Cargo conditional compilation warning, and moved things from See my branch here: master...soundslocke:multer:extended-content-disposition-field-parsing Would you still be happy to have a PR for this @SergioBenitez? |
Is it possiable to support field
filename*
?https://datatracker.ietf.org/doc/html/rfc6266#section-5
The text was updated successfully, but these errors were encountered: