Caddy is the first and only web server to use HTTPS automatically and by default

Re:Caddy is the first and only web server to use HTTPS autom... by francislavoie on Tuesday September 12, 2023 @12:21PM (#37483624)

To add onto mholt's reply, we avoid implicitly enabled functionality where possible (the only feature that's implicitly enabled generally is Automatic HTTPS, off the top of my head). By default, Caddy's HTTP handlers do nothing which is good because it gives you a clean slate to build on top of. If you had to turn off features to reset back to zero, that's cruft. For example, think of CSS resets, which are needed to turn off styles added by browsers by default; that's annoying and a complication that all websites need to deal with to get consistent behaviour.

[ Parent | on HN ]

Re:Caddy is the first and only web server to use HTTPS autom... by kasdi on Tuesday September 12, 2023 @03:17PM (#37486413)

Great approach. User agent default style sheets are the worst, especially since they are all different.

But, instead of handing the user a empty slate with nothing, it should contain a note saying “look, these are the recommended options”. If the initial config is interactive, it could even prompt to activate them: “want to use compression?” - “yes”, etc.

[ Parent | on HN ]

Re:Caddy is the first and only web server to use HTTPS autom... by francislavoie on Tuesday September 12, 2023 @03:20PM (#37486459)

Those recommendations are in the documentation.

Interactive configuration is easier said than done. We don't realistically have the time to build and maintain that on top of the core program and config. We're already stretched pretty thin.

[ Parent | on HN ]