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
Most Actix-using services provide some user configuration via .yaml files or CLI parameters. CORS is a common feature that would require to be configurable by the end user. Yet, the current CORS crate API is somewhat complex when it comes to translating end-user provided configuration into API calls.
I think it will be of great help for developers to suggest some ways of specifying CORS values via configuration and translating them to API calls. Note that this is different than the dynamic configuration via allowed_origin_fn or similar.
Most Actix-using services provide some user configuration via
.yaml
files or CLI parameters. CORS is a common feature that would require to be configurable by the end user. Yet, the current CORS crate API is somewhat complex when it comes to translating end-user provided configuration into API calls.I think it will be of great help for developers to suggest some ways of specifying CORS values via configuration and translating them to API calls. Note that this is different than the dynamic configuration via
allowed_origin_fn
or similar.Configuration Examples
Origins
Methods
// TODO: Rust example
Headers
// TODO: Rust example
The text was updated successfully, but these errors were encountered: