Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sentry's baggage header breaks the request #5832

Open
Wozacosta opened this issue Feb 13, 2025 · 1 comment
Open

sentry's baggage header breaks the request #5832

Wozacosta opened this issue Feb 13, 2025 · 1 comment

Comments

@Wozacosta
Copy link

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
Copy link
Contributor

aldur commented Feb 13, 2025

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Status: 🆕 New
Development

No branches or pull requests

2 participants