Application Octet Stream Utf8
Step 2: Run ProduKey.exe file to view your Windows 10 product key. Extract the zip file to a new folder to get ProduKey.exe file.
Here are two different log entries for Chrome submission of a CSV file. One is on Windows, and another on a Mac:
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.
Here are two different log entries for Chrome submission of a CSV file. One is on Windows, and another on a Mac:
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.