Railway is retrying after HTTP Status 500 response | Railway | Page 1

copper lintel Mar 30, 2023, 6:15 AM

#

So I have a proxy service on my API and sometimes the response is HTTP 500 and after that the Railway Platform retries the request, I tried it on localhost and the behaviour is not the same.

merry topazBOT Mar 30, 2023, 6:15 AM

#

Project ID: 26e0a7d6-19ec-418b-9d32-2b16f4b4d21e

#

You might find these helpful:

copper lintel Mar 30, 2023, 6:15 AM

#

ProjectID: 26e0a7d6-19ec-418b-9d32-2b16f4b4d21e

minor axle Mar 30, 2023, 6:25 AM

#

yep, this is not an unheard of behavior for a proxy to do

copper lintel Mar 30, 2023, 6:25 AM

#

Hey @minor axle thanks for the fast response

#

There is anyway to configure this? I really need this feature to not retry

minor axle Mar 30, 2023, 6:26 AM

#

no problem, and just for future reference #🛂｜readme #5

#

there is not, you can return a different code than 500

copper lintel Mar 30, 2023, 6:28 AM

#

I see it, so it will occur for the whole 500 - 599 HTTP status

minor axle Mar 30, 2023, 6:28 AM

#

I can't confirm that, I only know it will retry for 500, but that does sound plausible

copper lintel Mar 30, 2023, 6:29 AM

#

Thanks man I'll figure it out something, already help me a lot

#Railway is retrying after HTTP Status 500 response