You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If this is meant to become the go-to solution for parsing content-disposition headers, it should ideally support as many optional features as possible.
One that should be relatively easy to support is continuations. See the test case:
For some history, I originally decided not to implement it since it was optional, but thought about doing it anyway, but never did since I wasn't sure if anyone actually used it :)
For curiosity, do you happen to know a system/program that is generating them?
If this is meant to become the go-to solution for parsing content-disposition headers, it should ideally support as many optional features as possible.
One that should be relatively easy to support is continuations. See the test case:
attachment; filename*0="foo."; filename*1="html"
should be parsed as:
but is instead parsed as:
Also note the next test case:
attachment; filename*0*=UTF-8''foo-%c3%a4; filename*1=".html"
This currently results in garbage as the encoding prefix is not parsed.
The text was updated successfully, but these errors were encountered: