Possible to also catch send packets? about finalesfunkeln

[Maufeat]

Oh and what about the HTTP Packets, which are send / recveived by the client before the RTMP. (Login Success / Banned / etc.)

[frostycpu]

1. Yes I think I will add that.
2. Redirecting HTTP requests is possible, yes, but it would require a totally different library to work. If you are just interested in inspecting the packets you could try to capture them with Fiddler.

[yokrysty]

you can implement Fiddler's Core like this program https://www.lolskinview.com/

[frostycpu]

The problem with Fiddler's core is, that it intercepts all HTTP(S) requests and not just those from the LolClient. Programs that use certificate pinning (e.g. Dropbox) stop working when a Fiddler proxy is running.

I too am interested in catching HTTP packets, I just have to figure out a way to do it without intercepting unrelated packets.

[yokrysty]

I understand that but I don't think is that such a big problem.
I've searched the web and found some info about this, maybe it can help you, I don't have that much time to experiment. The idea is to register the FiddlerCore as in process proxy (I'm think of injection for the LoL process), instead of system proxy.

From the official book (Debugging with Fiddler by Eric Lawrence):
Getting Traffic to FiddlerCore
Like Fiddler itself, FiddlerCore runs as a local proxy instance, and it only sees traffic that is sent to it. If the RegisterAsSystemProxy flag is set when you call the FiddlerApplication.Startup method, FiddlerCore will automatically register as the system proxy, just like Fiddler does. If you do not configure FiddlerCore as the system proxy, you can manually configure most applications to point at your FiddlerCore instance. FiddlerCore offers the unique ability to register as the WinINET proxy for just the process in which it is running. This is a useful capability for scenarios where you have a Web Browser control in your .NET application and want to use FiddlerCore to only capture or modify the traffic from that Web Browser control (and any other WinINET APIs).
To make use of this capability, call the SetProxyInProcess method with your listening endpoint’s address and port, and a proxy-bypass list: Fiddler.URLMonInterop.SetProxyInProcess("127.0.0.1:7777", "<-loopback>");
When capture is complete, you may reset the current process back to the default system proxy:
Fiddler.URLMonInterop.ResetProxyInProcessToDefault();

sources:
http://stackoverflow.com/questions/28339174/listen-to-a-specific-application-using-c-sharp-and-fiddlercore
https://groups.google.com/forum/#!msg/httpfiddler/NOxnktF8R0s/Iu1SJbf-d1wJ
https://groups.google.com/forum/#!topic/httpfiddler/kkirFaUbeHw
https://groups.google.com/forum/#!topic/httpfiddler/10GtCA3HmHI