This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 30225 - W3C Validation fails on https site
Summary: W3C Validation fails on https site
Status: NEW
Alias: None
Product: Validator
Classification: Unclassified
Component: Parser (show other bugs)
Version: HEAD
Hardware: PC Windows NT
: P2 major
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
Depends on:
Reported: 2018-02-25 22:59 UTC by Horace
Modified: 2018-03-26 15:25 UTC (History)
0 users

See Also:


Description Horace 2018-02-25 22:59:36 UTC
Recently converted several sites to https.  Did so by suggested changes in httpd.conf which allows access to the old http urls to be forced onto an https connection.  The site performs well and all major browsers render the site fin. However, when I try to validate the site using the W3C validator, it fails with the message "500 Can't connect to" ... is one of the sites.

the server definitions in httpd.conf are...

    #    ServerAdmin
            Redirect /
            #RewriteEngine on
            #RewriteCond %{HTTPS} off
            #RewriteCond %{SERVER_PORT} !^443$
            #RewriteRule ^/(.*) https://%{HTTP_HOST}/$1 [NC,R=301,L]
Both ports are listened to.

On another site,, there seems to be an issue with the use of a local dtd which defines a local tag used for indexing only and several attributes used for paypal.  The local dtd has been in yse since 2007 and there have been no issues with validation. However, after converting previously http part of the site to https, the local dtd seems to cause a blocking issue with the W3C validator.
Comment 1 Horace 2018-02-26 04:13:47 UTC
A little more info: I watched the error+log and saw that it looks like the validator fails the ssl handshake when accessing the server.
Comment 2 Horace 2018-03-26 15:25:41 UTC
So - I'm confused? Posted this a month ago - I saw it was assigned but no response at all?? hmmmmm