Skip to main content

Chrome Custom URL Redirector Extension

Working as a IT professional sometimes you need to access remote systems using vpn connection. Throughout the vpn connection dns records and hosts records may be overwritten and control panel url addresses are inaccessible. To overcome this you need to use custom browser extension like greasemonkey, tempermonkey etc.

But i don't want to use these third party extensions so i wrote a simple chrome plugin which translates url addresses to ip addresses.

You need two files, manifest.json and background.js

Examples of these files are(add urls and ip addresses to urlDict variable as required!):

manifest.json:
{
  "name": "Custom URL Redirector",
  "version": "0.1",
  "description": "Checks URL and redirects as required.",
  "manifest_version": 2,
  "background": {
    "scripts": ["background.js"]
  },
  "permissions":["http://*/*","https://*/*","webRequest","webRequestBlocking","tabs"]
}

background.js:
chrome.webRequest.onBeforeRequest.addListener(
  function(details) {
    var urlDict = {
      "abc.com" : "1.1.1.1",
      "def.net" : "2.2.2.2",
      "ghi.org" : "3.3.3.3"
    };
    for(var key in urlDict) {
      if (details.url.indexOf(key) !== -1) {
        var re = new RegExp(key, "g");
        redirURL = details.url.replace(re, urlDict[key])
        return {redirectUrl: redirURL};
      }
    }
  },
  {urls: ["<all_urls>"]},
  ["blocking"]);

Save these two files in the same folder. And import them from chrome's extension page. Turn on developer mode , click load unpacked extension and select the folder containing these two files.

Now you can use the extension. Then all requests made to abc.com would be redirected to 1.1.1.1

Comments

Popular posts from this blog

Sending Jboss Server Logs to Logstash Using Filebeat with Multiline Support

In addition to sending system logs to logstash, it is possible to add a prospector section to the filebeat.yml for jboss server logs. Sometimes jboss server.log has single events made up from several lines of messages. In such cases Filebeat should be configured for a multiline prospector. Filebeat takes lines do not start with a date pattern (look at pattern in the multiline section "^[[:digit:]]{4}-[[:digit:]]{2}-[[:digit:]]{2}" and negate section is set to true ) and combines them with the previous line that starts with a date pattern. server.log file excerpt where DatePattern: yyyy-MM-dd-HH and ConversionPattern: %d %-5p [%c] %m%n Logstash filter:

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three