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 was archived by the owner on Jul 5, 2020. It is now read-only.
The headers conflict with Azure Storage request signing process (#640). As a result Storage responds with 403 to all requests and issue is extremely hard to debug.
We have a special configuration to disable injection of the headers into requests to storage endpoints, however, we cannot guarantee that proper config is always applied.
Removing support for these headers would eliminate the issue without any configuration and save users a lot of pain with debugging it.
Before starting the implementation we need to:
[x] - clarify if headers are used by JS SDK: No
[x] - if JS SDK still emits x-ms headers, perhaps we can still remove them on injection side.
The headers were used for correlation and were deprecated with
(all of them released ~ a year ago)
The headers conflict with Azure Storage request signing process (#640). As a result Storage responds with 403 to all requests and issue is extremely hard to debug.
We have a special configuration to disable injection of the headers into requests to storage endpoints, however, we cannot guarantee that proper config is always applied.
Removing support for these headers would eliminate the issue without any configuration and save users a lot of pain with debugging it.
Before starting the implementation we need to:
[x] - clarify if headers are used by JS SDK: No
[x] - if JS SDK still emits x-ms headers, perhaps we can still remove them on injection side.