- From: Michael[tm] Smith via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 May 2023 05:26:24 +0000
- To: public-css-archive@w3.org
> You must have a caching proxy inline somewhere. > Or... your DNS is way out of date and somehow you're seeing the old server directly and not the new proxy OK, thanks much — I’m not aware of any relevant caching proxy anywhere, so I guess the only thing it could be is my DNS being out of date. I wasn’t aware there was an old server vs the new proxy, but I’m guessing if there’s an old server that’s not up to date, then the behavior I’m seeing is because I’ve still been getting responses from that old server. I’ll see what I can do about troubleshooting my DNS — but in the meantime, I guess I should go ahead and close this, since it seeming clear now that has to just be a local problem. -- GitHub Notification of comment by sideshowbarker Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8809#issuecomment-1537774314 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 05:26:26 UTC