Mobile errors on iOS with 302 redirects

jonathan-heaney
HOBBY

a year ago

I have a weird issue with my deployment - on iOS, any 302 redirect requests result in a "This site can't be reached" error. You can reproduce this error by visiting my website:

web-production-4a6f.up.railway.app/redirect_fail/

That link will successfully redirect to the homepage on desktop or on Android, but on an iPhone or iPad, it will produce the "This site can't be reached" error.

No other request types result in this connection error on iOS.

I redeployed my app to Render, and the issue disappeared. So I know that it's related to Railway in some way, but I'm not sure why.

Solved

14 Replies

a year ago

Unfortunately I am unable to help as i don't have an IOS device, please explain the issue more in depth.


eric2024
PRO

a year ago

I am also seeing this problem. Redirects are working on other browsers but not WebKit. It happens on my iPad and the Windows minibrowser.exe WebKit build. I don’t have any other Apple devices to test.

On minibrower.exe, a redirect results in a messagebox appearing with this message:

Stream error in the HTTP/2 framing layer
Error Code: 92
Domain: CurlErrorDomain

Attachments


a year ago

Try disabling the edge proxy, waiting 10 minutes and test again.


eric2024
PRO

a year ago

That solved the problem


a year ago

This thread has been escalated to the Railway team.

Status changed to Awaiting Railway Response brody 11 months ago


a year ago

Where are you making the request from? Mobile carrier, wifi?


Status changed to Awaiting User Response railway[bot] 11 months ago


eric2024
PRO

a year ago

I was making the request over wifi. It happened with 302 responses and also when the site was misconfigured and returning a 500. It only happens with WebKit, other browsers I tested (on the same network) worked fine. Unlike the OP, the problem persisted when I tried to redeploy the site


Status changed to Awaiting Railway Response railway[bot] 11 months ago


@jonathan-heaney please let us know if the suggested path from @brody addresses the issue you're experiencing here:

Try disabling the edge proxy, waiting 10 minutes and test again.


Status changed to Awaiting User Response railway[bot] 11 months ago


jonathan-heaney
HOBBY

a year ago

Disabling the edge proxy worked for me as well, thank you for the help!


Status changed to Awaiting Railway Response railway[bot] 11 months ago


Status changed to Solved christian 11 months ago


Status changed to Open brody 11 months ago


a year ago

Hey jonathan, I have tried to make a reproducible example but I was unable to as the code I wrote to send a 302 redirect worked without issue on a webkit based browser when deployed to Railway with the edge proxy enabled, but when you first sent your link I was able to confirm the error on the same webkit based browser.

So would you mind switching back on the edge-proxy so I can test again?


jonathan-heaney
HOBBY

a year ago

Sure Brody, I just switched the edge-proxy back on and confirmed the error came back on my iOS device.


a year ago

Thank you, can you tell me more about the app itself? what is handling the actual 302 response, Django + Gunicorn, express? FastAPI + Uvicorn?


Status changed to Solved brody 11 months ago


Status changed to Open brody 11 months ago


jonathan-heaney
HOBBY

a year ago

Django + Gunicorn


a year ago

Looks like my update didn't post, but I was able to come up with a minimal reproducible example, and the team has implemented and shipped a fix already.


jonathan-heaney
HOBBY

a year ago

Thank you!!


Status changed to Solved brody 11 months ago