You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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)
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.
The text was updated successfully, but these errors were encountered: