Support for https
Opened this issue · 8 comments
I love your service!
Great idea and damn simple to use.
Is there any chance that https is supported as well?
As I see there is right now no https support enabled for the sld alias.redirect.name
Maybe it could be setup by using acme v2 wildcard certs from letsencrypt?
Thanks for the kind words!
There's no HTTPS support right now, but I'd be happy to have it. Do you want to open a PR?
@holic Would HTTPs even be possible? I love this simple approach and have a use case for it. If HTTPs was possible I'd put some time toward exploring this.
I'm thinking there may be a conflict with the HTTPs Certs. Not just a code thing.
Very much interested with https support, but I don't understand why it's not supported by default. Why does it need a special configuration? The redirect from one domain to another should work regardless to each certificates, no?
For those interested, it's not as trivial as at seems. It is not possible to perform an HTTPS redirect without an SSL certificate (https://stackoverflow.com/questions/6331371/how-to-redirect-https-to-http-without-any-ssl-certificate). It would imply that redirect.name should integrate a service like LetsEncrypt and this also requires (a lot of) extra DNS settings on the user side as well.
Recently I discovered that you can use CloudFlare with the 'Flexible' encryption mode to support https with redirect.name, might be worth looking into!
Ended up implementing a generic CloudFlare worker that uses the URI record to figure out where to redirect to https://github.com/mrexodia/cloudflare-redirect