- From: Michael[tm] Smith via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 May 2023 07:02:04 +0000
- To: public-css-archive@w3.org
OK, for the record here, it seems I had been getting routed to 173.230.149.95 (which I assume must be the old server) but now I’m finally getting consistently routed to 45.79.94.155 (which I assume must be the correct server, the new proxy). I have no idea how I “fixed” it — all I did was to run a few tools like dig, traceroute, and mtr. I hope it was in fact just some weird local issue, and not something caused by some broader network problem that other people (e.g., other people in Japan where I’m connecting from) might also run into. Because if they did run into it, it likely wouldn’t be obvious to them that they were seeing stale content. Would it be possible to shut down the 173.230.149.95 server so that anybody else who might be still getting routed to it now would see hard 404s rather than stale content? -- GitHub Notification of comment by sideshowbarker Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8809#issuecomment-1537855006 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 8 May 2023 07:02:06 UTC