Paul Hauner a3704b971e Support pre-flight CORS check (#1772) ... ## Issue Addressed - Resolves #1766 ## Proposed Changes - Use the `warp::filters::cors` filter instead of our work-around. ## Additional Info It's not trivial to enable/disable `cors` using `warp`, since using `routes.with(cors)` changes the type of `routes`. This makes it difficult to apply/not apply cors at runtime. My solution has been to *always* use the `warp::filters::cors` wrapper but when cors should be disabled, just pass the HTTP server listen address as the only permissible origin.		2020-10-22 04:47:27 +00:00
..
src	Support pre-flight CORS check (#1772)	2020-10-22 04:47:27 +00:00
tests	Node endpoints (#1778)	2020-10-22 02:59:42 +00:00
Cargo.toml	Support pre-flight CORS check (#1772)	2020-10-22 04:47:27 +00:00