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

Hi Peter

Thank you for your reply.

Yes, I know that. Already discussing with the vendor.

Any idea re the HTTPS fault in validator?

I imagine the validator doesn't have up-to-date certificate authorities...

Regards, Jonathan

On 06/07/16 22:00, Philip Taylor wrote:
> 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