Community
Participate
Working Groups
Build ID: I20100520-1744 (3.6rc2) 1. Help > Contents 2. Run a broken hyperlink finder on .../help/index.jsp --> Log (attachment 169872 [details] on bug 314322) shows 1 messages about a missing element from org.eclipse.platform.doc.isv: Error Tue May 25 14:58:35 CEST 2010 Error processing help request org.eclipse.platform.doc.isv/reference/extension-points/cheatSheetContentFileSpec.exsd A couple more broken links are reported by the link spider report for platform.doc.isv - see attachment 169874 [details] (zipped .html) on bug 314322. For example: http://127.0.0.1:4911/help/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/runtime/ error code: 204 (no info to return), linked from page(s): http://127.0.0.1:4911/help/topic/org.eclipse.platform.doc.isv/reference/api/index-files/index-5.html http://127.0.0.1:4911/help/topic/org.eclipse.platform.doc.isv/reference/api/index-files/index-9.html http://127.0.0.1:4911/help/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/ui/navigator/ error code: 204 (no info to return), linked from page(s): http://127.0.0.1:4911/help/topic/org.eclipse.platform.doc.isv/reference/api/index-files/index-9.html
Here is a broken external link: http://citeseer.ist.psu.edu/myers86ond.html error code: 12029 (no connection), linked from page(s): http://127.0.0.1:4911/help/topic/org.eclipse.platform.doc.isv/guide/compare_contentviewer.htm
>Here is a broken external link: >http://citeseer.ist.psu.edu/myers86ond.html >error code: 12029 (no connection), linked from page(s): >http://127.0.0.1:4911/help/topic/org.eclipse.platform.doc.isv/guide> >/compare_contentviewer.htm See bug 314400. >error code: 403 (forbidden request), linked from page(s): These all work fine for me. Looks like you're not allowed to access wikipedia ;-) >/api/index-files/index*.html Those might be wrong links in Javadoc. Need to take a closer look on these...
I cannot find anything suspicious in the source of those index files. They are generated by Javadoc and HTTP status code 204 doesn't necessarily mean that a link is broken.
>I cannot find anything suspicious in the source of those index files. They are >generated by Javadoc and HTTP status code 204 doesn't necessarily mean that a >link is broken. Ha - Found it! Running my own checker that also shows the link name/title, I found out that it's a problem with a relative links used inside some classes, see bug 314411 and bug 314413.
Is your link spider freely available?
>Is your link spider freely available? You know what: I used the same as you ;-) It looks like the title/name is only in the GUI but not in the report.
