[imps] validator front end not talking to servlet

[Rancid Iodine]

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.

HTML5 = http://myfqdn.com:8888/
CompoundXML = http://myfqdn.com.com:8888/

INSTEAD of that which is recommended in the documentation i.e.

HTML5 = http://127.0.0.1:8888/html5/
CompoundXML = http://127.0.0.1:8888/

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:

python build/build.py --w3cbranding --port=8888 --local run

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.



On 19 April 2013 10:07, Rancid Iodine <rancid.iodine at gmail.com> wrote:

> Nice, I had no idea about that option, or indeed the nature of
> validator.nu vis-a-vis w3c, thanks very much.
>
> Saying that, the --w3cbranding option doesn't come up if you do
>
>  python build/build.py --help ...
>
> 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
>
> python build/build.py --w3cbranding --port=8888 --local run
>
> you can't actually see the branding as you would on
> http://validator.w3.org/nu/ ...
>
> Are all these issues maybe a case of us using an older version of
> validator.nu possibly, or are there some other components I could
> download that would make it all look like http://validator.w3.org/nu/  ?
>
> Cheers,
>
> Andrei
>
> On 18 April 2013 23:52, Michael[tm] Smith <mike at w3.org> wrote:
>
>> "Michael[tm] Smith" <mike at w3.org>, 2013-04-19 07:34 +0900:
>>
>> > Rancid Iodine <rancid.iodine at gmail.com>, 2013-04-18 18:13 +0100:
>> >
>> > > Michael once said to me to get rid of the legacy w3c validator
>> altogether
>> > > (considering the validator.nu does a better job validating any
>> version of
>> > > HTML), but we're in a corporate "situation" here wherein I'm told
>> they will
>> > > not accept any validator unless it has a "w3c" stamped on it's
>> forehead ...
>> > > which validator.nu does not have.
>> >
>> > The W3C instance at http://validator.w3.org/nu/ does. Even the URL
>> alone does.
>> > http://validator.w3.org/nu/about.html makes it quite clear that it's an
>> > official W3C product/service -- the "W3C Nu Markup Validator". I'm not
>> sure
>> > what more I could do to stamp "W3C" on it clearly.
>>
>> Note that if you want to run the service locally with the W3C branding,
>> you
>> just need to start it with the --w3cbranding option, like this:
>>
>>   ./build/build.py --w3cbranding
>>
>> --
>> Michael[tm] Smith http://people.w3.org/mike
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/implementors-whatwg.org/attachments/20130419/1475fbfc/attachment-0003.htm>