Jehonathan Thomas

To clarify some of the things you mentioned. This new handlers will NOT be called if the body was already read through `GetRequestBodyAsString()` or `GetRequestBody()` from within existing before request...

Sorry for deleting my responses multiple times. 😅 I think I was thinking out loud while typing. One more thing that we need to do apart from this new handler...

May be you can check the request headers send to Squid from Titanium and without Titanium to check if there is any headers that would indicate the original IP.

So if it's a request header added by selenium chrome, you can remove that header inside request handler on Titanium proxy.

I am little unclear on what you meant by "they see Selenium Chrome with` --proxy-server=127.0.0.1:8000`" How do they see that? I assumed that information was added as a header to...

Instead of telling selenium chrome to use Titanium proxy, may be you can set Titanium as system proxy. So all requests from chrome will go through the proxy automatically.

We cannot get rid of bouncy castle because, we also have to support non-windows machines. There is already an option to not use BouncyCastle for Windows. https://github.com/justcoding121/Titanium-Web-Proxy/blob/develop/src/Titanium.Web.Proxy/Certificates/CertificateManager.cs#L19 https://github.com/justcoding121/Titanium-Web-Proxy/blob/develop/src/Titanium.Web.Proxy/Certificates/WinCertificateMaker.cs It had...

We cannot do that. SSL encryption is done at TCP level for the whole HTTP request, including url, headers and body. So, when decryptSsl is false, we cannot even parse...

A host can have multiple IP addresses. You may be able to find the host using a reverse lookup. You may be able to see the hostname even when SSL...

You can also deny SSL connection when using explicit end point, using DenyConnect property during TunnelConnect. Something like below. Remember this is only possible when using ExplicitEndPoint, which I assume...