Skip to content

azure_storage_queue uses camelCase query parameters breaking Azurite compatibility #3782

@ollipa

Description

@ollipa

Bug Title

azure_storage_queue: Generated code uses camelCase query parameter names instead of lowercase, breaking Azurite compatibility

Crate Name

azure_storage_queue

Crate Version

0.3.0

Description

The azure_storage_queue crate (v0.3.0) uses camelCase query parameter names (e.g. popReceipt, visibilityTimeout) in HTTP requests, but the Azure Queue Storage REST API specifies lowercase names (popreceipt, visibilitytimeout). This breaks compatibility with Azurite, which is case-sensitive for query parameters.

update_message fails with HTTP 400 against Azurite because both popreceipt and visibilitytimeout are required parameters. Azurite cannot find them due to the case mismatch.

Steps to Reproduce

  // Against Azurite (e.g. docker run mcr.microsoft.com/azure-storage/azurite)
  let client = QueueClient::new(endpoint, queue_name, None, Some(options));

  // Send and receive a message (works)
  client.send_message(msg, None).await?;
  let response = client.receive_messages(Some(recv_options)).await?;

  // Update message visibility (fails with 400)
  client.update_message(&message_id, &pop_receipt, 30, Some(update_options)).await?;
  // Error: HttpResponse { status: BadRequest, error_code: None }

Checklist

Metadata

Metadata

Assignees

No one assigned

    Labels

    customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-triageWorkflow: This is a new issue that needs to be triaged to the appropriate team.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    Projects

    Status

    Untriaged

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions