Fix CORS wildcard subdomain documentation #36321
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #36192
The documentation incorrectly stated that
SetIsOriginAllowedToAllowWildcardSubdomains()should be called with origins without the*wildcard character. This caused subdomain matching to fail.Changes
WithOrigins("https://example.com")toWithOrigins("https://*.example.com")in all samples usingSetIsOriginAllowedToAllowWildcardSubdomains()*wildcard character" with "The*wildcard character must be included in the origin to enable wildcard subdomain matching"ai-usage: ai-assisted, updatedms.dateto 11/10/2025Before (incorrect - no subdomains matched):
After (correct - matches
api.example.com,subdomain.example.com, etc.):Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.
Internal previews