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
Can you please confirm that the client request id won’t be repeated on retry too? Because client request id is not involved in HMAC signing, I am not sure if it’s fixed as part of the signing issue.
This is the real log of the response that the customer reported.
So looks like this is what happened
The SDK sent the initial request with x-ms-client-request-id: 0453ca94-5026-4fa0-aeee-ea38de69cfd5
The request is throttled and the server responded 429 (this is the first log I shared earlier)
The SDK retry for 429 and sent a request with x-ms-client-request-id: 0453ca94-5026-4fa0-aeee-ea38de69cfd5, 0453ca94-5026-4fa0-aeee-ea38de69cfd5
The server responded 401 likely due to the SDK HMAC signing issue you mentioned
The SDK won’t retry for 401 and the exception bubbled up.
Looks like when SDK retries, it doubles the client request id string. Is this fixed already?
The text was updated successfully, but these errors were encountered:
Action here is to add test to verify this doesn't happen in the current release.
annelo-msft
changed the title
Ensure client request id is added only once on retries.
Ensure client request id and other headers are added only once on retries.
Dec 4, 2019
Per Partner request:
Can you please confirm that the client request id won’t be repeated on retry too? Because client request id is not involved in HMAC signing, I am not sure if it’s fixed as part of the signing issue.
This is the real log of the response that the customer reported.
So looks like this is what happened
Looks like when SDK retries, it doubles the client request id string. Is this fixed already?
The text was updated successfully, but these errors were encountered: