a month ago
Hi Railway team,
Your edge router returns a 502 ("upstream error") for any request whose path ends with "%" or with "%" followed by a single hex digit (an incomplete percent-encoding). The request never reaches our application.
Examples (custom domain proxied by Cloudflare; the 502 comes from Railway's edge, not from our app):
https://www.finozio.com/fr/offres% → 502
https://www.finozio.com/fr/%E0%A4%A → 502
https://www.finozio.com/fr/offres%25 → 404 from our app (correct)
It reproduces without any application at all: on a *.up.railway.app subdomain that has no service, /abc%2 → 502 while /abc → 404.
Expected behaviour: a 400 Bad Request, or forwarding the request to the application so it can return its own 404.
Impact: a visitor who follows a malformed link sees a generic "502 Bad gateway" page instead of our 404, which looks like an outage.
Thanks!
1 Reply
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We reproduced this on our side. A request to an unassigned *.up.railway.app hostname whose path ends in an incomplete percent-encoding (such as /abc%2) gets a 502 straight from our edge, so the request never reaches a service at all.
Your application isn't causing these 502s. Our edge returns them before routing the request, and nothing in your service configuration changes that today. Paths with valid encoding, like the %25 example, are forwarded to your app normally.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago