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 6950 - 500 internal error returned while checking
Summary: 500 internal error returned while checking
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: HEAD
Hardware: All All
: P2 major
Target Milestone: 0.8.6
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
: 7822 8570 (view as bug list)
Depends on:
Reported: 2009-05-25 04:23 UTC by Gioacchino La Vecchia
Modified: 2010-03-02 18:45 UTC (History)
4 users (show)

See Also:


Description Gioacchino La Vecchia 2009-05-25 04:23:30 UTC
Site owner signals a 500 error I just verified while checking
After the check button is pressed against such a site validator
doesn't answer for a while and the return the 500 Internal Server Error
Comment 1 waheed 2009-07-16 06:15:10 UTC
I have installed the validator,

but when i click on check, i following error
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, 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.0.63 (Win32) Server at Port 80

Kindly  help me tocorrect this problem as soon as poosible. i have tried many ways so tell me any advance and sophisticated solution.
Comment 2 Etienne Miret 2009-08-17 14:02:33 UTC
(In reply to comment #0) (v0.8.5) behaves exactly as Gioacchino said, however my locally installed Validator (HEAD from CVS) has no trouble validating that same page (which is a 404 by the way).

Either the bug is corrected in the CVS, either it’s an installation specific problem in the official validator instance.
Comment 3 Ville Skyttä 2009-12-10 19:28:50 UTC
I suspect that the instance times out when trying to retrieve the document, it takes a long time before the 500 Internal Server Error occurs.  Why that happens, I don't know, but one possibility is that the server or something between it and the validator does that for connection attempts originating from

I have lowered the default user agent inactivity timeout to 45 seconds in the development version (was LWP's default, documented to be 180 seconds on my box); that should at least cause a better error message than "500 Internal Server Error" in more cases also on  See bug 4985 for more information.
Comment 4 Ville Skyttä 2009-12-10 20:01:58 UTC
*** Bug 7822 has been marked as a duplicate of this bug. ***
Comment 5 Ville Skyttä 2009-12-30 19:46:42 UTC
*** Bug 8570 has been marked as a duplicate of this bug. ***
Comment 6 Ville Skyttä 2010-03-02 18:45:21 UTC
0.8.6 outputs a better error message on timeouts.