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?

dang. we live in a postmill

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.

it's engagement bait so people post about it.

Mods, you gotta book this guy

oh god not the 30s

you ain't seen nothin, see?

I better not see you around this place no more

Aha, so Chrome was already doing it since like version 40 or so, and Mozilla just eventually followed Chrome's behavior in Firefox 95. Interesting...

https://bugzilla.mozilla.org/show_bug.cgi?id=1468476

Hmm I just looked at what today's Firefox does (since I used Pale Moon's devtools when I checked this out), and apparently it doesn't request the static resource again and therefore does not let the server return a 304, even if there's no Cache-Control header. I wonder what sorcery Mozilla did to determine whether a resource is immutable and therefore safe to just rely on cache when reloading... Or maybe they just decided that they shouldn't bother to look for 304 in every resource whose initiator/cause in the devtools network tab is not "document"... I don't think this aggressive caching is smart since that just increases the likelihood of outdated resources being served when the browser should've revalidated its cache. So I say go for it regardless of what mainstream browsers think lol

It certainly could be added to the nginx that Postmill includes.

Edit to add: Cloudflare doesn't add that stuff, the caching's been tweaked by me over years. I plan to document it in the Postmill wiki sometime in the future.

Ooh I really appreciate this. We're using Caddy, so I'll have to translate the config, but that shouldn't be too hard (+ easy to reverse if I mess it up lol).

u/emma I wonder if this can also be done in Postmill proper so that sysadmins don't have to manually add the header themselves in their reverse proxies?

woopsie lol

i also need to fix a 500 error on signing in!! i keep procrastinating image thumbnails. will get crackin on both later today

Oh god the broken image thumbnail virus spread here

Skill issue

Fuck You

It is not fixed, it still thinks it's an http site. If you changed docker-compose.yml, you'll also have to docker compose up -d.

(i call it dorker)

crud. thanks for the details; i'll fix this up tomorrow!

It is not fixed, it still thinks it's an http site. If you changed docker-compose.yml, you'll also have to docker compose up -d.

Also i just pushed new images since there was a bug after upgrading Symfony that would affect TRUSTED_PROXIES, so may be a good idea to docker compose pull before doing the above, too.

fixed!! thank u for pinging about this again, i totally forgot.

the fix took less time to do than typing this comment

twovests more like yellowvests

mease grunckey