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 www.tennispensacola.com:443" ... tennispensacola.com is one of the sites.

the server definitions in httpd.conf are...

    <VirtualHost 216.127.95.86:80>
        ServerName tennispensacola.com
        ServerAlias www.tennispensacola.com
    #    ServerAdmin webmaster@tennispensacola.com
        ServerAdmin webmaster@hav.com
            Redirect / https://www.tennispensacola.com/
            #RewriteEngine on
            #RewriteCond %{HTTPS} off
            #RewriteCond %{SERVER_PORT} !^443$
            #RewriteRule ^/(.*) https://%{HTTP_HOST}/$1 [NC,R=301,L]
    </VirtualHost>
    #===========================
    <VirtualHost 216.127.95.86:443>
        ServerName tennispensacola.com
        ServerAlias www.tennispensacola.com
       ServerAdmin webmaster@tennispensacola.com
 
Both ports are listened to.
	

On another site, backbenimble.com, 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.