Help

313 |

View youtube help video HERE. 314 |

Sometimes browser cache can stop overrides from working! Try reloading while holding shift or empty your cache!

315 |

This extension exists to help you gain full control of any website by redirecting traffic, replacing, editing, or inserting new content. It does this by comparing url "match rules" to the current tab url and then individual resource urls. If the urls match, then the rules are applied.

316 |

Rules are put into "Tab Groups". A Tab Group has a URL text field that acts as the match pattern for Chrome's current tab. Rules inside the Tab Group wont apply unless the match is successful. This is a good way to make sure overrides only happen on a certain website.

317 |

Example Tab URL Matches:

318 | 319 | 320 | 321 | 322 | 323 | 324 | 325 |

Tab Match URL		Browser Tab URL
http://www.example.com/	matches	http://www.example.com/
http://www.example.com/*	matches	http://www.example.com/some/path/info.txt
example	matches	https://www.something.com/example/in/path
://www.example/other/*	matches	https://www.example.org/some/other/path
*	matches	<Any URL Here>

326 |

Rules use the same star syntax. Web rules get an extra ability with stars (more on that below).

327 |

A Rule can come in four different types:

328 |

URL → URL: Every request url is compared with the Match URL and then transformed into the Replace URL if the match is successful.
URL → File: Every request url is compared with the Match URL. If the match succeeds, a file you create is supplied as the response.
Inject File: A file you create will be injected into the page as a JS or CSS document.
Change Headers: Modify request or response headers.

334 |

Each resource can only be changed by the first rule that matches it, so rules higher on the page have more precedence. You can rearrange rules by dragging on the up and down triangles.

335 |

Example URL → URL Patterns:

336 |

Text highlighted in blue is "captured" in *'s.

337 | 338 | 339 | 340 | 341 | 342 | 343 | 344 | 345 |

Match URL	Replace URL	Resource URL		Result URL
http://www.ex.com/neat.js	http://local:8080/cool.js	http://www.ex.com/neat.js	→	http://local:8080/cool.js
http://www.ex.com/js/*	http://local:8080/all.js	http://www.ex.com/js/some.js	→	http://local:8080/all.js
http://www.ex.com/*.js	http://local:8080/*.js	http://www.ex.com/captured_in_star.js	→	http://local:8080/captured_in_star.js
http://.ex.com/	http://.local:8080/	http://other.ex.com/second_capture.js	→	http://other.local:8080/second_capture.js
/js/*.js	http://local:8080/code/**.js	http://any.com/js/2stars.js	→	http://local:8080/code/2stars.js
http://ex.com///**.js	http://local:8080/*//***.js	http://ex.com/a/b/c.js	→	http://local:8080/b/a/c.js

346 |

When using the URL → URL rule, you can "store" parts of the resource URL in stars (*) and then reuse the stored part in the replace url with the same number of stars. Stars can capture parts of the url more than once - each new capture is put into a "queue" (See the 3rd to last example). If you need to be specific where stored parts of the url are placed, you can use multiple stars together (**) to 'create another variable'. You can also use this technique to throw away parts of a url you don't care about (you don't have to use the corresponding stars in the replace url). Examples of these can be seen in the above table.

347 |

Tips and Tricks

348 |

I highly recommend that you use this extension through Chrome's dev tools panel (right click somewhere on a page and click "Inspect". Then go to the "Overrides" tab). The dev tools view can help you make your url match rules correctly with a suggest feature.

349 |

Do you need to override https content with a URL → URL rule and content on your computer? Make sure you have an https server! Also make sure that if ajax calls are being used that your https server has CORS turned on. Finally, don't forget to check that you can browse to your https content and "Proceed Anyway" if chrome yells at you about an untrusted certificate (Or you can just add the certificate to your system's trusted certificates). I like to use this http(s) server (it auto generates ssl certificates and has CORS turned on by default).

350 |

If you are having trouble getting a rule to work, try turning on the logs (click the options button at the top of this page and check "Show Logs"). Then reload the page and look in Chrome's console for the url you are trying to match. If a match succeeds, the text highlight will be blue. If all else fails, try to make your rule less strict: *something* <-- In this case, "something" just has to show up somewhere in the url.

351 |

A URL → File rule needs to be paired with a mime type. This extension tries to guess the correct mime type based off of the resource url and the content you supply. If your files aren't loading and Chrome is giving you trouble about content arriving with the wrong mime type, it means that this extension couldn't automatically detect the correct mime type and you may need to provide it yourself. Here is an example of how to do this: If you have a JavaScript file, you would put /* mime: text/javascript */ on the very first line of the file. You can force any mime type you want as long as it's on the very first line of the file and in that format.

352 |

If you think you've found a bug and want to report it, please create an issue on the github page here: https://github.com/kylepaulsen/ResourceOverride. I am much, much more likely to see bug reports there than on the Web Store (they don't have email alerts). Also feel free to contribute if you'd like. :)

353 |

354 |

355 |

356 |

357 |

Resource Override

Request Headers

Response Headers

Help

Example Tab URL Matches:

Example URL → URL Patterns:

Tips and Tricks