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
These two response headers are useful for the service team to debug and diagnose issues, and hence it is requested that we do log them.
x-vss-e2eid
x-msedge-ref
We decided, other than logging them, to also add these header values to the exception message that is thrown, so they are always visible, even with logging disabled.
Given our logged headers are based on an allow list, currently these two headers are REDACTED.
Add two headers for Piplines to the allow list (best effort), and log the values of those unconditionally in exceptions. The headers do not contain secrets; the error case is the most important thing, but having them in normal logs is nice.
Add two headers for Piplines to the allow list (best effort), and log the values of those unconditionally in exceptions. The headers do not contain secrets; the error case is the most important thing, but having them in normal logs is nice.
* FixAzure#41986
Add header to cause pipelines OIDC endpoint not to redirect.
* FixAzure#41871
Add two headers for Piplines to the allow list (best effort), and log the values of those unconditionally in exceptions. The headers do not contain secrets; the error case is the most important thing, but having them in normal logs is nice.
* pr feedback
* more pr feedback fixes
* mark fields private
These two response headers are useful for the service team to debug and diagnose issues, and hence it is requested that we do log them.
We decided, other than logging them, to also add these header values to the exception message that is thrown, so they are always visible, even with logging disabled.
Given our logged headers are based on an allow list, currently these two headers are REDACTED.
azure-sdk-for-java/sdk/core/azure-core/src/main/java/com/azure/core/http/policy/HttpLogOptions.java
Lines 69 to 74 in 6673a1c
The text was updated successfully, but these errors were encountered: