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
Apparently, it's hard to properly use non-ASCII headers to set the filename, and it's preferred to do it by appending the filename to the URL: http://stackoverflow.com/a/1365186/248065
EDIT: https://tools.ietf.org/html/rfc5987 is also relevant, it seems to be the most-supported alternative to using an actual filename in the URL.
I wouldn't classify this as 'low-hanging fruit' anymore...
Thanks for the info. I think it's still low hanging fruit, albeit slightly less low hanging. The definition of LHF for these purposes is something like "interesting but relatively narrow problem in scope, with few knock-on dependencies and relatively localized in the codebase"... i.e., easy to pick up without knowing the codebase, even if it's hard to solve.
Non-ASCII characters in Content-Disposition (i.e. attachment filenames) break HTTP server. Example: "Þetta er skráarnafn sem brýtur HTTP þjóninn.odt"
The text was updated successfully, but these errors were encountered: