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.

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

Priorities for redirects #56

Open
regniets opened this issue Mar 29, 2022 · 2 comments
Open

Priorities for redirects #56

regniets opened this issue Mar 29, 2022 · 2 comments

Comments

@regniets
Copy link
Contributor

It would be cool for the redirecthandler to be able to handle priorities - so that you can practically can handle advanced scenarios.
Example:
Website-Domain is example.com
A subdomain old.example.com should be redirected to the new website.
Therefore you need a bunch of redirects from subpages and after those one should redirect the subdomain itself (best case: with a catchall) to the new domain.

@Sebobo
Copy link
Member

Sebobo commented Mar 30, 2022

I think redirects like that should always be done via the web server.
It's easier to configure and also to remove again.
Not easy to implement here IMO.

@regniets
Copy link
Contributor Author

Yes, that is where we keep doing them.
Only that you get a mix-up where you have a set of redirects on the webserver that do not respond to changes (e.g. when you move or rename nodes) and this is where errors do occur.
It would be a very handy feature though. (Just accidentally worked with hubspot sites and they have a decent redirect management where i could enter priorities etc. - could do practically anything)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants