Question about region & request headers
matthiasriener
PROOP

10 months ago

Hi, I am currently building a webhook feature for my customers, which means that they can add urls in the dashboard and I am calling their urls for certain events.

I noticed that the request headers from my webhook events are from the US, even though I have my server running in EU-West (Metal). Can someone explain, why that is?

Thanks

"headers": {
"host": "recipient-host",
"user-agent": "axios/1.7.9",
"content-length": "1028",
"accept": "application/json, text/plain, /",
"accept-encoding": "gzip, compress, deflate, br",
"content-type": "application/json",
"x-forwarded-for": "208.77.244.8",
"x-forwarded-host": "recipient-host…",
"x-forwarded-proto": "https",
"x-railway-edge": "railway/us-east4",
"x-railway-request-id": "haNgPTbRi6bbv54ivCjCg2074704348",
"x-real-ip": "208.77.244.8",
"x-request-start": "1741343359764"
},

6 Replies

matthiasriener
PROOP

10 months ago

24a11dae-4173-43d8-a81d-a6a15b852ad7


erisa
HOBBY

10 months ago

The x-railway-edge refers to the edge region close to the user that they're connecting through, not the region of your service. If they're connecting from the US, they go via the US edge


matthiasriener
PROOP

10 months ago

I see, I do have other services running in amsterdam which send requests to those servers. The railway-edge in the headers is still US.


erisa
HOBBY

10 months ago

Do you have an example URL that reproduces the issue? I recently made https://function-bun-production-9190.up.railway.app/ for something unrelated I was testing and it shows my header as railway/europe-west4 as expected when I reach it from within Europe



erisa
HOBBY

10 months ago

well the public page doesnt show its in Europe, but it is


Loading...