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
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: