Conversation

Notices

1. feld (feld@friedcheese.us)'s status on Friday, 15-Nov-2024 01:09:12 JST feld
   Updated Caddy from 2.7.x to 2.8.x and they of course broke more shit
   
   I have a server that's like
   
   foo.com, www.foo.com {
   # config here
   }
   
   
   For some inexplicable reason caddy is serving foo.com as HTTP but www.foo.com as HTTPS
   
   WHAT THE FUCK GUYS
   • feld (feld@friedcheese.us)'s status on Friday, 15-Nov-2024 01:09:11 JST feld

     in reply to
     This is bullshit, I'm done with Caddy. It's burned me so many times. They keep shipping half broken shit like their HTTP/3 support that is enabled by default (currently broken in releases because it sends duplicate Content-Length headers)
     
     I'm switching to Apache LMAO. It's gonna be 95% the speed of Nginx and they ship mod_md in their Docker images so it can handle fetching its own Acme certs
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: likes this.
   • feld (feld@friedcheese.us)'s status on Friday, 15-Nov-2024 01:09:12 JST feld

     in reply to
     Just rolled back to 2.7.4, it's working again