Handle links with arbitrary path.

Previously we assumed that ATP-rewritten links would have the querystring immediately after the domain.
This commit updates the regex to match links even if they have a path component.

Fixes #4.

chrome/content/unsafelinks.js

@@ -45,7 +45,7 @@ var unsafelinks = {
     },
 
     // Regular expression matching a safelinks-encoded URL.
-    urlRegex: /https?:\/\/(?:.+?\.)?safelinks\.protection\.outlook\.com\/([A-Za-z0-9\-\._~:\/\?#\[\]@!$&'\(\)\*\+,;\=%]*)/gi,
+    urlRegex: /https?:\/\/(?:.+?\.)?safelinks\.protection\.outlook\.com\/(?:[^\?]+)?([A-Za-z0-9\-\._~:\/\?#\[\]@!$&'\(\)\*\+,;\=%]*)/gi,
 
     replacer: function(url, queryString){
         // Extract the "url" parameter from the URL, if it exists.

manifest.json

@@ -2,7 +2,7 @@
     "manifest_version": 2,
     "name": "Un-Safelinks",
     "description": "Replace URLs which have been rewritten by Office 365 Advanced Threat Protection with the original URL.",
-    "version": "1.3.3",
+    "version": "1.4",
     "author": "Anton Sarukhanov",
     "homepage_url": "https://github.com/antsar/unsafelinks",
     "applications": {