Live data from Hacker News

Caddy – The HTTP/2 Web Server with Automatic HTTPS

caddyserver.com

31–40 of 66 posts

Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS

#31
post #18

Earlier quoted context omitted.

Agree. The $25/month stops me using it for side projects that generate small but non-zero revenue. Love the concept but not sure when I'll get to play time on something genuinely personal.

Can't you build it from source?

It does get quite complex when you need plugins.

I use the abiosoft Docker image and that has simplified it again.

Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS

#32
post #18

Earlier quoted context omitted.

Agree. The $25/month stops me using it for side projects that generate small but non-zero revenue. Love the concept but not sure when I'll get to play time on something genuinely personal.

Can't you build it from source?

I'm sure he can build it from source, but the "personal" license forbids using it for commercial purposes, so the point is moot.

Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS

#33
post #15

Earlier quoted context omitted.

It's open source, right? Just compile it yourself? To your lager point, I think paying for software is and has been the norm in many places. So nothing new.

I didn't notice that you can compile the source code yourself to avoid paying for the license. That seems to be a nice alternative.

Only if you're not using it for commercial stuff. If you're using it for commercial stuff you have to pay the $25/month

Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS

#34

Earlier quoted context omitted.

I didn't notice that you can compile the source code yourself to avoid paying for the license. That seems to be a nice alternative.

Only if you're not using it for commercial stuff. If you're using it for commercial stuff you have to pay the $25/month

The code is released under the Apache License. You're free to compile the source code and use it commercially. You're not allowed to do that with the official binaries.

Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS

#35
post #20

And it still doesn't obey the DNS specs. Specifically, the DNS RFCs define that, given no search domain, a relative hostname (e.g. google.com) is equivalent to its absolute hostname form (e.g. google.com.). This is used in SSL validation as well, a certificate valid for one is valid for the other, and in reverse. Every webserver SHOULD respond to both names identically, or redirect from one to the other. Let's try th…

You make it sound like the Caddy folks completely ignored the issue without providing a reason ("absolutely no reason", "doesn't even consider"). After looking into it, I find your post misleading and unfair, to say the least.

Link to the issue for other users who, like me, were concerned by your post:

https://github.com/mholt/caddy/issues/1632

According to the author, the issue is that (a) there are two RFCs that contradict each other on this distinction, and (b) most browsers do not treat them as such for the purpose of their same-origin policies. So he thinks it's best not to enable this alternate URL by default since it's trivial to add it as another route if you want.

I don't know if he's right or wrong, nevertheless, this clearly isn't a dude that doesn't give a shit.

Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS

#36

Earlier quoted context omitted.

> It's open source, right? Just compile it yourself? The point was that it was easy to install and get it running. Your point defeats the purpose of Caddy in the first place. It would be much easier to: 1. `sudo apt-get install nginx-extras python-certbot-nginx` 2. Add simple config with 80 port of your website/reverse proxy. 3. `sudo certbot --nginx` 4. Do not worry that you will be sued by nginx for using it for co…

Installing Caddy is easy. https://github.com/mholt/caddy#build Init scripts are included as well, both for FreeBSD, macOS and for a several different init systems used by various Linux distros. https://github.com/mholt/caddy/tree/master/dist/init FreeBSD even has it in the ports collection, so you can install it using the package manager that is included with FreeBSD doas pkg install caddy Once installed on FreeBSD w…

(Maybe I should switch to FreeBSD?)

Wait I have to manually install Caddy and then fight with systemd to make it start at boot? What is this? The 90?

Since they don't have have a standard package repo, you will also always be behind. You will have to keep track of their releases manually to make sure you are not missing an important update.

It is unclear why these folks have are resisting standard packages. Is that incompatible with their business model?

It made me move away from Caddy and instead go with Nginx and Certbot. Which is simpler and less maintenance work in the long run.

Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS

#37
post #5

They make it quite hard to find out, but here it is: > Caddy obtains certificates for you automatically using Let's Encrypt. Not sure why that is not stated front and centre. It's a good idea.

That’s literally the first selling point in 128px font. [1] It might not mention the implementation details but the concept is what matters. [1] https://i.imgur.com/hdEaKpG.jpg

Should've at least said "easily".

Just looks like it's capable of doing that which doesn't take much attention.

Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS

#38
post #36

Earlier quoted context omitted.

Installing Caddy is easy. https://github.com/mholt/caddy#build Init scripts are included as well, both for FreeBSD, macOS and for a several different init systems used by various Linux distros. https://github.com/mholt/caddy/tree/master/dist/init FreeBSD even has it in the ports collection, so you can install it using the package manager that is included with FreeBSD doas pkg install caddy Once installed on FreeBSD w…

(Maybe I should switch to FreeBSD?) Wait I have to manually install Caddy and then fight with systemd to make it start at boot? What is this? The 90? Since they don't have have a standard package repo, you will also always be behind. You will have to keep track of their releases manually to make sure you are not missing an important update. It is unclear why these folks have are resisting standard packages. Is that i…

[deleted]

Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS

#39

What's interesting is that it's the first web server not focused on speed or performance but on the user experience. I love nginx, but I had huge headaches configuring it when migrating php apps with huge htaccess rules to nginx. The terms of the license do not seem super clear though.

That said, I've found the performance to be pretty good. Getting < .01sec response times on a node.js API server that caches data in RAM. I'd expect to see worse if Caddy were a bottleneck.
Post reply on HN