Guard against nil value for x-ms-blob-content-type - #212
Open
Seth Boyles (sethboyles) wants to merge 5 commits into
Open
Guard against nil value for x-ms-blob-content-type#212Seth Boyles (sethboyles) wants to merge 5 commits into
Seth Boyles (sethboyles) wants to merge 5 commits into
Conversation
Resolve dependency issue for Nokogiri/Faraday
Version and Doc change for 2.0.3/2.0.4 release.
Author
|
Kan Tang (@katmsft) apologies if I am tagging the wrong person. Is it possible to get this merged & released at some point? It is blocking us from getting https://github.com/fog/fog-azure-rm/ upgraded to the newer versions of azure-storage-ruby. Thanks |
This was referenced Feb 16, 2022
|
Hi Kan Tang (@katmsft), Just checking in on this. |
Author
|
Yang Xia (@yaxia) Kan Tang (@katmsft) Could we get this looked at? |
5 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR just adds usage of
StorageService.with_headerforx-ms-content-type, so it behaves the same as other headers.Without this, we are having issue correctly generating the authorization signature: