Skip to content

Status Watch: An add-on for noticing HTTP error codes

Often on complex pages with many assets it can be easy to overlook assets which don’t load. Usually they are minor JS, CSS, or tracking pixels which aren’t noticed until you’ve spent way too long trying to track down the problem (or a month later you log into your stats dashboard to discover you haven’t been collecting stats).

With the launch of the new Add-on Builder (still an alpha product, but usable) I decided to make my first Jetpack to fix this.

In only about 20 lines of code I was able to look for any 4xx or 5xx errors in the HTTP traffic and show a brief notification to the user about what went wrong and where. The builder was a great development experience (lack of documentation aside) and was a breeze to do something relatively complex.

If you’ve wanted a similar add-on, feel free to use Status Watch. It’s a Jetpack so you’ll need Firefox 4, but on the bright side, you won’t even need to restart the browser. Just click and go.

I’ve had some requests to support a whitelist of sites so you don’t get notifications all over the web and I’ll add that when I get time. It’s surprising how many sites have 403s and 404s though.

Update 2011-02-17: Version 2 is on AMO now which supports a whitelist. See the AMO page for details.

{ 3 } Comments

  1. dfkdf | February 11, 2011 at 5:48 am | Permalink

    Good idea! Instead of a whitelist of websites that escape Status Watch, though, you may simply want a small whitelist of websites that will be monitored by Status Watch.

  2. Fred | February 11, 2011 at 3:50 pm | Permalink

    Very nice. Good job!

    One thing you might want to filter out is 401 responses (that are thrown by pages that require authentication). Since a) this is most likely intentional and b) the user will be greeted with a popup anyway.

  3. Wil Clouser | February 17, 2011 at 3:43 pm | Permalink

    The new version filters out 401s also.