How to redirect to www?

[codepilotsf]

I've got Kamal 2 working great and deploying my app to www.example.com. But if a user directly navigates to example.com without "www", they hit an ugly "connection is not secure" error message. How can I get Kamal Proxy to do what (in my humble opinion) it should already be doing by default?

[tuladhar]

By default, Kamal Proxy routes requests only to matching hosts and does not currently support redirection. However, you can achieve this functionality as such:

proxy:
  hosts:
  - example.com
  - www.example.com

[codepilotsf]

Okay so then my app responds on both hosts and I guess I just redirect in my application controller?

[tuladhar]

Yes

[codepilotsf]

Okay thanks for your help. That's too bad that Kamal Proxy doesn't handle something as basic as a redirect to www.

[emk-klaay]

It is open source. Feel free to make a PR to solve it. 👍

[soheil]

The biggest d*ck answer I've ever seen. Answers like this makes this project look horrible and I'm befuddled why RoR would use a deployment tool like this.

Redirects are as basic as it gets, if you're not gonna use something like nginx and reinvent your own solution in Go at least have the decency to implement the bare minimum features instead of making condescending remarks to your hijacked users.

[LiamBateman]

I've been looking for this as well, kind of like what we would do in Apache .htaccess

If I was to look at adding this in would there be appetite for this feature?

[viktorianer]

Redirects shouldn’t be a concern of Kamal 2. These are better handled by DNS, a reverse proxy, or the app itself, depending on the use case.

[soheil]

DNS doesn't do redirects! Often the point of a redirect to avoid hitting a specific endpoint in the app to begin with. Finally on your last point can you elaborate how you'd implement a nginx reverse proxy using kamal?!

Literally I've scoured the internet without finding a single example or guide on how to do a redirect or setup nginx/apache with this tool.

[codepilotsf]

Of those 3 options, I think option 2 is best. Not all DNS providers offer redirection. Checking the host and redirecting at the app level means every request takes a small performance hit. So that leaves number two— which when using Kamal 2 is kamal-proxy. So I believe this should be the role of kamal-proxy (but it currently doesn’t offer this feature).On Nov 24, 2024, at 10:42 AM, Viktor Schmidt ***@***.***> wrote: Redirects shouldn’t be a concern of Kamal 2. These are better handled by DNS, a reverse proxy, or the app itself, depending on the use case. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[soheil]

Seems like a non-answer just to show he's "responding to issues".

[dmitry]

The only way to use accessories is with an additional HTTP server. I have used Caddy as it's much easier to deploy and set up in terms of configuration and SSL. It also means you have to deal with TLS by yourself, though Caddy has an almost automatic way to activate it: https://caddyserver.com/docs/automatic-https
I have used this method for 3 servers already, but the problem is that if you have multiple Kamal deployments on one server, you have to support separate Kamal deployment for the Caddy proxy to kamal-proxy, in another way it will not work. It took me a couple of hours to find out all the necessary config details to make it.