ProxHTTPSProxyMII: Reloaded
|
Apr. 05, 2016, 04:57 AM
(This post was last modified: Apr. 05, 2016 05:37 AM by JJoe.)
Post: #145
|
|||
|
|||
RE: ProxHTTPSProxyMII: Reloaded
(Apr. 05, 2016 02:44 AM)zoltan Wrote: I installed python, but couldn't get ProxHTTPSProxy.py to work. It pops up, then disappears. Did you also install all the required libraries, openssl, pyopenssl, colorama, urllibs, PySocks? Note that Python 3.5+ cannot be used on Windows XP or earlier. (Apr. 05, 2016 02:44 AM)zoltan Wrote: I also noticed your post in the other thread about "http support lost" with ver 1.4. Doesn't that render it pretty useless anyway? No, I need to delete or change that post. Before 1.3, I would set the Proxomitron to forward both http and https to the rear proxy. Now I can only forward https. So http isn't lost. I just can't do what I was doing. (Apr. 05, 2016 02:44 AM)zoltan Wrote: Maybe it's best I just stick with 1.3.1, since it does seem to work if you add items to the no-verify list. I read your post from Feb 13 '15 about adding an "*" to the list. That seems like a perfect solution, so I'm wondering if it really is or if there's any real downside to it if you limit its use to a wired connection. I already switch to no proxy for banking or anything similarly sensitive. I ask because in the past few days with more use there are more sites showing SSL errors in the log. Adding each one to the list seems excessive/annoying. Your behaviour seems safe enough but I can't be certain. I haven't tested adding * to the list. |
|||
« Next Oldest | Next Newest »
|