In this five-part article series, you will learn how to manipulate your API behavior with a local proxy server.
After setting the scene with an introduction, we will now learn how to set up the Charles Proxy and its configuration
- Charles Proxy Setup & Configuration
- Charles Proxy in Action
- Fiddler Setup & Configuration (coming soon)
- Fiddler in Action (coming soon)
To get started, please follow the official instructions to install Charles on your preferred platform.
On Windows, Charles is automatically configuring your system and browser settings to route all traffic through it when you start the program.
The same applies to macOS when you confirm the permission dialog.
On Linux, things are slightly different. You have two options:
- Setting your
https_proxy environment variables to
Many applications use the environment variables and, in general, will affect most of your network traffic.
- Installing a browser add-on for easy toggling between proxy on/off just for browser traffic, e.g., Proxy SwitchyOmega add-on for Chrome.
If you are going to work with HTTPS, you also need to set up SSL decryption.
Without it, all traffic would be encrypted directly between API and frontend - which is good!
With SSL decryption enabled, Charles will establish two secure connections.
One to the API and one to the frontend.
This way, Charles can read messages from both sides.
It is a classic man-in-the-middle.
Follow these steps to activate SSL decryption.
*.mockapi.io with your API, e.g.,
When you have already pointed your browser to Charles and are browsing to an SSL-decrypted page, you will notice a security warning about an invalid certificate authority.
Your browser is mistrusting Charles' certificate, which is a good thing (otherwise, SSL would be entirely worthless).
To fix this, you need to either trust each site's certificate permanently or trust the Charles root certificate.
Read more about the platform specifications here.
Recording Your Traffic
Assuming you have everything up and running, you can now start your first traffic recording session.
Click on the "Start Recording" button and wait a couple of seconds.
You will probably see a massive list of connections. Yes, browsers are very chatty, especially with many tabs opened.
With default settings, we see every single connection from our browser.
We can fix this quickly: In the menu, click "Proxy" → "Recording Settings" → "Include" and then add your API's hostname.
For this demonstration, we're using the services of mockapi.io to create a simple REST API.
You may have to restart Charles at this point, to apply the new settings without having some weird glitches.
It's essential to take care of caching.
In case your API sends caching headers, Charles will serve cached contents automatically, and you will not be able to inspect a response's body.
In the menu bar, click "Tools" → "No Caching".
Our first record will now look like this:
On the right side, the upper box shows the request, the bottom one the response.
In this short article, we have taken a look at how to install and set up Charles Proxy to record traffic and decrypt SSL traffic for testing and debugging purposes.
Charles makes this process flawless, and we will use this as a base for the upcoming articles.
In the third article of this series, you will see Charles Proxy in action.
Verpassen Sie keine Artikel mehr zu Tools & co
Melden Sie sich bei unserem kostenlosen monatlichen Newsletter an, um die aktuellen technischen Artikel unserer Experten zu den Themen Angular, .NET, Blazor, Azure und Kubernetes zu erhalten.