Typically, https is proxied with the CONNECT method, and as such Apache typically blocks requests for proxying that have https URLs. I believe you might be able to force it with mod_rewrite, with "RewriteEngine on" and "RewriteRule (.*) $1 [P]" or something like that, but I'm not a mod_rewrite god so don't quote me.
What I do know is that you might^Wwill run into some issues with privacy and expected-to-be-encrypted communications, unless you're building this only for your own use. In the US, there's the Electronic Communications Privacy Act of 1986, and virtually every other country I know of has something much like it. In some areas, these rules don't apply if you explain as part of new-hire orientation that they have no expectation of privacy, and that everything can and will be monitored, even if they're trying to browse to their bank to figure out if they can afford a given business trip. It's possible that in some jurisdictions, these rights can't be waived. (Though the use of a company computer suggests that the user does so only with company permission, which is contingent on accepting the fact that you monitor everything... that's murky territory, and outside of my scope.) If you're trying to build this for your own benefit... I like your style. There's no inherent reason why everything a proxy caches has to be unencrypted, and there's no inherent reason why you shouldn't keep a copy of everything you've downloaded. or anything you've downloaded. -Kyle H On 7/23/10 4:29 AM, rajmohan sk wrote: > Sub : I want to build a man in the middle proxy server application. > > I have experimented so many methods to achieve this. But my > application is failing when I tried > to browse from the browser (IE 8 and Firefox 3.7). > > I have configured my browser proxy settings to '4433' port. My > application is listening on this port, > when I connect to this port from my browser, with the URL > https://localhost:4433 is it working, only a certificate warning is > there. > When I try to connect to another secured site, the SSL_accept function > is returning -1 and my error code is > as follows. > > "2572:error:1407609B:SSL routines:SSL23_GET_CLIENT_HELLO:https proxy > request:.ssls23_srvr.c:391:" > > I am not able to trace out the problem for many days and stucked at > this point. Anybody please help he to > trace out this issue > <http://sigads.rediff.com/RealMedia/ads/click_nx.ads/www.rediffmail.com/signatureline....@middle?>
smime.p7s
Description: S/MIME Cryptographic Signature
