2026-01-22 17:25 UTC
Replies (7)
-
@mirabilos@toot.mirbsd.org 2026-01-23 01:35
@markmcb@mas.to but lynx!
-
@wyatt@soc.megatokyo.moe 2026-01-23 01:41
@markmcb@mas.to i browse sometimes on windows 9x machines so this always makes me sad
-
@cks@mastodon.social 2026-01-23 02:27
@markmcb@mas.to If you have or get a syndication feed, I suspect that a bunch of feed fetchers will turn out to be HTTP/1.1 (only), too. They're often older and even when they're newer they may be using older HTTP libraries or HTTP settings. (My current blog host isn't HTTP/2 enabled to so I can't see myself.)
-
@stephen@microbe.vital.org.nz 2026-01-23 02:35
@markmcb@mas.to If you have RSS or Atom feeds worth making an exception for them too...most newsreaders seem to be on 1.x too.
-
@ltning@pleroma.anduin.net 2026-01-23 06:34
@markmcb@mas.to Wonder if a bit of lua and a shm zone could help track clients that respect upgrades and block them if they don't...
-
@sheephorse@mastodon.online 2026-01-23 07:30
@markmcb@mas.to Thanks for the write up, I have noticed a similar pattern on my blog but never thought to just turn off older protocols. I get so little traffic from google these days that even excluding "legitimate" crawlers would not make a difference.
-
@ramonfincken@mastodon.social 2026-01-23 07:43
@markmcb@mas.to excellent point: cat baddies-access.log | grep -v '1\.1' | wc -l 953 cat baddies-access.log | grep '1\.1' | wc -l 41519