Skip to content

Commit d712ba9

Browse files
authored
Update howto-configure-publisher-domain.md
Updating note for JSON deserialization to represent recent changes to functionality. charset=utf-8 is now a supported content header, alongside the empty string.
1 parent 05466e8 commit d712ba9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/active-directory/develop/howto-configure-publisher-domain.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ You're not required to maintain the resources that are used for verification aft
116116
If your tenant has verified domains, in the **Select a verified domain** dropdown, select one of the domains.
117117

118118
> [!NOTE]
119-
> The expected `Content-Type` header that should return is `application/json`. If you use any other header, like `application/json; charset=utf-8`, you might see this error message:
119+
> Content will be interpreted as UTF-8 JSON for deserialization. Supported `Content-Type` headers that should return are `application/json`, `application/json; charset=utf-8`, or ` `. If you use any other header, you might see this error message:
120120
>
121121
> `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.`
122122
>

0 commit comments

Comments
 (0)