- From: Norm Tovey-Walsh <ndw@nwalsh.com>
- Date: Fri, 19 Aug 2022 09:16:19 +0100
- To: Gerald Oskoboiny <gerald@w3.org>
- Cc: Michael Sperberg-McQueen <cmsmcq@blackmesatech.com>, Michael Kay <mike@saxonica.com>, xmlschema-dev@w3.org
- Message-ID: <m28rnktz7t.fsf@nwalsh.com>
> I included some rough stats in my initial message in the thread: > https://lists.w3.org/Archives/Public/xmlschema-dev/2022Aug/0000.html Right. Thank you. I only saw that after I rejoined the list. > but it's hard to say what all the applications might be that show up > as a generic UA like 'Java/*' Yeah, that’s a darned shame. > We are getting some useful data as comments on the blog post, > https://www.w3.org/blog/2022/07/redirecting-to-https-on-www-w3-org/ Yes. I interpret the comments about “getting the HTML page instead of the schema” as being the tools that don’t follow redirects: they get whatever page you serve with the 301 response. > 1) making this change will cause any use of XML Schema to break > (sounds like that's not the case), > > 2) this may be a minor nuisance in the short term, but workarounds are > readily available, or > > 3) this should only impact a handful of people using outdated > software. I’d have been inclined to say mostly 2 or 3 as my guess, but some of the comments on that weblog post are a little alarming. As I feared, not following redirects is a common problem and if libxml2 doesn’t work, that’s going to be an issue for a bunch of people, I expect. I feel for the folks who managed to put “getting the XSD from www.w3.org” into the critical path for logging in to their site without supporting redirects. > We are hoping our current 3-day https redirect experiment in progress > will give us insight into which of these is the case. > https://status.w3.org/incidents/dhv59mm7kdw6 Good luck! Be seeing you, norm -- Norman Tovey-Walsh <ndw@nwalsh.com> https://nwalsh.com/ > "Bother", said Pooh, as he deleted his root directory.
Received on Friday, 19 August 2022 08:27:54 UTC