Repository navigation
Fix: set CORS_ORIGINS so the web frontend can log in - #24
Merged
Merged
Conversation
app.core.config.Settings.cors_origins defaults to http://localhost:3000 (the local dev value) and nothing in production ever overrode it, so every cross-origin request from the actual deployed frontend -- https://demo.altsmanager.org, a different origin than https://api.altsmanager.org -- was rejected by the browser at the CORS preflight stage. This is why the admin panel (same-origin, server- rendered form) could log in fine while the frontend's login page (a cross-origin JS fetch) could not, with the same credentials. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Summary
Test plan
🤖 Generated with Claude Code