Skip to content
This repository has been archived by the owner on Oct 17, 2024. It is now read-only.

Setup secure Access-Control-Allow-Origin for production #3

Open
ebsaral opened this issue Dec 25, 2021 · 0 comments
Open

Setup secure Access-Control-Allow-Origin for production #3

ebsaral opened this issue Dec 25, 2021 · 0 comments
Assignees
@ebsaral
Labels
enhancement New feature or request

Comments

@ebsaral
Copy link
Contributor

ebsaral commented Dec 25, 2021

Situation

Currently, Access-Control-Allow-Origin is set to '*' in the template which means that the service is public. This is a security issue.

Requirements

  • Setup production domain (at least provide an option) for Access-Control-Allow-Origin
@ebsaral ebsaral added bug Something isn't working enhancement New feature or request labels Dec 25, 2021
@ebsaral ebsaral self-assigned this Dec 25, 2021
@ebsaral ebsaral changed the title Setup correct Access-Control-Allow-Origin for production Setup secure Access-Control-Allow-Origin for production Dec 25, 2021
@ebsaral ebsaral removed the bug Something isn't working label Jan 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ebsaral ebsaral

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ebsaral