It's also a security risk if your web server is the only one doing it, as it is a way for an attacker to identify the web server in use.
devs presumably
I thought it was a good idea at the time. ¯\_(ツ)_/¯
Gives off the of vibe "We can do this; we will do this and you schmucks can't do anything about it because it's in the EULA".
Regardless to how harmless it is. It's still an unprofessional quality to implement such and then deny the ability to disable it.
Same example as if when you honked your cars horn it tooted the car model. You'd be annoyed right?
Sure, its harmless because how often do you use your car horn but you expect a car horn to horn not advertise the model your driving.
Let's hope Elon doesn't read this.
Harmless or not - I think it's worth looking past this point. Maybe the http header was a way for them to search the internet and find *commercial* sites that didn't pay for Caddy license? Not very pro behaviour.
[0] https://web.archive.org/web/20180216153020/https://caddyserv...
Adding a sponsor header is harmless (albeit useless IMO). For me that would be no reason to not choosing this software, and certainly no ground for having a 'bad taste'.