W3C Validator not working correctly

  • Advertisement ( why? )
     

    DesktopboB, 25th Feb 2013 12:30 pm

    Starting around last Wednesday or Thursday the link to the W3C Validator doesn't work correctly when trying to validate local files.

    I noticed it first with trying to validate HTML 5 documents (which have not caused a problem before, but it is also failing with XHTML 1.0.

    This is using the button for check the markup of HTML on the Tools tab of the menu bar.

    What I'm getting is:
    Status: 403 Forbidden Vary: Referer Content-type: text/html
    Sorry! This document can not be checked.
    No User-Agent header found!

    The documents that fail as local work fine when tested on the web and have all validated correctly (meaning the header is unchanged from when previous validations) in the past.

    Has W3C changed something that Tools can't access now??

    Thanks,
    boB

    • tlc44, 27th Feb 2013 8:23 am

      I am having a similar or the same problem. I am getting this error, where previously I have had no problems.

      I don't know how to interpret the error, nor how to resolve the problem, but right now I can't validate any code.

      Markup Validation Service
      Check the markup (HTML, XHTML) of Web documents

      Sorry! This document can not be checked.
      No User-Agent header found!
      Please identify your software properly by providing the HTTP User-Agent string. Default from an underlying library (eg Java, Ruby, Coda, libwww) is not sufficiently unique in identifying your software. A good practice is to include a URI to more information about your service or software.

      • HTML-Kit Support, 27th Feb 2013 1:56 pm

        On 2/27/2013 8:23 AM, tlc44 wrote:

        I am having a similar or the same problem. I am getting this error,
        where previously I have had no problems.

        I don't know how to interpret the error, nor how to resolve the
        problem, but right now I can't validate any code.

        Markup Validation Service
        Check the markup (HTML, XHTML) of Web documents

        Sorry! This document can not be checked.
        No User-Agent header found!
        Please identify your software properly by providing the HTTP
        User-Agent string. Default from an underlying library (eg Java,
        Ruby, Coda, libwww) is not sufficiently unique in identifying your
        software. A good practice is to include a URI to more information
        about your service or software.

        Thank you for reporting this guys! I was able to reproduce it and looks
        like something has changed on W3C Validator side as boB suspected.

        I'm working on getting Tools to work with this change. Will post again...

        Chami

        • HTML-Kit Support, 4th Mar 2013 10:41 pm

          On 2/27/2013 1:56 PM, HTML-Kit Support wrote:

          On 2/27/2013 8:23 AM, tlc44 wrote:

          I am having a similar or the same problem. I am getting this error,
          where previously I have had no problems.

          I don't know how to interpret the error, nor how to resolve the
          problem, but right now I can't validate any code.

          Markup Validation Service
          Check the markup (HTML, XHTML) of Web documents

          Sorry! This document can not be checked.
          No User-Agent header found!
          Please identify your software properly by providing the HTTP
          User-Agent string. Default from an underlying library (eg Java,
          Ruby, Coda, libwww) is not sufficiently unique in identifying your
          software. A good practice is to include a URI to more information
          about your service or software.

          Thank you for reporting this guys! I was able to reproduce it and looks
          like something has changed on W3C Validator side as boB suspected.

          I'm working on getting Tools to work with this change. Will post again...

          Chami

          Just posted a new TreeHouse build to support this change in W3C Validator:

          http://www.htmlkit.com/assistant/

          Let me know if this doesn't help.

          Chami

          • DesktopboB, 5th Mar 2013 11:24 am

            Chami,
            Just tried out the Treehouse Build and it does connect but....

            (Yeah, you knew there was a "but" coming).

            Not to whine, but the time from clicking the validate button to the actual validation results are very slow...over 30-45 seconds in each test I did.

            The pages aren't overly large that I used and the response time we pretty much the same whether I was validating for the first time, or using the link at the bottom of the editor window to "run validator again".

            On the plus side, the validator now recognizes HTML 5!

            Not sure what I'm running into and I'll try testing again later this afternoon to see if there is some clog in my Internet connection (it's been working well this morning, so I don't think that is the problem).

            Thanks,
            boB

            • HTML-Kit Support, 5th Mar 2013 11:45 am

              On 3/5/2013 11:24 AM, DesktopboB wrote:

              Chami,
              Just tried out the Treehouse Build and it does connect but....

              (Yeah, you knew there was a "but" coming).

              Not to whine, but the time from clicking the validate button to the
              actual validation results are very slow...over 30-45 seconds in each
              test I did.

              The pages aren't overly large that I used and the response time we
              pretty much the same whether I was validating for the first time, or
              using the link at the bottom of the editor window to "run validator
              again".

              On the plus side, the validator now recognizes HTML 5!

              Not sure what I'm running into and I'll try testing again later this
              afternoon to see if there is some clog in my Internet connection
              (it's been working well this morning, so I don't think that is the
              problem).

              Thanks,
              boB

              Thanks for checking it out, boB, and for confirming that the W3C Markup
              Validator plugin is working.

              I too noticed that the validator is running slow but this doesn't seem
              to be an issue with HTML-Kit Tools. http://validator.w3.org (outside of
              HTML-Kit) is also running slow for me at the moment. For comparison, if
              you click the W3C CSS Validator button you'll notice that it comes up
              right away.

              Chami

              • DesktopboB, 5th Mar 2013 5:48 pm

                Chami,
                Checking back in in the late afternoon (3:45 round these parts).

                The HTML Validator seems to be back up and running up to speed.
                The CSS works as well, although it was also slow this morning.

                Must be a disturbance in the force.

                I'll keep you posted if I run into any other problems, but all seems to be working now.

                Thanks,
                boB

                • killdill045, 22nd Nov 2014 10:50 pm

                  The time from clicking the validate button to the actual validation results are very slow...over 30-45 seconds in each test I did.

                  The pages aren't overly large that I used and the response time we pretty much the same whether I was validating for the first time, or using the link at the bottom of the editor window to "run validator again".?


                  GuL

                  • HTML-Kit Support, 29th Nov 2014 2:22 pm

                    On 11/22/2014 10:50 PM, killdill045 wrote:

                    The time from clicking the validate button to the actual validation
                    results are very slow...over 30-45 seconds in each test I did.

                    The pages aren't overly large that I used and the response time we
                    pretty much the same whether I was validating for the first time, or
                    using the link at the bottom of the editor window to "run validator
                    again".?


                    GuL

                    Hi,

                    I'm afraid the speed of W3C Validator is going to fluctuate as with any
                    online service. It's responsive right now (took about three seconds when
                    I just tried it through HTML-Kit Tools) but it wouldn't surprise me to
                    see it slow down with high demand. Let me know if you're seeing this
                    delay all times of the day.

                    Chami