thanks - I've been looking into it more, but I'm really stumped re the HTTPS aspect. I've just looked into the "ProxyHandler.cs" source file. Questions I have:
a) I can't see how with HttpListener to get it working for both HTTP and HTTPS listening at the same port? I get an error. I have posted
b) My assumption re my question a) above is that, as I'm creating a windows console application standalone (not running on IIS) that I'm need to use HttpListener to capture the HTTP(S) requests before passing them into the ProxyHandler.cs methods - is this
c) I'm assuming as I would be configuring my local browser and applications to use a proxy server of "localhost:8080" that this would be correct for both HTTP and HTTPS - is this correct? That is the SSL/HTTPS traffic from the browser would
be going out to port 8080 too?
d) Assuming then the HttpListener can pick up the HTTPS request, I'm not sure whether there is any special requirement to setup a certificate and assign it somehow to the HttpListener? That is could HttpListener + HttpWebRequest (within "ProxyHandler.cs")
be enough to proxy HTTPS, or does there need to be some certificates setup. I've googled and seen some posts re HttpListener & SSL where people talk about setting the certificates up.
e) Are there any specific WebRequest http headers required to allow the proxying of HTTPS traffic from one local HttpWebResponse into a new external HttpWebRequest? e.g. any flags/headers that specifically arrange that the https receiving code doesn't
need to terminate the connection but just pass on, on the originators behalf?