Skip to content

Escaping failure on blob DELETE #24562

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
yonderblue opened this issue May 5, 2025 · 1 comment
Open

Escaping failure on blob DELETE #24562

yonderblue opened this issue May 5, 2025 · 1 comment
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Storage Storage Service (Queues, Blobs, Files)

Comments

@yonderblue
Copy link

yonderblue commented May 5, 2025

Bug Report

go.mod has:

github.com/Azure/azure-sdk-for-go/sdk/azcore v1.18.0
github.com/Azure/azure-sdk-for-go/sdk/storage/azblob v1.6.1
github.com/Azure/azure-sdk-for-go/sdk/internal v1.11.1 // indirect
  • What happened?

    Tried to delete a nonexistent blob with a tab in the blob name, only to get:

DELETE https://***.blob.core.windows.net/***/test/8d2c49bac5508e462cfe/1b4065bd5a50da115809	1a72b71e016e13da895d
--------------------------------------------------------------------------------
RESPONSE 400: 400 The requested URI does not represent any resource on the server.
ERROR CODE: InvalidUri
--------------------------------------------------------------------------------
<?xml version="1.0" encoding="utf-8"?>
<Error><Code>InvalidUri</Code><Message>The requested URI does not represent any resource on the server.
RequestId:b1db98f2-001e-0068-16da-bd1294000000
Time:2025-05-05T16:25:02.6234612Z</Message></Error>
--------------------------------------------------------------------------------
	type=*exported.ResponseError
  • What did you expect or want to happen?

    A 404.

  • How can we reproduce it?

    By putting a tab character anywhere in the blob name, path encoded. The above was setup like:

blobURL := containerURL + "/" + prefix + "/" + url.PathEscape(blobName)
client := blockblob.NewClientWithSharedKeyCredential(blobURL, cred, o)

and before the client.Delete(), the client.URL() looked like:

https://***.blob.core.windows.net/***/test/8d2c49bac5508e462cfe/1b4065bd5a50da115809%091a72b71e016e13da895d
  • Anything we should know about your environment.

    This was a test case, but we do have a file in azure that somehow got a tab in the blob name, which we cannot now access.

@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels May 5, 2025
@jhendrixMSFT jhendrixMSFT added the Storage Storage Service (Queues, Blobs, Files) label May 5, 2025
@github-actions github-actions bot removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label May 5, 2025
@RickWinter RickWinter added bug This issue requires a change to an existing behavior in the product in order to be resolved. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels May 6, 2025
@github-actions github-actions bot added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label May 6, 2025
@yonderblue
Copy link
Author

@tanyasethi-msft @vibhansa-msft Was hoping if you knew whether this would be looked at soon or might it be a while? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

5 participants