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

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