Charles handles this by using the server’s SSL certificate for the connection from Charles to the remote server, and then using Charles’ own SSL certificate for the “last mile” back to your browser or device. This means that the connection will be flagged as insecure; Charles’ certificates aren’t trusted by your browser or device – but we can easily change that. Continue reading
I use Charles Proxy extensively for debugging all kinds of applications, and lately I’ve been using it more with mobile devices. One of the killer features of Charles is its ability to intercept SSL traffic. This is hard – and rightly so, it should be difficult to inspect SSL traffic!