Here are two different log entries for Chrome submission of a CSV file. One is on Windows, and another on a Mac:
Minecraft download free full version windows 7. WINDOWS Chrome
MAC OS X Chrome
As you can see, on Mac, the content_type is set correctly to text/csv. On Windows, I get application/octet-stream
This is the SAME file uploaded from two different operating systems, both running Chrome
Upon investigation, I have learned that CSV content-type detection on Windows is FUBAR (seriously FUBAR). I have learned that the suggested fix is for the user to EDIT THEIR WINDOWS REGISTRY (caps added for emphasis). Yes, that is actually what the supposed correctly solutions is.
However, I tried editing my windows registry and it didn't even work (it still uploaded with content-type: octet-stream)
Is there a suggested way to work around this problem? Based on this research, validating on the browser-provided content-type seems to be basically useless, as you are never really guaranteed to a correct content-type.
Join 36 million developers who use GitHub issues to help identify, assign, and keep track of the features and bug fixes your projects need.
Sign up for free See pricing for teams and enterprisesHave 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
consider the following code: I thought shelf would return a response with but I get this:
After digging down in shelf code, it seems that the Is that an intended behavior? If not, would you accept a PR fixing this? |
I opened a PR with a possible fix #53 |
Fixed comparison case for content-type headerdecce6b