No wonder the redirect is not being cached lol
(but the http to https is a 308..?)
Comments
nitori OP wrote
dang. we live in a postmill
twovests wrote
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.
emma wrote
but sadly, there are no funny ones.
i beg to differ. 320 blaze it.
nitori OP wrote
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?
twovests wrote
it does! i'm just working from my phone, so if something somehow goes wrong, i don't wanna leave jstpst down while trying to fix it on a phone
flabberghaster wrote
Are you pentesting jstpst.net?
Please don't delete all of our posts if you find an exploit
emma wrote
it's engagement bait so people post about it.