Skip to content

Fix Azure Blob SAS signatures for encoded object paths - #2181

Open
nightcityblade wants to merge 1 commit into
apache:trunkfrom
nightcityblade:fix/issue-1805
Open

Fix Azure Blob SAS signatures for encoded object paths#2181
nightcityblade wants to merge 1 commit into
apache:trunkfrom
nightcityblade:fix/issue-1805

Conversation

@nightcityblade

Copy link
Copy Markdown

Fix Azure Blob SAS signatures for encoded object paths

Description

Azure Blob SAS canonical resources must use the decoded object path when the
signature is calculated, while the returned URL must remain percent-encoded.
Decode the path only for the string-to-sign and add regression coverage for an
object name containing a space.

Fixes #1805.

For more information on contributing, please see Contributing
section of our documentation.

Status

  • done, ready for review

Checklist (tick everything that applies)

  • Code linting (black --check, isort --check-only, and focused flake8 passed)
  • Documentation — N/A; this corrects existing signed-URL behavior without changing the public API
  • Tests (pytest -q libcloud/test/storage/test_azure_blobs.py: 86 passed)
  • ICLA — N/A; this is a focused two-file bug fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Azure Blob Storage get_object_cdn_url can't handle files with spaces.

1 participant