Re^2: Perlmonks.com and Perlmonks.net now redirect to Perlmonks.org

Yes, that's mildly expected - it also affects mini-cb60 for example. The reason is that we currently serve cached content to all anonymous GET requests.

The solution I see for this is to explicitly allow requests with the libwww-perl/x.y User Agent, or create a special URL that is not cached.

Comment on Re^2: Perlmonks.com and Perlmonks.net now redirect to Perlmonks.org Select or Download Code

Replies are listed 'Best First'.
Re^3: Perlmonks.com and Perlmonks.net now redirect to Perlmonks.org by hippo (Archbishop) on May 19, 2026 at 08:35 UTC
Tempting though it is, I would not go making special exceptions for widely-used user agent strings like this. You'll be back to square one in no time. The other option sounds good. I don't know what the chatterbot hits to get the messages but I see no value at all in serving say FullPage Chat with a long cache time. Still cache it to avoid catastrophe but drop the cache duration down to 30 seconds or so. Hopefully that will go some way to solving it. 🦛	[reply]
Re^4: Perlmonks.com and Perlmonks.net now redirect to Perlmonks.org by Corion (Patriarch) on May 19, 2026 at 08:39 UTC
Yes - the first step was a really coarse approach, basically caching all `GET` requests. Refining the access to some of the URLs is on the list, as we get more familiar with the Fastly / Varnish API. There is Webservice::Fastly, which we could for example use to invalidate the cache for FullPage Chat explicitly whenever a new chat item is added.	[reply] [d/l]