fix: add localnet proxy to add Access-Control-Allow-Private-Network header #523
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.
Google Chrome is slowly introducing more restrictions on sites which make calls to private network resources.
See https://developer.chrome.com/blog/private-network-access-preflight
This impacts tools like Dappflow.
This PR adds a proxy container to LocalNet and attaches the correct headers to ensure the pre flight CORS request that Chrome sends will succeed.
This PR fixes #524