Jehonathan Thomas

Currently for each client connection we create a new connection to server, and then it is used until client or server terminates the connection. I think reusing existing connections/preemptively creating...

@chancity That sounds like a serious problem. Do you see any specific exceptions? Does memory usage looks okay when this occur?

Also does this occur with less number of connections?

I will have to re look the code first for issues with TCP connection close, error handling and GC. After that may be it would be easy to debug.

@aricih In case you found any issues specific to memory leaks or connection not closed properly, appreciate your input.

@chancity Would appreciate if you can give a try now on latest release. There was a major bug in connection reuse we just fixed.

I noticed that .Net core version of the project is much faster for Ssl negotiation, and further researching I think the PCL version of BouncyCastle made the difference. So I...

If server is using self-signed certificate, it is going to throw error during SSL verification on proxy. To accept self-signed certificate you need to ignore verification error in the proxy....

The call stack tells that the chunked response from the server was not in correct format. It tried to parse the next chunk length from the header (to an integer)...

@grandsilence This project is[ no longer maintained](https://github.com/justcoding121/Titanium-Web-Proxy/commit/f863fdc4019ba35a66c30bcd684dcda4bedd220b), as I don't have time to contribute and other contributors are not active. Sorry, but you may check out Fiddlercore. (That's the only...