A timeout occurred (in 63.7s) for the request "http://x.x/reisen/aegypten/aegypten_04.php". Error: 3, Status: 404, Reason: Connection aborted on request. This target will not be processed.
I would like to change these errors but I don't know on which page the error is coded. Perhaps I missed a configuration option.
If you look at the link reports (when link checking is on), then the redirected links and links that timeout should typically show up, so you know in which document to look.
I will make a note to try to supply this information (the parent link) in those Batch Wizard progress messages in a future version. That should make it easier to fix the document that references the redirected or bad link.
... link checking ... "Target Proporties" / "Follow Links" / "Follow and validate links is checked"
are there more/other check I have to check?
Please where is the "link report"? After
batch checking my browser opens a new windows titled "[Summary Page] Batch Wizard Report" and 4 chapters
1. Documents with errors
2. Documents with warnings
3. Documents with no errors or warnings
Important Messages/Errors From Job Run (there are all these errors printed)
but no "link report".
Thanks,
Alexander
Last edited by AlexanderP on Mon Mar 07, 2011 9:24 am, edited 1 time in total.
You can enable link checking in the Tool to Use Page of the Batch Wizard Options, then you should get link reports for each target (if there is anything to report).
To check only certain links, you can use the "Check only these links" option in the Target List Tab of the Batch Wizard and specify something like this "*yourdomain.com*" (without the quotes).
Important Messages/Errors From Job Run
The request for "http://127.0.0.1/album/foto-index.php" was redirected to "http://127.0.0.1/album/".
The request for "http://127.0.0.1/reisen/prag-2007" was redirected to "http://127.0.0.1/reisen/prag-2007/".
The request for "http://127.0.0.1/reisen/sofia-2010" was redirected to "http://127.0.0.1/reisen/sofia-2010/".
The request for "http://127.0.0.1/reisen/sardinien-2007" was redirected to "http://127.0.0.1/reisen/sardinien-2007/".
The request for "http://127.0.0.1/reisen/wien" was redirected to "http://127.0.0.1/reisen/wien/".
A timeout occurred (in 73.6s) for the request "http://127.0.0.1/reisen/_vietnam-kambodscha-2011/vietnam-kambodscha_15.php". Error: 3, Status: 404, Reason: Connection aborted on request. This target will not be processed.
A timeout occurred (in 75.5s) for the request "http://127.0.0.1/reisen/_vietnam-kambodscha-2011/vietnam-kambodscha_00.php". Error: 3, Status: 404, Reason: Connection aborted on request. This target will not be processed.
A timeout occurred (in 75.5s) for the request "http://127.0.0.1/reisen/_vietnam-kambodscha-2011/vietnam-kambodscha_01.php". Error: 3, Status: 404, Reason: Connection aborted on request. This target will not be processed.
A timeout occurred (in 73.6s) for the request "http://127.0.0.1/reisen/_vietnam-kambodscha-2011/vietnam-kambodscha_17.php". Error: 3, Status: 404, Reason: Connection aborted on request. This target will not be processed.
A timeout occurred (in 75.1s) for the request "http://127.0.0.1/reisen/_vietnam-kambodscha-2011/vietnam-kambodscha_05.php". Error: 3, Status: 404, Reason: Connection aborted on request. This target will not be processed.
A timeout occurred (in 60.3s) for the request "http://127.0.0.1/reisen/peru-2009/peru_04.php". Error: 3, Status: 404, Reason: Connection aborted on request. This target will not be processed.
A timeout occurred (in 60.6s) for the request "http://127.0.0.1/reisen/spanien/spanien_13.php". Error: 3, Status: 404, Reason: Connection aborted on request. This target will not be processed.
A timeout occurred (in 60.6s) for the request "http://127.0.0.1/reisen/spanien/spanien_k.php". Error: 3, Status: 404, Reason: Connection aborted on request. This target will not be processed.
These errors are not displayed at section "4. Documents with bad links".
Thanks, Alexander
AlexanderP wrote:I found some other links, which I could not find, where the error is
Hello,
Are you willing to test a new version? If so, then please email me at support at htmlvalidator dot com. The new version will include the parent target of Batch Wizard progress messages like that.
As an alternative, you may want to set redirected links to show as errors in the Link Checking options page in the Validator Engine Options. That may cause the desired reports to be generated which may not otherwise be generated.
You could also try the "Always generate a link report" option in the Report Options->Link Report page of the Batch Wizard Options. That should cause all link reports to be generated, even ones with only warnings or only good links.
Thanks Albert,
I will go at first using the option always error. Works fine.
I'm not quit sure, but it looks like that a target like "page.php#wrong" and the anchor "wrong" doesn't exist result as time out but no error message where the "page.php#wrong" is used.
AlexanderP wrote:I'm not quit sure, but it looks like that a target like "page.php#wrong" and the anchor "wrong" doesn't exist result as time out but no error message where the "page.php#wrong" is used.
Hello,
I'm sorry for the delay.
Please note that CSE HTML Validator does not link check anchors except for anchors that reference elements in the same document.
Also, using an invalid anchor shouldn't cause a time out error for the URL. That is, if you are getting a timeout, then it shouldn't be because the anchor is wrong.
If you find that the above isn't the case, then please describe in detail how to reproduce the problem you are running into and I will investigate.
you described my problem perfect. Thanks!
Do you think, you could implement such an link check - anchors that reference elements points to a different document - to one of your next CSE HTML Validator version? I would be very happy.
AlexanderP wrote:you described my problem perfect. Thanks!
Do you think, you could implement such an link check - anchors that reference elements points to a different document - to one of your next CSE HTML Validator version? I would be very happy.
Your welcome!
This feature (anchor checking across documents) has "been on our radar" for possible implementation, but I can't be sure when or if it will be added (depends on time and priorities). I will definitely consider it for v11.