# Map Remote URL

Developers often need to test partial changes to a site from testing (staging) environments to production and vice versa. Deploying small changes can be a burden, especially if you have a complex infrastructure and the build time takes longer.

With a proxy tool in the middle, you can map local and remote resources, which enables you to quickly and efficiently test (mock) changes on the fly.

With Fiddler Everywhere, you can easily create a rule that redirects or maps traffic to and from remote hosts while enabling you to mock HTTP responses so that they are transparently served to client applications.

## Creating a "Map Remote (URLs)" Rule

Create a "Map Remote (URLs)" rule by setting the following actions through the [Rules Builder](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/modify-and-filter-traffic/modify-traffic-with-rules).

1. Create a matching condition that uses the "When **all these conditions** are met **any number of times**" pattern.
2. Match by a **URL** that uses a string value to match the desired URL. For example: `example.com`, `localhost`, or a more specific path.
3. Create an **Update URL** action and set the desired new target URL. For example: `google.com`,`localhost`, or another more specific path.

This sample Fiddler rule matches all sessions where the host is `example.com` and redirects (maps) to `google.com`.

![Creating "Map Remote (URLs)" rule](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/assets/dabda39414b3d7089ddc3091cd969c90/adv-map-remote-urls.png)

Once the rule is created, enable the **Rules** tab, toggle the rule switch, and start capturing traffic.

![Activating the "Map Remote (URLs)" rule](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/assets/6b6a3607b073916c2ce77b0f41056eb4/adv-map-remote-urls-active.png)

Download a ready-to-use <a href="https://github.com/telerik/fiddler-everywhere/tree/master/rules/map-remote-urls" target="_blank">"Map Remote (URLs)"</a> rule as a FARX file, which you can import through the Rules toolbar.

## See Also

* [Learn more about the Rules functionality in Fiddler Everywhere here...](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/modify-and-filter-traffic/modify-traffic-with-rules)
* [Learn more about all rules presets in Fiddler Everywhere here...](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/rules-presets)
* [Learn more on how to organize your rules here...](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/modify-and-filter-traffic/organizing-rules)
* [Learn more about the matching conditions here...](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/modify-and-filter-traffic/conditions-and-actions#conditions)
* [Learn more about the supported actions here...](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/modify-and-filter-traffic/conditions-and-actions#actions)
* [Learn more about final and non-final rules here...](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/modify-and-filter-traffic/conditions-and-actions#final-and-non-final-actions)
* [Learn more about using breakpoints here...](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/modify-and-filter-traffic/breakpoints)