Re: http://validator.w3.org/#validate_by_input External Checker not available 500 Can't connect to localhost:8888 (connect: Connection refused)

2013-02-04 20:12, doc inf wrote:

> It used to work properly!
>
> -----
>
> I got the following unexpected response when trying to retrieve
> <http://h10_remon_van_dijk.informatica-mwc.nl/>:
>
>     |500 Can't connect to h10_remon_van_dijk.informatica-mwc.nl:80
>     <http://h10_remon_van_dijk.informatica-mwc.nl:80> (Bad hostname
>     'h10_remon_van_dijk.informatica-mwc.nl
>     <http://h10_remon_van_dijk.informatica-mwc.nl>')|

The page is accessible in general, the Validator just can't reach it. 
Apparently its domain name service has some problems.

While waiting for this to get fixed, you can use
http://validator.nu
instead. However, it seems to have an issue with XHML 4.01 Transitional 
doctype, reporting it as an error, even though it processes the document 
according to it. I wonder if this is a recent change and whether this 
oddity is present in the W3C Validator as well.

"Error: Almost standards mode doctype. Expected e.g. <!DOCTYPE html>." 
sounds rather questionable HTML5 evangelism.

> I heart Validator logo <http://www.w3.org/QA/Tools/Donate>

A bit strange, isn't it? I would expect W3C Quality Assurance to take 
better care of alt attributes. This is actual markup from the Validator 
report page, not a howler from an alt tutorial:

			<img src="http://www.w3.org/QA/Tools/I_heart_validator" alt="I heart 
Validator logo" title=" Validators Donation Program" width="80" 
height="15" />

Yucca

Received on Wednesday, 6 February 2013 11:17:41 UTC