Add configuration for allowed origins #1355
Labels
area/api
Related to the external API component
area/cli
Related to the CLI binary
area/config
Related to configuration
feature
New feature or request
Milestone
Currently, if users start developing web apps that access an instance of DefraDB directly, they will be confronted with CORS errors from the browser because the app and DefraDB will operate on different ports locally and possibly different domains publicly.
We should allow configuration of the HTTP API with a list of allowed origins.
Note:
WithAllowedOrigins
already exists on the API but we need to add the configuration through the CLI and config files.The text was updated successfully, but these errors were encountered: