Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CORS whitelist as env variable #1797

Open
JensWinkler91 opened this issue Oct 11, 2023 · 0 comments
Open

Add CORS whitelist as env variable #1797

JensWinkler91 opened this issue Oct 11, 2023 · 0 comments

Comments

@JensWinkler91
Copy link

Is your feature request related to a problem? Please describe.

I've found this old issue about cors #950.
The suggested solution there is to use a proxy server to access the api via browser.

In my case that would mean that i have to implement a new backend instance or configure a proxy server that has the only purpose to forward my request from localhost:3000 to localhost:8080/v1/update.

As watchtower provide an API i think there should be a possibility to define a CORS whitelist.

Describe the solution you'd like

I'd be nice if we could use a variable .e.g. WATCHTOWER_HTTP_CORS_ORIGINS to allow one or multiple origins.

As env variable:
WATCHTOWER_HTTP_CORS_ORIGINS=localhost:3000, localhost:4000

Describe alternatives you've considered

I don't know other alternatives.

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant