Fix infinite redirect loops on two blog posts - #5588
Merged
Conversation
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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
/blog/2023/05/integrating-modbus-with-node-red//blog/2026/03/rethinking-edge-ais-core-orchestration/nuxt/redirects.ts. Nitro's route matching is case-insensitive by default, so each of these rules also matched its own lowercase canonical URL, redirecting it to itself — an infinite loop that aborts navigation before the page ever renders.nuxt/redirects.tsand re-added them tonetlify.tomlinstead. Netlify's edge redirects match exact case, so the old capitalized URLs still 301 to the canonical lowercase URLs, without colliding with them.nuxt/redirects.tsfor the same pattern (a key case-insensitively equal to its ownto, or colliding with another key) — no other instances found.Test plan
npm run dev), confirm they render normally now.netlify.tomlredirects only run through Netlify's own layer, not plainnuxt dev, can't be checked locally withoutnetlify dev, confirm they 301 to the canonical URL instead of looping or 404ing.Related Issue(s)
https://app.asana.com/1/1213818720452348/project/1215165115614867/task/1217418319610123?focus=true
Checklist