Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[app-configuration] Use the x-ms-useragent header when in the browser #6528

Conversation

richardpark-msft
Copy link
Member

@richardpark-msft richardpark-msft commented Dec 12, 2019

The User-Agent header is not alterable in the browser so we need to fallback to the x-ms-useragent header so we can still send the same information.

This also requires a change on the service backend which won't take effect until January but we will start sending the correct header on next release of the SDK.

Fixes #5810 (for the SDK-side).

(service issue to accept the new header)
Azure/AppConfiguration#217

Richard Park (WDG/ES) and others added 2 commits December 12, 2019 09:37
Also, whitelisted the x-ms-useragent header for
logging as well since it's the User-Agent header
we use for browsers.
@richardpark-msft richardpark-msft requested review from bennage and chradek and removed request for bennage December 12, 2019 17:44
Copy link
Member Author

@richardpark-msft richardpark-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just replying.

@ramya-rao-a
Copy link
Contributor

@bterlson, @daviwil Can you take a look at this as it touches the land of policies and core?

Copy link
Contributor

@daviwil daviwil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes seem fine to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[App Configuration] CORS Issue with header "x-ms-command-name"
4 participants