|
ProxHTTPSProxyMII: Development
|
|
May. 30, 2014, 07:58 PM
(This post was last modified: May. 31, 2014 12:31 AM by JJoe.)
Post: #6
|
|||
|
|||
|
RE: ProxHTTPSProxy, a Proxomitron SSL Helper Program
Ok. Installed and running.
![]() ![]() Fresh install of "Python3.4.1" didn't work for me. All is well after an uninstall and reinstall of "3.4.1", tho. "Win32 OpenSSL v1.0.1g Light" required "Visual C++ 2008 Redistributables". Don't forget to bypass the Proxomitron before using "pip install pyopenssl" at the Window's command prompt. Assuming Python34 is installed in the default folder Code: c:\Python34\Scripts>pip install pyopensslTo enable $SETPROXY(127.0.0.1:8081), add the Rear proxy to the Proxomitron via "Proxy" on the Proxomitron's main dialog Code: 127.0.0.1:8081 ProxHTTPSProxyRear(More detailed instructions later or per request) For now, I'm using these Exceptions-U entries Code: $OHDR(Tagged:Proxomitron FrontProxy/*) $SET(keyword=$GET(keyword)i_proxy:3.) $SETPROXY(127.0.0.1:8081)(^)in sidki's set. This way the keyword is always set regardless of the other list entries and the other list entries are checked. When I $RDIR in Exceptions-U to block a connection I'll be using something like Code: unwanted.com/ $USEPROXY(false)$SET(keyword=i_proxy:0.)$RDIR($GET(blackhole)/killed.gif?\u)otherwise the rear proxy will be asked for "killed.gif". However, the new routine works better with sidki's set in bypass while using the Proxomitron's "Use Remote Proxy" setting. I'm not sure why. So, I'm also using the Proxomitron's default set with the web filters bypassed and this, Code: [HTTP headers], header filter to test the routine. Current issues 1. When searching at startpage.com Code: 127.0.0.1 - - [30/May/2014 08:42:40] "GET http://s10-us4.startpage.com/tst2/engl2. Need to find a server with bad certification for testing. Got to go. |
|||
|
« Next Oldest | Next Newest »
|

Search
Member List
Calendar
Help







![[-]](images/ONi/collapse.gif)