From cbf6ae9723500155a92b265e2b17176b5686dfd0 Mon Sep 17 00:00:00 2001 From: Anton Date: Fri, 20 Mar 2026 11:02:18 +0300 Subject: [PATCH] fix(beacon): forward Content-Type header from upstream responses (#806) 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 --- .../dshackle/upstream/beaconchain/BeaconChainSpecific.kt | 1 + 1 file changed, 1 insertion(+) diff --git a/src/main/kotlin/io/emeraldpay/dshackle/upstream/beaconchain/BeaconChainSpecific.kt b/src/main/kotlin/io/emeraldpay/dshackle/upstream/beaconchain/BeaconChainSpecific.kt index c1e6672b..c756cc29 100644 --- a/src/main/kotlin/io/emeraldpay/dshackle/upstream/beaconchain/BeaconChainSpecific.kt +++ b/src/main/kotlin/io/emeraldpay/dshackle/upstream/beaconchain/BeaconChainSpecific.kt @@ -123,6 +123,7 @@ object BeaconChainSpecific : AbstractPollChainSpecific() { } override fun getResponseHeadersToForward(): List = listOf( + "Content-Type", "Eth-Consensus-Version", "Eth-Consensus-Finalized", "Eth-Execution-Optimistic",