Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Why do we need a redirect path? #62

Open
loevgaard opened this issue Jan 2, 2021 · 0 comments
Open

Why do we need a redirect path? #62

loevgaard opened this issue Jan 2, 2021 · 0 comments

Comments

@loevgaard
Copy link
Member

loevgaard commented Jan 2, 2021 •
edited
Loading

Right now it's possible to have a redirection path like A => B => C => D. Why is that?

Given this redirection path, if I add a new redirect that redirects D => E, then it would make more sense to update the redirects, such that:

  • A => E
  • B => E
  • C => E
  • D => E

This way we know that when we have a redirect it always contains it's final destination in the destination field.

UPDATED
Comment from @Roshyo: This would only be correct if all the redirects are permanent redirects.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@loevgaard