Built from master a few minutes ago: v2.2.2-0.20201118231455-12cc69ab7ade h1:Pss1c1toELBy8jbzQGQpD327MkPLS+4XfWptLzjkQQM=
My normal setup is currently on: v2.2.1 h1:Q62GWHMtztnvyRU+KPOpw6fNfeCD3SkwH7SfT1Tgt2c=
2. How I run Caddy:
My normal setup involves docker and such, but this example is just using xcaddy to build from master, running caddy with ./caddy run, and accessing the webserver via 192.168.1.101:9090 from another machine on LAN.
a. System environment:
$ uname -a
Linux xnaasSRV 4.19.0-12-amd64 #1 SMP Debian 4.19.152-1 (2020-10-18) x86_64 GNU/Linux
Again: normally this is all dockerized and such, which is where I first noticed the issue. But I’ve build from master and am running more “normally” for this testing to demonstrate that the issue is not my specific setup.
Unfortunately, now something is doing something janky. Instead, I end up getting sent in a redirect loop that causes every major browser to error out. It seems like it’s trying to point me to 192.168.1.101:9090/private/?r=<spamhere> and/or 192.168.1.101:9090/404?r=<spamhere>.
4. Error messages and/or full log output:
Here’s an example from debug logging when trying to go to 192.168.1.101:9090/nothere: https://pastebin.com/gVafzx41 (the bit at the end is just me hitting ctrl+c to kill the process).
5. What I already tried:
Other than removing the handle_errors, I can’t think of what to try, thus I’ve come here seeking assistance.