Draft
Add middleware to handle 301 redirects for changed location URLs#468
Conversation
Author
|
@jbeard4 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs. I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review. |
Co-authored-by: jbeard4 <586962+jbeard4@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Links changed by org or location changes are not forwarding to a new link, and invalidating the old link
Add middleware to handle 301 redirects for changed location URLs
Sep 4, 2025
Member
|
@shakilhossain1 Is this PR old? Do we still need a middleware? I thought we fixed this issue here. Please let me know if I should close this PR. |
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.
When organization names or location details change, the location URL slugs change accordingly, but old URLs were showing 404 errors instead of redirecting to the new URLs. This creates broken links for users and impacts SEO.
Problem
The issue occurred when:
For example:
/locations/montefiore-medical-center-albert-einstein-wellness-center-port-morris/locations/montefiore-einstein-port-morrisSolution
Added Next.js middleware (
src/middleware.ts) that automatically handles 301 redirects for changed location URLs:/locations/{slug}patternsKey Features
Test Results
Validated against the reported examples:
montefiore-medical-center-albert-einstein-wellness-center-port-morris→montefiore-einstein-port-morris✅montefiore-medical-center-albert-einstein-wellness-center-wakefield→montefiore-einstein-wakefield✅montefiore-medical-center-morris-heights→montefiore-einstein-*✅montefiore-medical-center-norwood→montefiore-einstein-norwood-111-east-210th-street✅Fixes #242.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
fonts.googleapis.com/usr/local/bin/node /home/REDACTED/work/yourpeer.nyc/yourpeer.nyc/node_modules/next/dist/compiled/jest-worker/processChild.js(dns block)If you need me to access, download, or install something from one of these locations, you can either:
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.