URL redirect

[strich3]

Add a redirect option to the rules, for example:

If you want people to get redirected from website.xyz/somethingold to website.xyz/somethingnew

Very simple but could be useful

[kmanwar89]

Added my +1 to this feature request, hope it gets considered/implemented!

[megastary]

I very much hope so, because without this, I need to get back to Nginx. Kinda surprising that this is missing.

[rekirk82]

Looking forward to be being able to to do this for users.

[Node815]

Please make this happen, not having the ability to do so, is making me seriously consider going back to Cloudflare which I'd rather not do. I've touched the Traefik files so many times with my attempts, my head is spinning at this point. The path rewrites don't want to work via the GUI, or they sometimes do but not always.

[oschwartz10612]

Coming soon! :}

[JobDoesburg]

Any schedule for this? And will it be a full HTTP redirectp option? (Instead of just a path rewrite for an existing resource, like what's already supported currently I think)

[i-am-at0m]

Any schedule for this? And will it be a full HTTP redirectp option? (Instead of just a path rewrite for an existing resource, like what's already supported currently I think)

do you mean like a HTTP 301 or HTTP 302 response? it would be really really nice to be able to set up something like that to redirect to a status page with a 302 if there are no online targets for a site IMO as well as just being able to set up full on redirect resources.

[JobDoesburg]

Yes I mean 301 / 302 responses. I have quite some set up and right now I am running a manual nginx redirect service proxied by pangolin to do this, while Pangolin could easily do it itself directly.
So instead of specifying for a resource (and possibly a specific path) what site it should proxied to, it should be possible to indicate a 301 or 302 redirect.

[austinglander]

To those of you that can't wait (like me), I vibe coded a quick and dirty implementation of redirects as another type of resource. If you're interested, you can find my fork here. The CHANGES.md file on the redirect-resources branch contains migration instructions (should just be a one line change in your docker-compose.yml).

Use at your own risk. I skimmed over the generated code but did not test it rigorously.

[austinglander]

This is what a redirect resource looks like

[austinglander]

Notably does not support routing to different URLs based on path