Resource Override

Learn how to migrate your configurations from Resource Override Chrome Extension to Requestly

We don’t have any quick import feature for Resource Override Configurations. We have an open GitHub issue for the same, please comment if you want us to take it on priority. Here are the manual steps you can use to make the same configurations as in Resource Override Chrome Extension.

URL → URL

Every request URL is compared with the Match URL and is redirected to the Replace URL if the match is successful.

Exact Match

If your Resource Override configuration is with exact match without using any * in it.

This becomes a very straightforward setup in Requestly. Use the Redirect Rule with the "Equals" operator.

Wildcard Match

If your Resource Override configuration is a wildcard match with 1 * in it.

In Requestly, Use the "Wildcard" operator and the substituted value should be replaced with $1,$2, etc.

e.g. In Requestly, You will use HTTP Redirect Rule like

Multiple Wildcard Operators

If your Resource Override configuration is a wildcard match with multiple *’s in it.

In Requestly, This becomes HTTP Redirect Rule with Wildcard Operator. Each star gets a number from left to right. You can use $<number> like $1, $2 where you want to use the matched values of *’s.

URL → File

When you want to load a file in place of the Matched URL.

In Requestly, you can use the Redirect Request Rule with Redirects to option as Pick from Files/Mock Server and then select the file/create a file that you want to load.

Inject File

In Resource Override, you can select a file(JS/CSS) and inject that into a webpage.

In Requestly, you can use Inject Script Rule as below.

Change Headers

In Resource Override, you can use Change Headers to update the Request or Response Headers.

In Requestly, you can use the Modify Headers Rule and similarly configure the rule as below.

Updated on