Allow CORS and a default 200 response at the root #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This enables CORs and will respond with a 200 at the root of the server. Why does this matter?
Here's a PoC I whipped up that relies primarily on a local dat-gateway when available, but falls back to a public gateway when not available locally.
The PoC Bunsen app served up through a public gateway:
The PoC Bunsen app serving up the requested dat through the local gateway because it is available:
The PoC Bunsen app serving up the requested dat through the public gateway because the local gateway is not available:
The CORs and the response at the root is important because before setting the iframe to the gateway, we do a preflight fetch to see if there is a 127.0.01:3000 gateway available.