Hi just read the announcement for Commercial Caddy licensing and the requirement for the
Caddy-Sponsors HTTP header being required/used. I need clarification,
- Does this only apply to the official provided/downloaded binaries and is not a requirement if building via source compile ourselves ?
- Or does this
Caddy-Sponsorsheader requirement also extend to self built source compiled Caddy binaries ?
- Is there a limit to size of the header as you add more sponsors ?
- I am testing and evaluating Caddy for integration into my Centmin Mod LEMP stack installer which is open source and free, so distributing Caddy via custom integration into my LEMP stack installer would be considered commercial or personal use ? What if my Centmin Mod LEMP stack users usage is commercial ? How do I deal with Caddy distributed this way ? I DO NOT have any info as to what my users use my LEMP stack for whether it’s personal or commercial. The integration doesn’t modify any Caddy source code. It’s just scripted integration for automatic site vhost creation via shell based script cli command line or shell based menu so it eventually generates domain vhosts which would work with several planned web server integrations - nginx and later, openlitespeed, litespeed, apache 2.4, caddy and/or h2o. So end user can generate a site vhost once and be able to choose which web server they want to use which would share a common site account structure/web roots etc. Also Haproxy is planned too so technically can have web sites running different backend web servers eventually.
The concern I have is due to performance as there’s known performance overhead with Caddy as you start adding more HTTP headers to your site - benchmarks at Any performance overhead as you add more headers under HTTP/2?. Have you looked at the performance overhead as you continue to add new sponsors and increase the size of the
Caddy-Sponsors header ?
I would rather put in the HTML footer of a Caddy powered web site, a Powered by Caddy text/logo then have additional HTTP headers reduce overall web performance over time. Just my 2 cents
Currently I see
curl -I https://caddyserver.com/blog/accouncing-caddy-commercial-licenses HTTP/1.1 200 OK Accept-Ranges: bytes Caddy-Sponsors: This free web server is made possible by its sponsors: Minio, Uptime Robot, and Sourcegraph Content-Length: 0 Content-Security-Policy: style-src 'self' https://fonts.googleapis.com; script-src 'self' data: https://www.google-analytics.com https://checkout.stripe.com; img-src 'self' data: https:; font-src 'self' data: https: blob:; media-src 'self' https:; connect-src 'self' https:; object-src 'none'; Content-Type: text/html; charset=utf-8 Etag: "ow83jscod" Last-Modified: Wed, 13 Sep 2017 14:43:04 GMT Referrer-Policy: no-referrer-when-downgrade Server: Caddy Strict-Transport-Security: max-age=31536000 X-Content-Type-Options: nosniff X-Frame-Options: SAMEORIGIN X-Xss-Protection: 1; mode=block Date: Wed, 13 Sep 2017 16:40:08 GMT