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

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

From: Philip Taylor <P.Taylor@Rhul.Ac.Uk>
Date: Wed, 6 Jul 2016 22:00:21 +0100
To: Jonny Grant <jg@jguk.org>
CC: "www-validator@w3.org" <www-validator@w3.org>
Message-ID: <577D7165.2060706@Rhul.Ac.Uk>
As your page neither needs https to be delivered, not is it written in HTML 5, you can easily verify it using the standard W3C validator :

    https://validator.w3.org/check?uri=http://primes.utm.edu/nthprime/

Philip Taylor
--------
Jonny Grant wrote:
> https://primes.utm.edu/nthprime/
>
> 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)

-- 

Philip Taylor
Received on Wednesday, 6 July 2016 21:01:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 6 July 2016 21:01:05 UTC