We document how to set up CORS with a connect-es server in Node.js / Server plugins, and we have very light documentation in Web / Common errors.
Since backend and frontend are often different teams, and since it is not always very obvious which header names need to be allowlisted for multi-protocol support, this documentation does not seem sufficient.
To provide better guidance, we discussed several options, and ended up with the idea to add a top-level section on CORS.
We document how to set up CORS with a connect-es server in Node.js / Server plugins, and we have very light documentation in Web / Common errors.
Since backend and frontend are often different teams, and since it is not always very obvious which header names need to be allowlisted for multi-protocol support, this documentation does not seem sufficient.
To provide better guidance, we discussed several options, and ended up with the idea to add a top-level section on CORS.