Hello
Thank you for making this awesome piece of software. I have used it many times before, and this is the first time where I actually can't get Fiddler to record any HTTPS traffic from league of legends.
What i want: Record all HTTPS requests that are getting sent by League of legends to their servers, using the League of Legends client. (The client is the only place where you can actually see the information that i need).
What does not work: I am quite sure that League of Legends does NOT use windows default proxy, and therefore does not get picked up by Fiddler. I am not quite sure if they use SSL-Pinning, I dont think they do - but i might be wrong. Each time I try to boot up League of legends I just see the HTTP tunnel without any HTTPS requests in between.
What i have tried:
- Tried forcing League of legends to use the proxy 127.0.0.1:8888 for it to go through fiddler. This is where I see only HTTP tunnels with instant connection closed. It also gave me the warning "Do you want to trust this certificate bla bla bla."
- Tried using ProxyCap and Your freedom to make rules to route all the data through fiddler using 127.0.0.1:8888.
- Tried to add an environment variable to my system settings called "all_proxy" with the value of 127.0.0.1:8888 to again make it go through fiddler.
I have attached two images, one showing my HTTP tunnels and one showing that I can receive HTTPS requests from other apps such as ShareX in this example.
Still no luck... What should I do in order to actually see the HTTPS Requests between the HTTP Tunnels? Thanks.
1 Answer, 1 is accepted
Sorry for the late response. The fact that you see the HTTP CONNECT requests means that you are successfully making the League of Legends to use Fiddler as a proxy. However, it seems that Fiddler fails to decrypt its traffic.
It also gave me the warning "Do you want to trust this certificate bla bla bla."
I suppose that League of Legends asks you if it could trust the Fiddler certificate. If this is the case, it seems that it does not trust the certificates which are installed in the Windows Certificate Store, so you have to agree on that warning if there is such an option.
If this doesn't solve your case, you could try to use the Fiddler CertMaker. If there are any problems with it you could type the 'prefs set fiddler.certmaker.bc.debug' command in the QuickExec box of Fiddler. This will make Fiddler to log any HTTPS errors with this extension.
Regards,
Simeon
Progress Telerik