Context
The desktop Local Proxy currently permits wildcard browser origins when CORS is enabled. The proxy also falls back to Maple's saved credential when an incoming request does not provide its own Authorization header.
That combination creates a billing and security boundary worth treating explicitly: a browser origin that can reach the loopback endpoint under the browser's local-network policy may be able to make inference requests using the saved credential.
Scope
- Confirm behavior across supported browsers and their local-network protections.
- Decide whether CORS should remain enabled by default for new configurations.
- Define migration or consent behavior for existing saved configurations.
- Consider origin restrictions or requiring an explicit inbound credential whenever CORS is enabled.
- Keep user-facing warnings and setup guidance aligned with the chosen policy.
This should be designed and reviewed separately from PR #652, which should remain a documentation and presentation change.
Context
The desktop Local Proxy currently permits wildcard browser origins when CORS is enabled. The proxy also falls back to Maple's saved credential when an incoming request does not provide its own Authorization header.
That combination creates a billing and security boundary worth treating explicitly: a browser origin that can reach the loopback endpoint under the browser's local-network policy may be able to make inference requests using the saved credential.
Scope
This should be designed and reviewed separately from PR #652, which should remain a documentation and presentation change.