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 7262 - Validation generates 500 error on validating RDFa document.
Summary: Validation generates 500 error on validating RDFa document.
Alias: None
Product: Validator
Classification: Unclassified
Component: Parser (show other bugs)
Version: 0.8.5
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
Depends on:
Reported: 2009-08-11 16:06 UTC by Michiel Roos
Modified: 2009-08-13 17:41 UTC (History)
0 users

See Also:


Description Michiel Roos 2009-08-11 16:06:54 UTC
Example document:

Expected result: a verdict

Observed result: 500 internal server error.
Comment 1 Ville Skyttä 2009-08-12 04:38:19 UTC
I cannot reproduce, works fine when I try it out.  Perhaps some kind of a transient problem?
Comment 2 Michiel Roos 2009-08-12 07:27:30 UTC
Are these services location based? Do I reach another validator machine than you? I'm in Holland, Den Bosch.

My request for validation just does not return for a long time and then gives a 500. 

I just tried again.

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [no address given] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Apache/2.2.9 (Debian) mod_python/3.3.1 Python/2.5.2 Server at Port 80
Comment 3 Ville Skyttä 2009-08-13 16:04:40 UTC
Could be, or it could be that the server that serves the alice-example.html ends up being different for us.  Anyway, I've tested validator instances in Finland (my own) and Japan (W3C QA development server), it works from both.

Do you get these errors when validating any other documents than your example?
Comment 4 Michiel Roos 2009-08-13 17:41:47 UTC
As of today, I can no longer reproduce the 500 error.

Please close this bug.



A 'glitch' hopefully.