Railway is overwriting an important header [X-Request-Id]

I'm encountering a challenge integrating Mercado Pago Webhooks on Railway. Their validation process requires specific headers, but some of these headers are being overwritten by Railway's infrastructure.

My API is built with NestJS, and everything functions correctly when tested in other environments. I've pinpointed that Railway is modifying the X-Request-Id header, which is crucial for validating webhook authenticity (see: https://www.mercadopago.com.br/developers/en/docs/your-integrations/notifications/webhooks#bookmark_2._validate_notification_origin)

Is there a way to configure Railway to preserve these headers or any workarounds to ensure successful Mercado Pago webhook integration?

Solved

3 Replies

2 years ago

Hi,

The team is currently out for a long weekend, but we've shared this with our infra engineers so they can look into a solution tomorrow
Best,
Nico


Status changed to Awaiting User Response Railway over 1 year ago


Thanks for helping! Okay! I'll be waiting for news. Greetings!


Status changed to Awaiting Railway Response Railway over 1 year ago


2 years ago

Hello! we now use X-Railway-Request-Id


Status changed to Awaiting User Response Railway over 1 year ago


Status changed to Solved brody over 1 year ago


Loading...