sentry's baggage header breaks the request

[Wozacosta]

Describe the bug
The header baggage set by sentry (referenced here), when present in the request, breaks it and we get back :

Received an HTTP message that the node could not decode

Steps To Reproduce
Please provide detailed instructions (e.g. command line invocation with parameters) to reproduce the behavior.

Curl with baggage header set:

curl 'https://api.mainnet.hiro.so/v2/fees/transaction' \
  -H 'Content-Type: application/json' \
  -H 'baggage: sentry-environment=production' \
  --data-raw '{"transaction_payload":"000516a66269b5011c8feb0eb8ca6fe39ecef63a8b6c7b000000000000000048686a00000000000000000000000000000000000000000000000000000000000000","estimated_len":180}'

The same without the baggage header, which works:

curl 'https://api.mainnet.hiro.so/v2/fees/transaction' \
  -H 'Content-Type: application/json' \
  --data-raw '{"transaction_payload":"000516a66269b5011c8feb0eb8ca6fe39ecef63a8b6c7b000000000000000048686a00000000000000000000000000000000000000000000000000000000000000","estimated_len":180}'

Expected behavior
When present, the baggage header shouldn't make the node unable to decode the message.

Environment (please complete the following information):

Reproduced on those 2 endpoints: https://stacks-node-api.mainnet.stacks.co endpoint and https://api.mainnet.hiro.so/v2/fees/transaction

Additional context
Please include any relevant stack traces, error messages and logs.

If you are encountering an issue with a smart contract, please include the smart contract code
that demonstrates the issue.

[aldur]

Thank you @Wozacosta! It seems you are issuing the request against the Hiro API. Would it be possible for you to try issuing it against a Stacks node directly?

[Wozacosta]

@aldur Thanks, didn't retry directly against a node as it was identified as being an issue on stacks-blockchain-api instead.
Here is the issue hirosystems/stacks-blockchain-api#2219.

[diwakergupta]

@aldur Thanks, didn't retry directly against a node as it was identified as being an issue on stacks-blockchain-api instead. Here is the issue hirosystems/stacks-blockchain-api#2219.

Turns out it was indeed a bug in stacks-core, fixed by #5904

[stacks-foundation]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.