Azure-docs: The expected 'Content-Type' header that should be returned is application/json.

[taylorchasewhite]

The expected 'Content-Type' header that should be returned is application/json. You may get an error as mentioned below if you use anything else like application/json; charset=utf-8

"Verification of publisher domain failed. Error getting JSON file from https:///.well-known/microsoft-identity-association. The server returned an unexpected content type header value. "

This is a problem. For any application that is deployed use static web files on a deployment service, the developer is unable to modify the response headers. As a result developers cannot verify their publisher domain without _changing their deployment strategy_.

This issue is loosely related to 39665.

Please fix this issue, for the following reasons:

• there is no reason the charset designation should invalidate the hosted JSON file
• it is a outsized cost to the developer to workaround this bug (by changing service providers), as compared to the seemingly small cost to removing the content-type check.
• every developer using a standards compliant web server is going to hit this, and some may not be able to adjust the response headers.

Thank you,

Taylor

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 61edea45-b5d6-05b3-33c3-2265ef8cb309
• Version Independent ID: c7d5813c-5cf1-44c3-88ff-3c194d3e44ad
• Content: Configure an app's publisher domain - Microsoft identity platform
• Content Source: articles/active-directory/develop/howto-configure-publisher-domain.md
• Service: active-directory
• Sub-service: develop
• GitHub Login: @rwike77
• Microsoft Alias: ryanwi

[Snuff-Daddy]

Couldn't agree more. Wasted a bunch of my time.

[SaurabhSharma-MSFT]

@taylorchasewhite Thanks for your feedback! We will investigate and update as appropriate.

[YashYash]

Thank you @taylorchasewhite . We have been waiting on this for a while now. Was just about to create an issue, till I came across yours. Not sure why it was considered ok to close the other issues, when users have been dealing with this for almost a year.

[Wtrapp]

+1

[taylorchasewhite]

Hi @souravmishra-msft & @rwike77, just checking in on this, have you guys decided the direction for this issue (I know addressing it may take some time), but I'd like to know roughly the path forward here.

Thanks!