This repository has been archived by the owner on Apr 22, 2021. It is now read-only.
Fix: NULL MimeType when sending files without extension #270
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
laurent-clouet
pushed a commit
that referenced
this pull request
Oct 21, 2020
laurent-clouet
pushed a commit
that referenced
this pull request
Oct 21, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
To automatically detect the MimeType of the file being sent to the server, the app makes a call to the
Files.probeContentTypemethod. ProbeContentType uses the file extension to assign the correct MimeType. As files with error log sent to the server don't have any extension (they have a farm_XXXXXXXXXXXXX pattern) the probeContentType method generates a NULL MimeType.As logs are plain text files, this PR adds the .txt extension to the log files generated to generate the proper MimeType.