W3C home > Mailing lists > Public > www-validator@w3.org > July 2016

Re: HTTPS valid in Chrome, but not via w3c validator

From: Jonny Grant <jg@jguk.org>
Date: Mon, 11 Jul 2016 11:50:43 +0100
To: "Michael[tm] Smith" <mike@w3.org>
Cc: "www-validator@w3.org" <www-validator@w3.org>
Message-ID: <57837A03.2090700@jguk.org>


On 10/07/16 22:57, Michael[tm] Smith wrote:
> Jonny Grant <jg@jguk.org>, 2016-07-06 20:59 +0100:
>> Archived-At: <http://www.w3.org/mid/577D6338.7010108@jguk.org>
>>
>> I see this has a valid certificate in Chrome, signed by Godaddy.
>>
>> https://primes.utm.edu/nthprime/
>>
>> But the validator rejects it:
>> https://validator.w3.org/
>>
>> I got the following unexpected response when trying to retrieve
>> <https://primes.utm.edu/nthprime/>:
>> 500 Can't connect to primes.utm.edu:443 (certificate verify failed)
>
> Please use https://validator.w3.org/nu/ instead:
>
>    https://validator.w3.org/nu/?doc=https://primes.utm.edu/nthprime/
>
> (I think the reason that site doesn’t work in https://validator.w3.org/ is
> because it probably is a site that relies on SNI (Server Name Indication),
> which https://validator.w3.org/ does not support.)
>
> But https://validator.w3.org/nu/ does support SNI.
>
>    —Mike
>

Thank you Mike

Maybe the validator can be updated to use the NU variant?

Regards, Jonny
Received on Monday, 11 July 2016 10:51:24 UTC

This archive was generated by hypermail 2.3.1 : Monday, 11 July 2016 10:51:26 UTC