Recent comments in /f/meta

nitori wrote

Reply to Ongoing list of improvements to make when I get around to it :3 by twovests

I'm not sure about doing a warrant canary tbh. It's going to be another responsibility to keep up on a regular basis (Raddle updated their canary monthly before they've made it irregular, and other companies do it every 6 months). Updating the canary itself is not the hard part (until you get an actual gag order), but rather remembering to do it lol. If you forget, users might think jstpst got compromised when it's not

If you're going to do it anyway, it might be a good idea to have at least one admin who is outside of 14 Eyes doing the cryptographic signing, so that a government agency from those countries couldn't just force an admin here to update the canary

3

nitori OP wrote

Reply to comment by twovests in Why is the www.jstpst.net only a 302 to jstpst.net by nitori

Ah I see, thanks. In nginx I always use return instead of rewrite (which seems to be the closest to Caddy's redir) so I have to always specify the http response code.

but it won't take effect until I restart it.

Does Caddy not have a reload command like nginx does where you don't have to restart the server to apply the config changes?

2

twovests wrote

Reply to Why is the www.jstpst.net only a 302 to jstpst.net by nitori

The Caddyfile uses a redir directive for www.jstpst.net, which is 302 (temporary) by default. I never looked into it lol. I went in and changed this to a 308 but it won't take effect until I restart it.

That redirects to jstpst.net which is in a separate Caddy entry, which is a reverse proxy over the Docker on port 80. Caddy has HTTP by default and redirects http to https, so I'm guessing that's 308.

That said, as a joke, Caddy lets you use any 3XX code, but sadly, there are no funny ones.

5