-
-
Notifications
You must be signed in to change notification settings - Fork 343
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
mov file recognized differently in browser and in server code #211
Comments
BTW, after reverting to 10.8.0 both server and client result is: {
"ext": "mov",
"mime": "video/quicktime"
} |
// @stroncium |
@sindresorhus I have no idea how to test it in browser, and I suppose it will be a waste of time to learn how is building for browsers done just for this issue, but while running the code in my mind I've come up with #214, which fixes an issue existing in nodejs, and there is really high chance it is the issue @yoavain-sundaysky hit in browser. |
Sorry for the late response. |
I'm using file-type in client code to determine content-type to use in request to server.
I'm using file-type in server code to make sure the content I get matches the content-type.
I used to get the same result, but today, after updating from 10.8.0 to 11.0.0 I got 2 different results:
Client:
Server:
Attached the file:
640x360_vid.zip
The text was updated successfully, but these errors were encountered: