3 ms·
> (Is anyone offended that you can’t remove nginx’s Server self-promotional header without an extra module?) Wait a second. The Caddy developers implemented a
by aorth 9y ago
> (Is anyone offended that you can’t remove nginx’s Server self-promotional header without an extra module?)
Wait a second. The Caddy developers implemented a premium "thank you" feature that embeds their sponsors' company names in the HTTP headers of the binary distribution[0], and then defends this by complaining that you can't disable nginx from simply printing a header that says "server: nginx"? It's not even remotely the same thing!
I think this was a very poor use of judgement. I don't even see why it's relevant that they asked their sponsors "do you want us to put your names in the HTTP headers of all the poor suckers running the binary builds?" There's a handful of other places that would be way more appropriate for spamming sponsors' names, for example: banner on the website, in the log files, on the download page, in the README, etc.
[0] https://github.com/mholt/caddy/pull/1866 https://github.com/mholt/caddy/pull/1866
- TAForObvReasons 9y agoThe biggest rub for me was the intentional misdirection regarding the Apache 2 License. As a web server, the only attribution required is to the person or entity who is deploying the server, not to the people accessing the website! (To be clear on that point, the actual web server software is running on the server end, not on the user end; this is in contrast with a JS library that runs in the web browser) I think the authors either fundamentally misunderstand the requirements (in which case they should find a lawyer) or they are intentionally misleading readers (in which case they are acting in bad faith and deserve contempt)