SRE weekly 所有文章

sreweekly/articles/207/02-running-servers-and-services-well-is-not-trivial.html

@@ -0,0 +1,78 @@
+<html>
+<head>
+<title>You're using a too-old browser</title>
+<meta name="viewport" content="width=device-width">
+</head>
+<body>
+<h1> You're using a suspiciously old browser </h1>
+<p> You're probably reading this page because you've attempted to access
+some part of <a href="../space/blog/">my blog (Wandering Thoughts)</a> or
+<a href="../space/">CSpace</a>, the wiki thing it's part of. Unfortunately
+you're using a browser version that my anti-crawler precautions consider
+suspicious, most often because it's too old (most often this applies to
+versions of Chrome). Unfortunately, as of early 2025 there's a plague
+of high volume crawlers (apparently in part to gather data for LLM
+training) that use a variety of old browser user agents, especially
+Chrome user agents. To reduce the load on
+<a href="../space/blog/">Wandering Thoughts</a> I'm experimenting with
+(attempting to) block all of them, and you've run into this. </p>
+
+<p> If this is in error and you're using a current version of your
+browser of choice, you can contact me at <a
+href="https://www.cs.toronto.edu/~cks/">my current place at the
+university</a> (you should be able to work out the email address
+from that). If possible, please let me know what browser you're
+using and so on, ideally with its exact User-Agent string.</p>
+
+<h2> A special note to people using Inoreader (the feed reader) </h2>
+
+<p>
+I am not blocking Inoreader's feed fetcher or considering it to be
+too old, and it routinely fetches feeds from me. I don't know why
+Inoreader is showing you this page. It is possible that they're
+periodically trying to fetch feeds or pages with an old browser
+HTTP User-Agent (or an actual old browser) and taking the results
+of that fetch (this page) as what they should show people instead
+of the results of their syndication feed fetcher agents. This is a
+bad mistake today; <a
+href="/~cks/space/blog/web/HTTPResultsAndUserAgents">the results
+of modern HTTP fetches depend partly on the HTTP User-Agent used</a>.
+</p>
+
+<h2> A special note to people using Feedly (the feed reader) </h2>
+
+<p> Much like Inoreader, Feedly is periodically fetching my syndication
+feeds with a fake, old browser HTTP User-Agent header, which fails,
+and is then grimly latching on to the results for their actual feed
+fetching with their regular Feedly HTTP User-Agent. There is nothing
+I can do about this; you should contact Feedly support, if you can
+find them. See <a
+href="https://utcc.utoronto.ca/~cks/space/blog/web/FeedReaderErrorsProblem?showcomments#cks-20260215115901">this
+comment of mine in Wandering Thoughts</a> for more details.
+</p>
+
+<h2> A special note for people using Vivaldi </h2>
+
+<p> Due to an ongoing attack, you may need to change
+<a
+href="https://help.vivaldi.com/desktop/miscellaneous/user-agent-brand-masking/">the
+"User Agent Brand Masking" setting</a> so that your Vivaldi identifies
+itself as Vivaldi, instead of Google Chrome. This applies to even
+the current version of Vivaldi. </p>
+
+<h2> A special note for people using archive.* </h2>
+
+<p> You may be seeing this through archive.today, archive.ph, archive.is,
+and so on. Unfortunately, archive.* crawls pages to archive in a way that
+is impossible to distinguish from malicious actors. They use old Chrome
+User-Agent values, crawl from IP address blocks that are widely distributed
+and not clearly identified as theirs, and some of their IP addresses have
+falsified reverse DNS entries that claim they are googlebot IP addresses
+(which is something that is normally done only by quite bad actors). I
+suggest that you use archive.org, which is a better behaved archival
+crawler and can crawl <a href="../space/blog/">my blog (Wandering Thoughts)</a>.
+</p>
+
+<address>Chris Siebenmann, 2025-02-17</address>
+</body>
+</html>