Aha: the problem seems to occur only on pages which include unicode characters in the url. At least, I havenāt been able to reproduce the problem on other pages so far.
Is it possible that some servers on the CDN are not handling unicode chars properly?
My other sites on netlify without unicode in the urls work fine. I also created a copy of this problem site replacing the Unicode characters with non Unicode and that one has been fine for the last 15 hours as well.
I experienced something similar today and was just about to write a post when I saw this.
I was testing my app on my mothers old laptop. When I opened Firefox DevTools I saw 21 (!) redirects (301) after each other, ending up with a warning ātoo many redirectsā. Refresh did not help. The URL includes some swedish characters Ć„, Ƥ, ƶ. https://cv3-dev.netlify.app/mƶrbylĆ„nga/
The following redirects had the same response headers except the x-nf-request-id 01FJ6M45EHMTZ42YEAKPA30NEB 01FJ6M45H906HD8GQRF0PFSDNM 01FJ6M45MN39TT96MSN9JSS7B9 01FJ6M45TN0G0Z44D3XCBXH7BM
ā¦
20 retries before giving up (21 total) Age also incremented somewhat (not every retry, ended up on 345)
Suddenly after a new refresh it started working again:
But another IP 206.189.50.215:443 instead of previous 3.67.153.12:443
@hrishikesh, a local deployment does not reproduce the issue after extensive testing.
A 98% cache hit rate sounds normal to me, and the fact that the problem occurs on both uncached and cached hits indicates to me that the issue might be elsewhere. My two cents.
To reproduce these, have you tried to access these from an Android?
@einar good to know! Curious, how long have you had these urls deployed for?
@hrishikesh wondering if this is now considered to be a bug and how this issue will be prioritized and worked on? Guidance on this question would be helpful. Thank you for looking into it.
Thank you for sharing! Weāre filing this for our developers to take a look at. We can see the problem exists so they can investigate it on their end.
Weād appreciate your patience till this gets solved.
Iāve checked twice so far, and itās worked fine. Since the problem is intermittent, Iāll check a few more times later today and tomorrow and get back.
Sure, happy to speak to that to the extent of our knowledge.
Seems like this was a bug in our redirect handling code around unicode-containing rules and potentially even redirects for URLās that simply had unicode in them that matched a redirect rule.
You experienced it partially since our CDN was running some proposed updates on some nodes which failed in the way you observed, and which we applied a fix for while we were working on another issue. We think the scope of the problem was (again, only on a few CDN nodes) from about 11 through 18 oct or thereabouts.