<div dir="ltr"><div><div><div>Hold the phone, I have a startling development. I've just managed to get past the "504 gateway error" by specifying the externally visible FQDN in /etc/w3c/validator.conf i.e. <br>
<br>HTML5 = <a href="http://myfqdn.com:8888/">http://myfqdn.com:8888/</a><br>CompoundXML = <a href="http://myfqdn.com.com:8888/">http://myfqdn.com.com:8888/</a><br><br></div>INSTEAD of that which is recommended in the documentation i.e.<br>
<br>HTML5 = <a href="http://127.0.0.1:8888/html5/">http://127.0.0.1:8888/html5/</a><br>CompoundXML = <a href="http://127.0.0.1:8888/">http://127.0.0.1:8888/</a><br><br></div>BTW I am running on Centos 6.0 (already a little old now, but I don't think distro or version makes a heap of difference) and starting the servlet now like so now:<br>
<br>python build/build.py --w3cbranding --port=8888 --local run<br><br></div>Despite running with --local as you can seee, the problem I encountered earlier seems to be down to a basic failure to make localhost listen on that port.<br>
<div><div><div> <br></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 19 April 2013 10:07, Rancid Iodine <span dir="ltr"><<a href="mailto:rancid.iodine@gmail.com" target="_blank">rancid.iodine@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">Nice, I had no idea about that option, or indeed the nature of <a href="http://validator.nu" target="_blank">validator.nu</a> vis-a-vis w3c, thanks very much.<br>
<br></div><div class="gmail_extra">Saying that, the --w3cbranding option doesn't come up if you do <br>
<br> python build/build.py --help ...<br><br></div><div class="gmail_extra">This doesn't mean the option doesn't work, but I had to download missing .pngs to the checker/validator/site directory, and even then when you run<br>
</div><div class="gmail_extra"><br>python build/build.py --w3cbranding --port=8888 --local run <br><br>you can't actually see the branding as you would on <a href="http://validator.w3.org/nu/" target="_blank">http://validator.w3.org/nu/</a> ...<br>
</div><div class="gmail_extra"><br></div><div class="gmail_extra">Are all these issues maybe a case of us using an older version of <a href="http://validator.nu" target="_blank">validator.nu</a> possibly, or are there some other components I could download that would make it all look like <a href="http://validator.w3.org/nu/" target="_blank">http://validator.w3.org/nu/</a> ?<br>
<br></div><div class="gmail_extra">Cheers,<br><br>Andrei<br></div><div><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 18 April 2013 23:52, Michael[tm] Smith <span dir="ltr"><<a href="mailto:mike@w3.org" target="_blank">mike@w3.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">"Michael[tm] Smith" <<a href="mailto:mike@w3.org" target="_blank">mike@w3.org</a>>, 2013-04-19 07:34 +0900:<br>
<div><br>
> Rancid Iodine <<a href="mailto:rancid.iodine@gmail.com" target="_blank">rancid.iodine@gmail.com</a>>, 2013-04-18 18:13 +0100:<br>
><br>
> > Michael once said to me to get rid of the legacy w3c validator altogether<br>
> > (considering the <a href="http://validator.nu" target="_blank">validator.nu</a> does a better job validating any version of<br>
> > HTML), but we're in a corporate "situation" here wherein I'm told they will<br>
> > not accept any validator unless it has a "w3c" stamped on it's forehead ...<br>
> > which <a href="http://validator.nu" target="_blank">validator.nu</a> does not have.<br>
><br>
> The W3C instance at <a href="http://validator.w3.org/nu/" target="_blank">http://validator.w3.org/nu/</a> does. Even the URL alone does.<br>
> <a href="http://validator.w3.org/nu/about.html" target="_blank">http://validator.w3.org/nu/about.html</a> makes it quite clear that it's an<br>
> official W3C product/service -- the "W3C Nu Markup Validator". I'm not sure<br>
> what more I could do to stamp "W3C" on it clearly.<br>
<br>
</div>Note that if you want to run the service locally with the W3C branding, you<br>
just need to start it with the --w3cbranding option, like this:<br>
<br>
./build/build.py --w3cbranding<br>
<div><div><br>
--<br>
Michael[tm] Smith <a href="http://people.w3.org/mike" target="_blank">http://people.w3.org/mike</a><br>
</div></div></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>