fix: support more uncommon file types for attachments #520
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
It seems that the fix implemented in #514 was not enough to solve the issue with attachment uploads of uncommon file types. We decided to not pass the
Content-Type
and let the backend set it, but the backend is still returning a 406 response for some file types (for example for a.pcap
file).The only fix we can implement on our side is to use a library to determine the correct mime type based on the file extension. I used the mime library, which adds ~10K to the
shared-bundle.js
file when gzipped.Checklist