You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it's only possible to enable CORS for the dev server via the --cors option. However, with the recent change to enable CORS by default, this option is not really useful anymore. Instead, it should be possible to disable CORS via CLI option to ease the integration of the dev server into local development environments where CORS headers can be problematic.
Suggested solution
The --cors option could either allow a value, like --cors=0, or there could be a new CLI option like --disableCors or similar.
Since v6.0.9, cors is disable by default (meaning only same origin request is allowed), so you can enable it back by --cors. Can you clarify your issue? (Also --cors should already support some variants like --no-cors, --cors=true, --cors=false)
Ah, my bad, you're right. I mixed up what true and false means for cors. But good to know that true/false can be provided via CLI, that's not in the documentation I think.
Description
Currently, it's only possible to enable CORS for the dev server via the
--cors
option. However, with the recent change to enable CORS by default, this option is not really useful anymore. Instead, it should be possible to disable CORS via CLI option to ease the integration of the dev server into local development environments where CORS headers can be problematic.Suggested solution
The
--cors
option could either allow a value, like--cors=0
, or there could be a new CLI option like--disableCors
or similar.Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: