fix(admin): correct CORS configuration guidance DEV-2471#7284
Open
jnm wants to merge 3 commits into
Open
Conversation
…and add a validator to prevent standard ports 80 or 443 from being added, since those are never to be sent by clients per spec
Member
Author
|
@greptileai please review |
Contributor
Member
Author
|
@greptileai please review again |
jnm
marked this pull request as ready for review
July 20, 2026 21:53
platreth
self-requested a review
July 21, 2026 07:04
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🗒️ Checklist
for user-facing doc changes create a Zulip thread at#Support Docs Updates, if any<type>(<scope>)<!>: <title> DEV-1234Front endand/orBack endorworkflow👷 Description for instance maintainers
Fix CORS configuration guidance in the Django Admin interface so that it correctly says NOT to add default ports 80 or 443 for HTTP or HTTPS, respectively. Add a validator to prevent saving new origins if this guidance is not heeded.
👀 Preview steps
/admin/external_integrations/corsmodel/add/http://some-origin:80andhttps://some-origin:443: both should failhttp://some-origin:443: it should succeed