fix: change default rpc config + upgrade CORS library #1118
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.
Description
This PR introduces several changes to the default JSON-RPC config of the Gno node:
*
) origin requests by default. The reasoning behind this is that local development setups that require the RPC layer will have their requests rejected by the CORS policy, and will require a custom RPC config to be specified to the node. This is more of a convenience on the side of development, as production Gno RPC setups will have a concrete RPC configuration that is more limitedOPTIONS
requests (preflight requests) in the default configurationHow can I test this out?
Essentially, you can run the local node with the default RPC params, and try to do an HTTP request from a frontend application:
Example error:
Contributors' checklist...
BREAKING CHANGE: xxx
message was included in the description