This repository was archived by the owner on Oct 14, 2026. It is now read-only.
Repository navigation
fix: restore legacy /docs/api-auth/* redirects removed in #2002 - #2044
Merged
Merged
Conversation
#2002 (old redirect cleanup, first pass) deleted all 53 redirects sourced under /docs/api-auth/* as low-traffic/unindexed. A customer reported two of these as hard 404s this week: /docs/api-auth/tutorials/adoption/api-tokens /docs/api-auth/tutorials/adoption/refresh-tokens Their application code and error messages link directly to these paths, so GSC/page-view data wouldn't have caught this - the traffic isn't organic search, it's inbound from external code depending on the URL staying stable. Restored all 53 entries removed in that commit, pointing at the same destinations, since all but one still resolve correctly today. The one exception (/docs/api-auth/token-renewal-in-safari) previously pointed at an internal page that itself now 302s out to an external support article - repointed directly at that external URL instead of chaining through a dead intermediate hop. Verified via a local redirect-matching simulation that all 53 restored sources resolve to their intended destination with no shadowing by an earlier wildcard rule in the file.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
avanscoy
approved these changes
Oct 13, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
A customer reported two hard 404s this week that worked as recently as last week:
https://auth0.com/docs/api-auth/tutorials/adoption/api-tokenshttps://auth0.com/docs/api-auth/tutorials/adoption/refresh-tokensRoot cause: #2002 ("old redirect cleanup, first pass") removed all 53 redirects sourced under
/docs/api-auth/*as low-traffic/unindexed, based on GSC and page-view data. That data wouldn't surface this case, since the reporting customer's own application code and error messages link directly to these URLs & the traffic is inbound from external code depending on the path staying stable, not organic search.Also confirmed several other
/docs/api-auth/*paths still linked from live docs content today (e.g./docs/api-auth/introfrommain/docs/api/authentication/login-legacy/database-ad-lapd-active.mdx,/docs/api-authfrommain/docs/quickstart/backend/rails/_index.mdx) are broken the same way, so this likely isn't limited to the two paths reported.Fix
Restored all 53 entries deleted in #2002, pointing at their original destinations
Verified via a local redirect-matching simulation that:
api-tokens→/docs/secure/tokens/access-tokens,refresh-tokens→/docs/secure/tokens/refresh-tokens)References
Root cause: #2002
Checklist
CONTRIBUTING.md.