Broken Links

This document contains broken links in order to demonstrate WebLight's link testing capabilities. The link problems below are shown in the issue report generated by WebLight.

404 Not Found

The web is littered with broken links like the example below. They are often caused when sites are reorganized without taking the steps needed to keep links working (see redirects).

Example: link to hrefNotFound which doesn't exist.

Server, Network and DNS Problems

Server and network problems can also prevent links working properly. These errors may be temporary such as when a server goes down, or permanent when the business goes down and the domain no longer exists.

Example: link to document on host nosuch.hsto that doesn't exist.

Redirects

The HTTP protocol allows documents to be moved without causing significant problems, in fact they quite difficult to notice with a browser.

Temporary redirect 307 and 302 Found indicate that a document can temporarily be found at a different location. Developers can use them to centralize references to URIs which are expected to change.
Example: tredirect.cgi should redirect your browser to tredirect.html.

Moved Permanently 301 indicates that the resource has moved permanently. By using permanent redirects sites can be reorganized without disrupting users with 404 Not Found problems.

Links to resources that have been moved permanently should be changed when they are identified because they waste bandwidth, and increase latency.
Example: predirect.cgi should redirect your browser to predirect.html.

Link Types

The examples above are the most common but WebLight checks many other types of links that can also break. In the example below the src in the img below points to an image that doesn't exist.

Example: [<img src="srcNotFound" alt="missing image" />] looks like []