You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
I'm receiving a success response when inserting a message that differs from the documented response. It includes the account details and the shared key and 56k of queue/request related metadata.
I'm really just looking for confirmation this response is expected. If so I can take appropriate steps to resolve any issues. But I can't find it documented anywhere so it's a concern particularly because of the shared keys exposed in the response.
How can we reproduce the problem in the simplest way?
Insert a message to a queue using sendMessage from the sdk
Have you found a mitigation/solution?
Yes and no. I need to know if the response is expected. I'm sending messages from Azure PlayFab event cloudscripts with a 1 sec execution time limit. My operations are based in West Europe and I've had to create an additional storage account in the same region as PlayFab's servers, West US. I've optimized the request from PlayFab shaving off 400ms, if I can do the same with the queue response the issue is resolved for me. If I can't I may need to pop something into a table instead.
Cheers
Steve
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Which service(blob, file, queue, table) does this issue concern?
Storage queues
Which version of the SDK was used?
Node: @azure/storage-queue 12.4.0
.Net: Azure Storage Queues 12.6.1
Which platform are you using? (ex: .NET Core 2.1)
.Net Core 3.1
What problem was encountered?
I'm receiving a success response when inserting a message that differs from the documented response. It includes the account details and the shared key and 56k of queue/request related metadata.
I'm really just looking for confirmation this response is expected. If so I can take appropriate steps to resolve any issues. But I can't find it documented anywhere so it's a concern particularly because of the shared keys exposed in the response.
How can we reproduce the problem in the simplest way?
Insert a message to a queue using sendMessage from the sdk
Have you found a mitigation/solution?
Yes and no. I need to know if the response is expected. I'm sending messages from Azure PlayFab event cloudscripts with a 1 sec execution time limit. My operations are based in West Europe and I've had to create an additional storage account in the same region as PlayFab's servers, West US. I've optimized the request from PlayFab shaving off 400ms, if I can do the same with the queue response the issue is resolved for me. If I can't I may need to pop something into a table instead.
Cheers
Steve
The text was updated successfully, but these errors were encountered: