fix content type issue defaulting to octet-stream #224
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 of the Change
This PR ensures that the blob is being sent to the storage with the proper content type as we're experiencing issues with some containers defaulting the content type to
application/octet-stream
With this fix, we're not leaving the default content type but sending the file content type directly to the
createBlockBlob()
function through the$options
parametersFixes #210
How to test the Change
Changelog Entry
Credits
@hugosolar
Checklist: