Post #1740298

2026-04-28 08:19 UTC

👩🏻‍💻 my so-called sudo life - day 497: Mastodon stampede edition 🐘 Dear Fedi friends, You may remember how last year I was dealing with self-DDoS attacks every time I shared a link to my Wordpress or Ghost sites. Well, I solved the issue with Ghost (#VinylCache is brilliant) but I never found a solution for my Wordpress site... not even with #BunnyCDN. I guess I wasn't tweaking the right settings. This is a pity because TBH the ActivityPub for Wordpress plugin is SO COOL and works flawlessly. I had to move my blog posts to Ghost and keep Wordpress as a static portfolio site. That being said, I never dared share links to my Wordpress site anymore because I would get about 4000 requests within 60 seconds and everything would freeze. I just looked into #BunnyCDN's settings again and tried to tweak them. So please bear with me for an experiment, sharing an old blog post and seeing what happens. Wish me luck! From the archives: https://elenarossini.com/2025/01/my-so-called-sudo-life-time-matters/ #BuyEuropean #CDN #DDOS #MastodonHugofDeath #MastodonStampede #Wordpress #blog #MySoCalledSudoLife

Replies (2)

@xavier@pony.social 2026-04-28 08:55

@elena@aseachange.com looking at the response headers, the assets (fonts, css, js) are indeed served from cache (cdn-cache: HIT), but fedi instances don't load the assets when generating the preview, only the main HTML. The main HTML file is still not cached by the Hostinger CDN (x-hcdn-cache-status: DYNAMIC header, then a x-powered-by: PHP/8.2.30 confirming that wordpress was called). I'm not certain about the specifics for Hostinger, but in most cases, DYNAMIC indicates that the wordpress server itself denied caching via a Cache-control header. Right now, I think the stampeede issue will still happen, unless you change the wordpress config to allow caching of generated pages. It's not enabled by default, because when you enable it, you need to setup cache invalidation for page changes to propagate.

Open ##1740740
@mirou@mastodon.social 2026-04-28 08:29

@elena the page was hard to load at first but now it seems to work fine. I load it in my Mastodon client, the safari (slow on both at first then fast) and tried again in Firefox to make sure it wasn’t cached locally.

Open ##1783031