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
There are currently two edge cases where the request may fail where it could have passed. These edge cases can be handled by simply moving the policies around.
Case 1:
This case is related to the StorageHeadersPolicy. In this policy the current_time is set. This policy is currently ran before the retry policy. This means that if the retry policy was retrying and the time period has exceeded 15 min difference between the pre-established current_time it would fail as it would be considered an outdated request on the server side.
Solution Move the headers policy after RetryPolicy, i.e, current time would get reset with every retry.
Case 2:
This case is related to the StorageCredentialPolicy, moving it after the retry policy means that the TokenCredential can be refreshed if it has expired while retrying.
The text was updated successfully, but these errors were encountered:
tasherif-msft
added
Client
This issue points to a problem in the data-plane of the library.
Storage
Storage Service (Queues, Blobs, Files)
and removed
Mgmt
This issue is related to a management-plane library.
labels
Oct 22, 2020
There are currently two edge cases where the request may fail where it could have passed. These edge cases can be handled by simply moving the policies around.
Case 1:
This case is related to the
StorageHeadersPolicy
. In this policy the current_time is set. This policy is currently ran before the retry policy. This means that if the retry policy was retrying and the time period has exceeded 15 min difference between the pre-established current_time it would fail as it would be considered an outdated request on the server side.Solution Move the headers policy after RetryPolicy, i.e, current time would get reset with every retry.
Case 2:
This case is related to the StorageCredentialPolicy, moving it after the retry policy means that the TokenCredential can be refreshed if it has expired while retrying.
The text was updated successfully, but these errors were encountered: