|
| LinkScan for Unix. Reference Manual. | Section 7 |
| Previous Contents Next | Help Reference HowTo Card |
The following section describes each of the LinkScan Error and Status Codes. Each Status Code is assigned to one of six Severities:
| Symbol | Code | Severity | Explanation |
 |
0 | Unknown: | LinkScan has not tested or was unable to test this link |
 |
1 | Error: | LinkScan found a hard error on this link |
 |
2 | Possible Error: | There may be a problem with this link. It should be retested at a later time |
 |
3 | Warning: | LinkScan found something unusual about this link. Manual inspection highly recommended |
 |
4 | Advisory: | This link is probably ok, but manual inspection recommended |
 |
5 | No Error: | This is a good link |
The Severity associated with any specific Error or Status Code may be customized by the LinkScan Administrator through the use of the Statuscode option.
Status codes in the range 0-99 are generated exclusively by LinkScan and generally refer to the status of local links (HTML files, Non-HTML files, etc.).
Status codes in the range 100-699 are defined exclusively by the HyperText Transfer Protocol.
Status codes in the range 800-3099 are generated exclusively by LinkScan and generally refer to Networking Problems (Failed DNS lookups, failure to connect to a remote server or timeouts) as well as some other LinkScan detected warning or advisory messages.
No Status (0)Explanation: This object has not been tested.
Action: Inspect this link manually.
HTML File (1)Explanation: This HTML document was found OK.
Action: None required.
Error: Bad HTML File (2)Explanation: The Referring document is linked to an HTML file that does not exist on your server.
Action: Create/restore the missing file or correct the erroneous reference.
Non-HTML File (3)Explanation: This non-HTML file was found OK.
Action: None required.
Error: Bad non-HTML File (4)Explanation: The Referring document is linked to a non-HTML file that does not exist on your server.
Action: Create/restore the missing file or correct the erroneous reference.
Anchor (5)Explanation: The corresponding <a name=> tag was found OK.
Action: None required.
Error: Bad Anchor (6)Explanation: The Referring document is linked to a <a name=> tag that does not exist within the target document.
Action: Create/restore the missing tag or correct the erroneous reference.
Warning: Orphaned HTML File (7)Explanation: This HTML file cannot be reached (directly or indirectly) from your home page.
Action: Check whether this is intentional or an error.
Warning: Orphaned non-HTML File (8)Explanation: This non-HTML file cannot be reached (directly or indirectly) from your home page.
Action: Check whether this is intentional or an error.
Imagemap File (9)Explanation: This server-side Imagemap file was found OK.
Action: None required.
Error: Bad Imagemap File (10)Explanation: The Referring document is linked to a server side Imagemap file that does not exist on your server.
Action: Create/restore the missing file or correct the erroneous reference.
Valid Mailto Link (11)Explanation: This mailto: link appears valid based on an examination of the tag and E-mail address syntax.
Action: None required.
Possible Error: Invalid Mailto Link (12)Explanation: This mailto: link appears invalid based on an examination of the tag and E-mail address syntax.
Action: Inspect this link manually.
Warning: Missing / (13)Explanation: This link is almost certainly missing a trailing "/". LinkScan was able to validate the link by adding the "/".
Action: Add a "/" character to the end of the existing URL. This omission, although not normally fatal, may cause visitors that try to follow the link problems or delays.
Warning: Unprocessed SSI (14)Explanation: LinkScan identified but did not process this Server Side Include (SSI). If you are scanning the website via Network (HTTP) Access, your server failed to process the SSI and the served document may be incomplete!
Action: Inspect this Server Side Include manually.
PDF File (15)Explanation: This PDF document was found OK.
Action: None required.
Error: Bad PDF File (16)Explanation: The Referring document is linked to a PDF document that does not exist on your server.
Action: Create/restore the missing file or correct the erroneous reference.
Warning: No Closing /a (17)Explanation: LinkScan found a tag of the form <A HREF=...> with no corresponding </A> tag. This check is not enabled in a default configuration.
Action: Correct the markup. Mismatched tags may cause problems with some or all browsers. If very large numbers of these errors "clog" the LinkScan database, this check may be disabled via the Closeatag setting.
Error: Invalid Scheme (18)Explanation: This link uses a scheme that LinkScan did not recognize as valid. LinkScan validates various schemes (http:, https:, ftp:, ldap:, mailto:). It is aware of, but does not validate, other common schemes (e.g. gopher:, news:) and these are stored with No Status. This link uses an unknown scheme. It may caused by a typographical error.
Note: links using the file: scheme are always marked with an Invalid Scheme Error. The use of the file: scheme is rarely desirable (or intended) in published documents and generally indicates an oversight.
Action: Inspect/correct this link manually. In rare cases, when the use of the file: scheme is actually intended, use an Exclude or Substitute command to modify the LinkScan behavior as appropriate.
Advisory: No Alt/Height/Width (20)Explanation: The Referring document contains an IMG SRC tag without the ALT, HEIGHT and/or WIDTH attributes.
Action: Adjust the specified IMG SRC tag.
Flash File (21)Explanation: This Flash document was found OK.
Action: None required.
Error: Bad Flash File (22)Explanation: The Referring document is linked to a Flash document that does not exist on your server.
Action: Create/restore the missing file or correct the erroneous reference.
Text File (23)Explanation: This Text document was found OK.
Action: None required.
Error: Bad Text File (24)Explanation: The Referring document is linked to a Text document that does not exist on your server.
Action: Create/restore the missing file or correct the erroneous reference.
Javascript File (25)Explanation: This Javascript document was found OK.
Action: None required.
Error: Bad Javascript File (26)Explanation: The Referring document is linked to a Javascript document that does not exist on your server.
Action: Create/restore the missing file or correct the erroneous reference.
XML File (27)Explanation: This XML document was found OK.
Action: None required.
Error: Bad XML File (28)Explanation: The Referring document is linked to a XML document that does not exist on your server.
Action: Create/restore the missing file or correct the erroneous reference.
Error: HTML Syntax (99)Explanation: An HTML Syntax Error was found.
Action: Correct the HTML markup.
Continue (100)Explanation: This HTTP Status Code will not normally arise with LinkScan.
Action: Inspect this link manually.
Switching Protocols (101)Explanation: This HTTP Status Code will not normally arise with LinkScan.
Action: Inspect this link manually.
Good URL (200, 201, 202, 203, 205, 206)Explanation: LinkScan found a good (external) URL.
Action: None required.
Error: No Content (204)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Error: Multiple Choices (300)Explanation: The target server requires a language selection before serving the applicable document.
Action: Add a command to the linkscan.cfg file such as:
Extraheader Accept-Language: en
Error: Moved Permanently (301)Explanation: This URL has moved permanently.
Action: Update this link as soon as possible. The redirection instruction may expire shortly, making it harder for you to find the new location.
Advisory: Moved Temporarily (302)Explanation: The URL of the page retrieved is different from the URL of the page requested. This is a design feature of the referenced server. According to the http specifications, you should continue using the existing URL. However, in our experience, such links should be inspected manually. Some servers report redirections to temporary URL's that are specific to the current user session. It would clearly be undesirable to modify your existing hyperlinks in these situations. But, other servers return a 302 Status Code when the URL has in fact been moved "permanently".
Action: Inspect this link manually.
Error: Network/Server Error (303, 304)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Error: Use Proxy (305)Explanation: This link must be accessed via a proxy server.
Action: Inspect this link manually and contact your LinkScan Administrator.
Error: Unused (306)Explanation: This status code is no longer used and is reserved.
Action: Inspect this link manually and contact the Web Server Administrator.
Warning: Temporary Redirect (307)Explanation: This link is temporarily redirected.
Action: Inspect this link manually.
Error: Network/Server Error (400)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Warning: Unauthorized (401)Explanation: The remote server reported that you are not authorized to access the requested object. You may be able to access it manually if you supply a valid username and password.
Action: Inspect this link manually.
Warning: Payment Required (402)Explanation: The remote server reported that you are not authorized to access the requested object. You may be able to access it manually if you supply a valid username and password.
Action: Inspect this link manually.
Error: Forbidden (403)Explanation: The remote server understood the request but refused to fulfill it. Supplying a username and password will not help.
Action: Inspect this link manually.
Error: Not Found (404)Explanation: The remote server reported that the requested object does not exist. This condition is probably (but not necessarily) permanent.
Action: Inspect the link manually. A very small number of servers report a "Not Found" error when there is, in fact, no problem. In some cases, the server may display a "Moved" message even though it did not supply a "Moved" header.
Error: Method Not Allowed (405)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Error: Not Acceptable (406)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Error: Proxy Authentication Required (407)Explanation: The Proxy Server requires authentication.
Action: Review the LinkScan Proxy Server configuration settings or contact your LinkScan Administrator.
Possible Error: Request Timed Out (408)Explanation: The Request timed out.
Action: Check the link manually. This URL is currently unavailable. LinkScan was not able to establish whether the situation is temporary or permanent. You may wish to probe the site using the standard ping and traceroute utilities.
Error: Conflict (409)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Error: Gone (410)Explanation: The remote server reported that the requested object does not exist. The condition is permanent and no forwarding address is known.
Action: Inspect the link manually.
Error: Length Required (411)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Error: Precondition Failed (412)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Error: Request Entity Too Large (413)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Error: Request URI Too Large (414)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Error: Unsupported Media Type (415)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Possible Error: Server Error (500)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Possible Error: Not Implemented (501)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Possible Error: Bad Gateway (502)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Possible Error: Service Unavailable (503)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Possible Error: Gateway Timed Out (504)Explanation: The connection to the remote server timed out.
Action: Check the link manually. This URL is currently unavailable. LinkScan was not able to establish whether the situation is temporary or permanent. You may wish to probe the site using the standard ping and traceroute utilities.
Possible Error: HTTP Version Not Supported (505)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Possible Error: Network/Server Error (600, 601, 602, 603)Explanation: An unusual error occurred.
Action: Inspect this link manually.
Advisory: Skipped - Recently Test (800)Explanation: This link was skipped because it has been tested recently. See How to control the testing of external links.
Action: None required.
Possible Error: Skipped - Bad Server (801)Explanation: This link was skipped because an excessive number of other links to the same server appeared broken. The server is probably down, either temporarily or permanently. See How to control the testing of external links.
Action: Retest this link later and/or manually inspect the links to this server.
Advisory: Skipped - FTP Limit (802)Explanation: This link was skipped because the limit on the number of FTP links to any one server was exceeded. See How to control the testing of external links.
Action: Manually inspect this link and/or increase the Maxftp setting.
Advisory: Skipped - CGI Limit (803)Explanation: This link was skipped because the limit on the number times LinkScan checks the same CGI with different queries was exceeded. This avoids the possibility of LinkScan checking the same URL with a potentially infinite number of automatically generated query strings. See How to control clusters of links.
Action: Manually inspect this link and, if appropriate, increase the Maxcgi setting.
Possible Error: No DNS Entry (900)Explanation: LinkScan was unable to locate the requested server.
Action: Check the link manually. This server may no longer exist. Or, it is possible that the remote site's Domain Name Server (DNS) was temporarily unavailable at the time LinkScan tried to access it. You may wish to probe the site using the standard nslookup utility.
Possible Error: DNS Timeout (901)Explanation: LinkScan was unable to complete a DNS lookup.
Action: Check the link manually. This URL is currently unavailable. LinkScan was not able to establish whether the situation is temporary or permanent. You may wish to probe the site using the standard ping and traceroute utilities.
Possible Error: Connect Error (902)Explanation: LinkScan was unable to establish a TCP/IP connection to the remote server. Most likely, the remote server is currently rejecting connections.
Action: Check the link manually. This URL is currently unavailable. LinkScan was not able to establish whether the situation is temporary or permanent. You may wish to probe the site using the standard ping and traceroute utilities.
Possible Error: Connect Timeout (903)Explanation: A timeout arose while attempting to connect() to the remote server.
Action: Check the link manually. This URL is currently unavailable. LinkScan was not able to establish whether the situation is temporary or permanent. You may wish to probe the site using the standard ping and traceroute utilities.
Warning: Missing / (904)Explanation: This link is almost certainly missing a trailing "/". LinkScan was able to validate the link by adding the "/".
Action: Add a "/" character to the end of the existing URL. This omission, although not normally fatal, may cause visitors that try to follow the link problems or delays.
Warning: Probably OK (905)Explanation: The remote server did not supply a valid http header, but it did appear to serve up a valid HTML document.
Action: Inspect this link manually.
Warning: Contains an IP Address (906)Explanation: This link uses a numeric IP address. These addresses are much more likely to change than conventional server addresses referenced via the Domain Name Service (DNS).
Action: We recommend that you use a conventional URL if at all possible.
Error: Multiple Redirections (907)Explanation: This URL appeared to be subject to multiple redirections. LinkScan will follow up to five redirections. It then generates a 907 error rather than continue in a potentially infinite loop.
Action: We recommend that you inspect your server redirections (often defined in a .htaccess file).
Warning: Missing / (908)Explanation: This link is almost certainly missing a trailing "/". LinkScan was able to validate the link by adding the "/".
Action: Add a "/" character to the end of the existing URL. This omission may cause significant problems for some users that access the web via proxy servers.
Error: Disconnected (909)Explanation: This error typically results when a remote server disconnects a TCP/IP connection prematurely.
Action: Inspect this link manually. If problems persist, please contact LinkScan Technical Support at linkscan@elsop.com.
Warning: Location Not Absolute (910)Explanation: The server attempted to redirect the request to a different URL using an HTTP "Location" header but failed to supply an absolute URL as required by the HTTP specifications.
Action: Check the HTTP server configuration files and/or any CGI scripts that generate HTTP "Location" headers and ensure they transmit an absolute URL on redirections.
Error: Unsafe Character (911)Explanation: This link contains an 'unsafe' character; probably a control character or a non-encoded space (spaces in URL's should be written as "%20"). Different browsers will interpret this link differently.
Links written with a leading query... <A HREF="?Something"> will also be flagged with a 911 Error. Although strictly legal, we have found that different browsers process the tag in a wildly inconsistent manner. Include some or all of the pathname to avoid this problem and eliminate the error.
Action: We recommend that you inspect and correct this link.
Advisory: SSL Server Path Not Checked (912)Explanation: LinkScan was able to establish a TCP/IP connection to the specified port (Default: 443) on the specified server. LinkScan does not natively support SSL/HTTPS on Unix platforms and did not validate the pathname portion of the URL.
Action: We recommend that you inspect this link manually using a browser with SSL support if you wish to validate the complete URL.
Advisory: Simulated Redirect (913)Explanation: LinkScan processed a Redirect directive in the linkscan.cfg file.
Action: Check this link manually.
Warning: Meta Redirect (914)Explanation: LinkScan detected a redirection specified using a <META HTTP-EQUIV REFRESH> tag.
Action: This construct is not supported by all clients. We recommend that you at least insert a regular hyperlink in this document that will be visible by someone viewing the page.
Warning: Meta Loc not Absolute (915)Explanation: LinkScan detected a redirection specified using a <META HTTP-EQUIV REFRESH> tag. Furthermore, the target location was specified using a relative URL.
Action: This construct is not supported by all clients. We recommend that you specify the REFRESH using an Absolute URL and insert a regular hyperlink in this document that will be visible by someone viewing the page.
Advisory: LDAP Server Query Not Checked (916)Explanation: LinkScan was able to establish a TCP/IP connection to the specified port (Default: 389) on the specified server. LinkScan does not natively support LDAP and did not validate the query portion of the URL.
Action: We recommend that you inspect this link manually using a browser with LDAP support if you wish to validate the complete URL.
Error: No Headers Seen (917)Explanation: LinkScan connected to the remote server but did not receive any HTTP response headers.
Action: We recommend that you inspect this link manually.
Possible Error: Timeout Header (930)Explanation: A timeout arose after LinkScan connected established a connection to the remove server and during the exchange of HTTP Request and Response Headers.
Action: Check the link manually. This URL is currently unavailable. LinkScan was not able to establish whether the situation is temporary or permanent. You may wish to probe the site using the standard ping and traceroute utilities.
Possible Error: Timeout Body (931)Explanation: A timeout arose after LinkScan connected established a connection and exchanged HTTP Request and Response Headers but during the transmission of the document body. Typically this arises when LinkScan attempts to download a very large document (e.g. multi-MegaByte PDF file) over a limited bandwidth connection.
Action: Check the link manually.
Possible Error: Timeout Unknown (932)Explanation: A timeout arose but no other details are available.
Action: Check the link manually.
Warning: Body Truncated (933)Explanation: LinkScan downloaded an incomplete document body because the size exceeded the Maxdownload parameter.
Action: Check the link manually.
Error: Error Creating Socket (990)Explanation: LinkScan was not able to create a socket (network connection) while testing this link. This indicates an internal problem with LinkScan and/or your operating system.
Action: Contact LinkScan Technical Support at linkscan@elsop.com.
Error: SSL Error (991)Explanation: The Windows Internet Library was not able to access this URL. The remote server may have an invalid or unrecognized security certificate.
Action: Inspect this link manually.
Error: Post Data Not Found (992)Explanation: A data file referenced by a LinkScan multipart POST command was not found.
Action: Correct the POST command and/or supply the missing data.
Error: Unknown (999)Explanation: LinkScan was not able to establish the status of this link. This error tends to arise with approximately 0.1 percent of servers on the Web. Generally, the remote server is completely non-compliant with the http specifications or refused to accept TCP/IP connections from your current IP address.
Action: Inspect this link manually.
Error: FTP Error (1000)Explanation: LinkScan failed to receive a satisfactory response from this FTP server. The error description reflects the actual message returned by the FTP server.
Action: Inspect this link manually.
Error: Bad Syntax (2000)Explanation: This mailto tag appears to contain an e-mail address with an invalid syntax.
Action: Inspect this link manually.
Error: SMTP No Such User (2001)Explanation: This mailto tag appears to refer to an invalid address. The SMTP server associated with this address reported that it did not recognize the username.
Action: Inspect this link manually.
Warning: SMTP Mailbox Full (2002)Explanation: This mailto tag appears to point at a valid e-mail address. The SMTP server associated with that address reported the mailbox was full.
Action: Inspect this link manually.
Possible Error: SMTP Failure (2003)Explanation: This mailto address is suspect. LinkScan was unable to obtain a satisfactory response from the SMTP server associated with that address.
Action: Inspect this link manually.
Error: Errordoc Match (3000)Explanation: This link resulting in a redirection to a URL matching the user-specified Errordoc pattern (probably a custom error page).
Action: Inspect this link manually.
Error: Errorbody Match (3001)Explanation: This document contained a string matching the user-specified Errorbody pattern. The document probably contains a human-readable error message even though the document was served with a 200 OK HTTP status code.
Action: Inspect this link manually.
Error: Profiler Match (3002)Explanation: This document contained a string matching the user-specified Profiler pattern.
Action: Inspect this link manually.
LinkScan for Unix. Reference Manual. Section 7. LinkScan Status and Error Codes
LinkScan Version 11.6
© Copyright 1997-2006
Electronic Software Publishing Corporation (Elsop)
LinkScan™ and Elsop™ are Trademarks of Electronic Software Publishing Corporation
| Previous Contents Next | Help Reference HowTo Card |