This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Seems that the validator doesn't support local files anymore I sent this file: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <title>Untitled Document</title> </head> <body> </body> </html> and got Error found while checking this document as HTML 4.01 Transitional! Result: 1 Error, 2 warning(s) No Character Encoding Found! Falling back to UTF-8. Unable to Determine Parse Mode! Validation Output: 1 Error Line 1, Column 0: end of document in prolog.
This bug is valid. When uploading (maybe other cases too), the validator intermittently claims "end of document in prolog" when the document is not blank. It will even occur with a completely valid document; after a few retries, the document will validate perfectly. I don't know what the cause is but it's difficult to reproduce because it doesn't occur every time.
The problem we have is that a bug in the validator (currently fixed in dev but yet to be pushed to validator.w3.org) fills up the hard drive and breaks file upload capability. I cleaned up the drive... again. Looking forward to the next release.
I figured it was something like that. I just don't know why this is marked WORKSFORME.
*** Bug 6520 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > I figured it was something like that. I just don't know why this is marked > WORKSFORME. Not sure either. The OP the status to WORKSFORME (as in, can't reproduce) back in October. I'm changing to Resolved FIXED since the fix is in CVS and the release is upcoming (our usual practice).
For reference, the patch applied is at: http://lists.w3.org/Archives/Public/www-validator-cvs/2009Feb/0025.html
Glad to know it's fixed, but shouldn't you be using logrotate (http://linuxcommand.org/man_pages/logrotate8.html) or something to ensure this doesn't happen again with a different kind of error.
(In reply to comment #7) > Glad to know it's fixed, but shouldn't you be using logrotate > (http://linuxcommand.org/man_pages/logrotate8.html) or something to ensure this > doesn't happen again with a different kind of error. We do :) but keep in mind that we're talking about the validator here, with millions of hits daily, so any problem will fill up a log partition very, very fast (in a matter of days, actually) regardless of logrotate settings.
I'm having this problem as well, i've tried some random domains (with content of course) and i keep getting : Line 1, Column 1: end of document in prolog I tried to revalidate a couple of times and it did worked but only once.
The validator does not appear to be working with local files (again). Just wanted to make you aware of it and hope that someone is on the case!
This is happening at the moment intermittently with files being uploaded. I am on an OU course which requires us to submit files which validate, and lots of people on the course are reporting this error on the forums. Submission of xhtml doctypes return the error message as below: Error found while checking this document as HTML 4.01 Transitional! Result: 1 Error, 2 warning(s) No Character Encoding Found! Falling back to UTF-8. Unable to Determine Parse Mode! Validation Output: 1 Error Line 1, Column 0: end of document in prolog.elow:
One server had his disks full. After cleaning it seems fine again.