How to enable Map Local over https with Charles Proxy?

Step 1: Installing and Configuring Charles Proxy

First, ensure Charles Proxy is successfully installed on your machine. After installation, perform basic configurations to enable it to capture HTTPS traffic. This includes:

1. Enable HTTP Proxy: In Charles' main interface, select Proxy > Proxy Settings, ensure the HTTP proxy is enabled, and set an appropriate port (typically 8888 by default).
2. Install SSL Certificate: To allow Charles to decrypt HTTPS traffic, install Charles' SSL certificate on your device. Access the installation option via Help > SSL Proxying > Install Charles Root Certificate, then install and trust the certificate in the system or browser based on your operating system.

Step 2: Enabling SSL Proxying

To enable Charles to inspect HTTPS traffic, activate SSL Proxying:

1. In Charles, select Proxy > SSL Proxying Settings.
2. In the pop-up window, click Add to specify domains or IP addresses for decryption. For example, add * to represent all websites or specific domains like *.example.com.

Step 3: Configuring Map Local

Once SSL Proxying is configured, set up Map Local rules to map specific network requests to local files:

1. In Charles' main interface, locate the request you want to map, right-click it, and select Map Local.
2. In the pop-up window, set the local path. Choose an existing file or folder; if it's a folder, Charles will attempt to match the request filename.

Example

Suppose you are developing a website at example.com and want to replace a JavaScript file for local debugging. Follow these steps:

• Capture the corresponding JavaScript file request, e.g., https://example.com/script.js.
• Right-click the request and select Map Local.
• In the Map Local settings, select or enter the local file path, e.g., /Users/username/Desktop/local_script.js.

Conclusion

By following these steps, you can easily implement Map Local via HTTPS with Charles Proxy. This is highly valuable in frontend development and debugging, especially for quickly testing the impact of local code changes on the live environment.