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

On 12/07/16 05:47, Michael[tm] Smith wrote:
> Jonny Grant <jg@jguk.org>, 2016-07-11 11:50 +0100:
>> Archived-At: <http://www.w3.org/mid/57837A03.2090700@jguk.org>
>>
>> On 10/07/16 22:57, Michael[tm] Smith wrote:
> ...
>>> (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.
>>>
>> Thank you Mike
>>
>> Maybe the validator can be updated to use the NU variant?
>
> It does already as long as you give it a document with the doctype
> <!DOCTYPE html> instead of an obsolete doctype such as the HTML4 doctype.
>
> So in https://primes.utm.edu/nthprime/ you should remove this:
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
>
> and just replace it with this:
>
> <!DOCTYPE html>
>
> If you do that and use https://validator.w3.org/ the validation request
> will get automatically redirected to https://validator.w3.org/nu/
>
>    —Mike

Hi Mike,
Thank you for the reply.
Unfortunately it is not my website, so I can't change their HTML.

It seems like the NU validator is better, so maybe this can just be the 
default?

Regards, Jonny

Received on Tuesday, 12 July 2016 09:23:46 UTC