StakeSquid/dshackle
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(beacon): forward Content-Type header from upstream responses (#806)

Browse Source 
Add Content-Type to the beacon chain response headers whitelist.
Without this, REST endpoints returning SSZ binary data (e.g.
/eth/v2/debug/beacon/states) are mislabeled as application/json
by dproxy, breaking client-side parsing.

Companion fix: drpcorg/dproxy#2348
This commit is contained in:
Anton
2026-03-20 11:02:18 +03:00
committed by GitHub
parent 56f6bb3a7b
commit cbf6ae9723
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
src/main/kotlin/io/emeraldpay/dshackle/upstream/beaconchain/BeaconChainSpecific.kt
View File

@@ -123,6 +123,7 @@ object BeaconChainSpecific : AbstractPollChainSpecific() {
} }
override fun getResponseHeadersToForward(): List<String> = listOf( override fun getResponseHeadersToForward(): List<String> = listOf(
"Content-Type",
"Eth-Consensus-Version", "Eth-Consensus-Version",
"Eth-Consensus-Finalized", "Eth-Consensus-Finalized",
"Eth-Execution-Optimistic", "Eth-Execution-Optimistic",