-
Notifications
You must be signed in to change notification settings - Fork 232
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
gateway: add CORS to specs #423
Labels
dif/expert
Extensive knowledge (implications, ramifications) required
effort/days
Estimated to take multiple days, but less than a week
kind/maintenance
Work required to avoid breaking changes or harm to project's status quo
P1
High: Likely tackled by core team if no one steps up
Comments
3 tasks
lidel
added
dif/expert
Extensive knowledge (implications, ramifications) required
P1
High: Likely tackled by core team if no one steps up
kind/maintenance
Work required to avoid breaking changes or harm to project's status quo
effort/days
Estimated to take multiple days, but less than a week
and removed
need/triage
Needs initial labeling and prioritization
labels
Jun 26, 2023
This was referenced Jun 27, 2023
2 tasks
Open
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dif/expert
Extensive knowledge (implications, ramifications) required
effort/days
Estimated to take multiple days, but less than a week
kind/maintenance
Work required to avoid breaking changes or harm to project's status quo
P1
High: Likely tackled by core team if no one steps up
Currently, gateway specs leave CORS to implementers, but various things will not work on public gateways (path, subdomain, and trustless) unless relaxed CORS is set, like we do in
boxo/gateway
.Tasks
The text was updated successfully, but these errors were encountered: