Skip to content
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.

Sign up for GitHub

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

Jump to bottom

azure_storage_blob: No way to access response status code? #2183

Open
exFalso opened this issue Feb 17, 2025 · 1 comment
Open

azure_storage_blob: No way to access response status code? #2183

exFalso opened this issue Feb 17, 2025 · 1 comment
Labels
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

Comments

@exFalso
Copy link

exFalso commented Feb 17, 2025

Hi, when using e.g. PutBlockBlobBuilder it seems PutBlockBlobResponse does not include the response status code. This means for example that when using https://learn.microsoft.com/en-us/rest/api/storageservices/specifying-conditional-headers-for-blob-service-operations there is no way to tell whether a blob has been written or not, as this is communicated with a 200 vs 304 status.

The root cause seems to be that part of the response data is simply discarded when constructing PutBlockBlobResponse. It also seems other operations have the same issue.
@github-project-automation github-project-automation bot moved this to Untriaged in Azure SDK Rust Feb 17, 2025
@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 Feb 17, 2025
@exFalso
Copy link
Author

exFalso commented Feb 17, 2025

Correction: I see the 304 appears as an error, I assume this is the intended behaviour?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
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
Projects
Azure SDK Rust
Status: Untriaged
Milestone
No milestone
Development

No branches or pull requests
1 participant
@exFalso