W3C home > Mailing lists > Public > site-comments@w3.org > March 2019

Re: Missing redirect from http://www.w3.org to https://www.w3.org

From: Taft, Rob R <rtaft@navisite.com>
Date: Sat, 9 Mar 2019 02:52:09 +0000
To: Gerald Oskoboiny <gerald@w3.org>, Simon Hanna <Simon.Hanna@aeb.com>, "Taft, Rob R" <rtaft@navisite.com>
CC: "site-comments@w3.org" <site-comments@w3.org>
Message-ID: <47d4d74922224f019965511699e0648a@NCEMEXGP022.CORP.CHARTERCOM.com>
I can reach it now.

On March 8, 2019 5:34:46 PM Gerald Oskoboiny <gerald@w3.org> wrote:

> Hi Simon, Rob,
> * Simon Hanna <Simon.Hanna@aeb.com> [2019-03-08 12:16+0000]
>> Hi,
>> We are experiencing serious issues because our software is
>> trying to download XSD files hosted by w3.org, but isnít being
>> redirected from http to https.
>> Iím not sure why you are not redirecting http traffic to https.
>> TBH Iím unsure how this used to work, we just found out today,
>> that our systems no longer workÖ
>> Would be nice if you added the redirect (back)
> We do not redirect these resources from http to https, because
> some old clients can not handle https.
> We haven't made any recent changes to the way we serve these
> resources, but we received three similar reports like this in a
> short time frame today so I suspect our upstream network provider
> was doing some kind of DDoS protection that impacted certain
> networks but not others.
> Can you confirm if you are able to access our site over port 80
> now? If you are still unable to retrieve xsd files could you
> please try http://www.w3.org/ or http://www.w3.org/robots.txt ?
> To avoid issues like this in the future I recommend using an HTTP
> cache or XML catalog when requesting XSD files from other sites.
> For more info please see
> https://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic/
> --
> Gerald Oskoboiny <gerald@w3.org>
> http://www.w3.org/People/Gerald/

Received on Saturday, 9 March 2019 02:52:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:53:00 UTC