Yesterday the caddy maintainers announced their new commercial licenses along with a new EULA for their free version as well. (Applying to the binaries they provide on their site, not self-compiled binaries)
https://caddyserver.com/blog/accouncing-caddy-commercial-licenses.html
Especially [this commit](https://github.com/mholt/caddy/commit/ad973f1d125d4da9ba8bc21448dcd3de3fe79cbe) is source for a lot of grief.
It introduces a Header to every HTTP Response that includes the name of their sponsors. Users of their binary version are not allowed to temper that header with other tools. The config file won't allow for removing that header even for self-compiled versions.
This is an unacceptable situation for us, but we have a few options:
1. remove caddy
2. patch caddy ourselves (which I think is legally allowed)
3. replace caddy with [https://github.com/WedgeServer/wedge](https://github.com/WedgeServer/wedge), a caddy fork that removes the header.
I think option 3 is the most sensible. The caddy developers seem to be content with this fork aswell.
@SevereOverfl0w @voidlinux/pkg-committers
Why is 1 a requirement? The code is still apache licensed, so there's no
need to remove it altogether.
On 14 Sep 2017 11:28 am, "lemmi" <notifications@github.com> wrote:
> Yesterday the caddy maintainers announced their new commercial licenses
> along with a new EULA for their free version as well. (Applying to the
> binaries they provide on their site, not self-compiled binaries)
> https://caddyserver.com/blog/accouncing-caddy-commercial-licenses.html
>
> Especially this commit
> <https://github.com/mholt/caddy/commit/ad973f1d125d4da9ba8bc21448dcd3de3f=
e79cbe>
> is source for a lot of grief.
> It introduces a Header to every HTTP Response that includes the name of
> their sponsors. Users of their binary version are not allowed to temper
> that header with other tools. The config file won't allow for removing th=
at
> header even for self-compiled versions.
>
> This is an unacceptable situation for us, but we have a few options:
>
> 1. remove caddy
> 2. patch caddy ourselves (which I think is legally allowed)
> 3. replace caddy with https://github.com/WedgeServer/wedge, a caddy
> fork that removes the header.
>
> I think option 3 is the most sensible. The caddy developers seem to be
> content with this fork aswell.
>
> @SevereOverfl0w <https://github.com/severeoverfl0w>
> @voidlinux/pkg-committers
> <https://github.com/orgs/voidlinux/teams/pkg-committers>
>
> =E2=80=94
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/voidlinux/void-packages/issues/7657>, or mute the
> thread
> <https://github.com/notifications/unsubscribe-auth/AF2h2ou-71RGh6gON33E86=
wxot02xV2Vks5siP_pgaJpZM4PXXxt>
> .
>
--=20
You are receiving this because you are on a team that was mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/voidlinux/void-packages/issues/7657#issuecomment-3294426=
60=
@SevereOverfl0w we had a short discussion on IRC and at that time this the favourite option, which is why I included it. Adding wedge doesn't mean we have to remove the old caddy version. I'd like to keep version 0.10.8 around for a while to give people time to migrate.