VSCode extension that checks for broken links in an HTML, XML, or RSS file.
Checks for broken links in anchor-href, link-href, img-src, and script-src tags in currently-open HTML file. It checks HTTP/HTTPS links by trying to access them on the internet, and checks relative links (../folder/file.html) by checking if the file exists on the local file system.
Checks both clearnet and onion (Tor) links.
Also checks for badly-formatted mailto links, and duplicate local anchors (anchor-name, anchor-id).
Also checks for working HTTPS equivalents of HTTP links.
Also checks for broken links in currently-open XML or RSS file.
Open an editor window on an HTML, XML, or RSS file, and then press
Broken links are reported via the standard error/warning/information diagnostic icons in lower-left of UI.
Click on the diagnostic icons and numbers to open the diagnostics pane.
Click on a diagnostic line, see that link highlighted in the source file, press
Alt+T to open that URL in your browser.
If it's an HTTP link, press
Alt+M to try to open the HTTPS equivalent of that URL in your browser.
Alt+L to clear all diagnostic messages generated by this extension.
Tip: After you do
Alt+H and get diagnostics, work on the problems from bottom (last diagnostic) to top (first diagnostic). That way the line numbers in the diagnostics don't change as you delete or add lines in the source.
To see/change settings for this extension, open Settings (
Ctrl+,) / Extensions / "HTML / XML / RSS link checker".
To change the key-combinations for this extension, open File / Preferences / Keyboard Shortcuts and search for Alt+H or Alt+T or Alt+M or Alt+L.
Onion (Tor) links
Onion URLs look like
https://1234567890123456.onion/something (16 chars before '.onion') or
https://12345678901234567890123456789012345678901234567890123456.onion/something (56 chars before '.onion'). They are used to access dark-web sites through Tor Browser (usually).
Checking validity of Onion (Tor) links
Alt+H to check onion links, you must have a Tor/socks proxy listening on 127.0.0.1:9050. On Linux:
sudo systemctl status tor # should show an active Tor service
# if it's not active, try:
sudo systemctl start tor
sudo ss -lptu | grep :9050 # should show an active Tor listener
For more information see https://github.com/talmobi/tor-request#requirements If you don't have a Tor/socks proxy listening, each onion link will give an error "Can't check onion URLs: no Tor/socks service listening on 127.0.0.1:9050".
While checking links, the Tor Browser can be running or not, it doesn't matter. Only the proxy is used.
Opening Onion (Tor) links in Tor Browser
[THIS FEATURE SEEMS TO BE BROKEN]
Alt+M to open onion links in the Tor Browser, you must have Tor Browser installed and running already. You have to launch it yourself; this extension won't launch it.
Also, on Linux, you must install "xdotool":
sudo apt install xdotool
Then for any bad onion link reported in the diagnostics, do
Alt+T on it. If it's an "http://" onion link (illegal, I think), also you can do
Alt+M on it. You should see focus switch to the Tor Browser, and the URL will be typed in the address bar, then accessed.
The connection to Tor Browser is not 100% reliable. The extension is using xdotools to send key-presses to the Tor Browser, and it's fairly timing-dependent and one-way. If your system is busy, or Tor Browser is busy, or something else goes wrong, you may see the wrong things happen in Tor Browser (chars missing from the URL, or some dialogs popping open).
addExtensionToLocalURLsWithNone: If a local file URL has no extension, add this extension to the filename before checking (default is ""; don't include "." in the setting).
checkInternalLinks: Check #name links to targets inside current file (default is true).
checkMailtoDestFormat: Check format of email addresses in mailto links (default is true).
dontCheckURLsThatStartWith: Don't check URLs that start with any sequence in this comma-separated list (default is "127.,192.,localhost,[::1],[FC00:,[FD00:").
localRoot: String prepended to links that start with "/" (default is ".").
maxParallelThreads: Maximum number of links to check in parallel (range is 1 to 20; default is 20).
processIdAttributeInAnyTag: #name link can be to any tag with ID attribute inside current file (default is true).
reportHTTPSAvailable: Report if HTTP links have HTTPS equivalents that work ? (default is [check and report] "as Information")
reportNonHandledSchemes: Report links with URI schemes not checked by the checker, such as FTP and Telnet (default is "as Information").
reportRedirect: Report links that get redirected (default is "as Warning").
timeout: Timeout (seconds) for accessing a link (range is 5 to 30; default is 15).
torOpenURLCmd1: command (1) to open an URL in Tor Browser ('URL' will be appended; default is "xdotool search --onlyvisible --name 'Tor Browser' windowactivate --sync key --clearmodifiers --window 0 ctrl+t type --delay 100 "
torOpenURLCmd2: command (2) to open an URL in Tor Browser (default is "xdotool search --onlyvisible --name 'Tor Browser' windowactivate --sync key --clearmodifiers --window 0 Return").
userAgent: User-Agent value used in Get requests (default is "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0").
HTML: Tag name and href/src/id attribute must be on the same line.
XML and RSS: Entire tag (for link, guid, and url tags) must be on the same line.
Doesn't know about comments; will find and check tags inside comments.
Checks "#name" links to targets in current file, but not in other local or remote files.
Doesn't check EVERY detail of the email address spec in mailto links. Just a cursory check.
XML: There are no standard tag and attribute names, so some links may not be checked.
Note that checking for broken links is more of an art than a science. Some sites don't actually return 404, but send you to a landing page. For example, Azure.com works this way. You can go to https://Azure.com/foo/bar and it will happily redirect you to a sub-page of https://azure.microsoft.com/, with no 404 status returned. So take a status of "OK" with a grain of salt - you may not be arriving at the page you intend.
Also, browsers seem to be more tolerant than the library used by this extension. This extension will report a lot of certificate-errors and such that browsers mostly ignore.
And checking is getting harder, with more URLs redirecting through GDPR-consent or cookie pages and such, or redirecting to same URL with a tracking parameter added, causing false positives.
If there are multiple identical tags with identical link-targets on same line (for example two Anchor tags with identical href targets), clicking on diagnostic for any of them takes you to first one in the source line.
Doesn't check ANY of the email address format after "?", as in "mailto:email@example.com?subject=xyz".
"://" is prepended to items in dontCheckURLsThatStartWith before matching; e.g. if you specify "localhost" the code searches for "://localhost" in URLs.
The checking in XML and RSS files is permissive, allowing known stuff from RSS, and likely stuff that could be in XML. Any attribute of the form *url="something" or *href="something" will be checked, as well as the standard RSS tags: link, guid, url.
Onion: an URL is considered "onion" if it starts with "https://" and contains ".onion" ANYWHERE in it.
Onion: if an URL starts with "http://", it will be treated as non-Onion, and the "https://" form of it will be checked as non-Onion too.
From the Marketplace
Open Visual Studio Code and press
F1; a field will appear at the top of the window. Type
ext install linkcheckerhtml, hit enter, and reload the window to enable.
From VSIX file
code --install-extension linkcheckerhtml-n.n.n.vsix
- In VSCode GUI, in the Extensions view "..." drop-down, select the "Install from VSIX" command.
From source code
- Do a
git clone to copy the source code to "linkcheckerhtml" in your home directory.
- In CLI,
cd linkcheckerhtml and then
- Copied from "Microsoft / linkcheckermd" and then greatly modified.
- Extension works, but probably has memory leaks, not much testing.
- Finally nailed that hang bug.
- Added setting for timeout.
- Fixed timeout and redirect settings.
Alt+T to open an URL in a browser.
- First release with a VSIX file.
- Got rid of: "href" or "src" has to be first attribute in the tag.
- Require at least one "." in mailto address's domain.
- Try to dispose memory properly to avoid leaks.
- Handle local files with "?args" on the end.
- Added localRoot setting.
- Fixed mailto that ends with "?".
- Added userAgent setting, and it definitely makes some sites happier.
- Increased default timeout to 12.
- Check local anchors (#name) in current file.
- Support anchor-id (HTML5) as well as anchor-name.
- Added settings about checking local anchors (#name) and ID attributes in current file.
- Moved repeated add-diagnostic code into a function.
- Added setting and code to check if HTTPS equivalent exists for HTTP address.
Alt+M to open current HTTP URL as an HTTPS URL in browser.
- Briefly tested IPv6 addresses to see that at least they don't cause anything to blow up.
- Set default user-agent string to latest Firefox.
- Added dontCheckURLsThatStartWith setting and code.
- Increased default timeout to 15.
- Added "Using the extension" image.
- Better message when 0 files left to do.
- Added addExtensionToLocalURLsWithNone setting and code.
Alt+L to clear all diagnostics belonging to this extension.
- Changed my email address.
- Added support for XML and RSS files.
- Changed to Axios 0.19.0.
- On redirected link, give new URL.
- Updated package dependencies because of security warnings.
- Don't report link that redirects to same link (but rare, usually something is different).
- Don't report link that redirects to same link with a tracking parameter added (but rare, usually something else is different too).
- Fix status when file contains zero links.
- Added support for checking onion links. Simple pass or fail, consider redirect as pass, no way to control timeout or user-agent.
- Onto new versions of VSCode and npm and node.
- Updated default user-agent string to Firefox 76.
Alt+M on onion link open it in Tor Browser, using xdotool.
- Flag onion links where domain name is illegal length.
- Moved xdotool command line strings into settings. (Wayland will use ydotool ?)
- Treat onion links that start with "http:" as clearnet links.
- Somehow using xdotool to send onion links to Tor Browser has stopped working.
- Somehow using xdotool to open onion link in Tor Browser has gotten broken.
- Test onion links a lot more, maybe indicate redirects, any way to control timeout, set user-agent.
- Better way to open onion link in Tor Browser ?
- Way to open onion link in Tor Browser on Windows ?
- Add setting "do/don't check onion links".
- Snap version of VSCode uses
Alt+H for Help menu.
- Create automated tests.
- A lot of code cleanup needed, move stuff into functions.
- Extension really is supposed to remove each diagnostic line after the corresponding source line is edited.
- Bundle extension to make it smaller/faster ? https://code.visualstudio.com/api/working-with-extensions/bundling-extension
- Can't really test IPv6 because my system and ISP have it turned off.
- Allow single-quotes on attributes ? I thought HTMLHint didn't allow them, so I didn't support them.
- Don't check a link if it has rel="nofollow" ? Probably should leave it as-is: check it.
- Any way to do retries inside axios ? Apparently not.
- Memory leaks ? Doesn't seem to be any tool to check an extension for leaking. Maybe not possible, since extensions are running inside a huge framework of Electron or Node or something.
- Display a "busy" cursor ? Can't. Window.withProgress could put up a dialog, but then user would have to close the dialog manually every time, don't want that. Doesn't seem to be a way to close that dialog programmatically.
- Click on diagnostic, do
Alt+M to browser, come back to VSCode, cursor is in filter field of diagnostics pane instead of in source file. More convenient if in source file. But seems to be no way to do it.
- Multi-line tag (tag name and href/src attribute on different lines) silently ignored. Would be a lot of work to deal with, given the simple way the code does parsing.
I'm no expert on this stuff, maybe I'm doing some things stupidly.
- Linux Mint 19.0-19.3 Cinnamon, now Ubuntu GNOME 20.04
- VSCode was 1.29.1 (which said Node.js 8.9.3), then 1.39.0-exploration (which says Node.js: 12.4.0), now 1.46.0-insider (which says Node.js: 12.13.0)
- 5/2020 the snap versions of VSCode, node, and npm on Ubuntu 20.04 have problems; don't use them.
node --version was 8.10.0 then 10.15.3 now 10.19.0
npm --version was 3.5.2 then 6.9.0 now 6.14.4
- Ran Yeoman to make a Typescript test extension, then copied the entire node_module directory tree from there to linkcheckerhtml directory.
- Put path to node_module directory tree in vscode-typings.d.ts
sudo npm -g install --save axios then copy /usr/local/lib/node_modules/axios to project node_modules
This extension doesn't collect, store or transmit your identity or personal information in any way. All it does is read the current editor window, do existence-tests on local files, open links to internet sites, and send internet links to your browser.