a3704b971e
## 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.
19 lines
680 B
TOML
19 lines
680 B
TOML
[package]
|
|
name = "warp_utils"
|
|
version = "0.1.0"
|
|
authors = ["Paul Hauner <paul@paulhauner.com>"]
|
|
edition = "2018"
|
|
|
|
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
|
|
|
|
[dependencies]
|
|
warp = { git = "https://github.com/paulhauner/warp", branch = "cors-wildcard" }
|
|
eth2 = { path = "../eth2" }
|
|
types = { path = "../../consensus/types" }
|
|
beacon_chain = { path = "../../beacon_node/beacon_chain" }
|
|
state_processing = { path = "../../consensus/state_processing" }
|
|
safe_arith = { path = "../../consensus/safe_arith" }
|
|
serde = { version = "1.0.116", features = ["derive"] }
|
|
tokio = { version = "0.2.22", features = ["sync"] }
|
|
headers = "0.3.2"
|