Fix origin validation for production domains #127
Merged
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.
Problem: Same-origin requests from production domains (mcp.socket.dev, mcp.socket-staging.dev) were being rejected because browsers don't send an Origin header for same-origin requests, and the validation only allowed missing origins for localhost hosts.
Solution: Extended the Host header validation to also accept production domain hostnames, allowing same-origin requests from production environments to work correctly.
Changes:
Version bump: 0.0.15 → 0.0.16