Loop redirection between two URLs

[yin1999]

Summary

Got a loop redirection between the following URLs:

• https://developer.mozilla.org/en-US/docs/Web/API/Window/performance
• https://developer.mozilla.org/en-US/docs/Web/API/performance_property

This may be related to mdn/content#33339.

URL

• https://developer.mozilla.org/en-US/docs/Web/API/Window/performance
• https://developer.mozilla.org/en-US/docs/Web/API/performance_property

Reproduction steps

1. Open browser with devtools opened in Network panel
2. navigator to https://developer.mozilla.org/en-US/docs/Web/API/Window/performance
3. See network logs

Note, clearing website data cannot resolve this problem, it seems to be a server-side problem.

Expected behavior

Won't get a loop redirection, and this page can be opened as normal.

Actual behavior

Got a loop redirection.

Device

Desktop

Browser

Chrome

Browser version

Stable

Operating system

Windows

Screenshot

Anything else?

No response

Validations

• I have read the Community Participation Guidelines.
• I have verified that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• I have checked that this is a concrete bug. For Q&A open a GitHub Discussion.

[bsmth]

Already discussed on Discord, but adding a note to say I can't reproduce this, it may have been caches being invalidated during deploy.

[bsmth]

For some more context, the problem appears to be from here:

mdn/content@dfb8c72#diff-afe010c4707d10d488b1e1c050b3298da03267dec0abca46d6d444b2ae8774a5L10890

We had a situation with these changes in the redirects file:

- /en-US/docs/Web/API/Window/performance /en-US/docs/Web/API/performance_property
+ /en-US/docs/Web/API/performance_property /en-US/docs/Web/API/Window/performance

And the old & new redirects were both active at the same time.

[caugner]

I cannot reproduce the issue, and indeed this indicates a temporary caching issue. We tell browsers to cache permanent redirects for moved pages for 30 days (which we could reduce), and our CDN only caches them for 30 minutes.

[argl]

Also not able to reproduce here. I am closing this issue, if this persists beyond the ususal cache timeouts, feel free to re-open.