The Un-Official Proxomitron Forum

Full Version: 502: No server or forwarder data received
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi!

I try to use ProxHTTPSProxyMII with privoxy. However when I try to load the index.html file I get an 502 no server or forwarder data received.

Privoxy can use the redirect rules that I set up, but even if I uncomment them I cannot reach the remote server due to the error message. So I would like to have a mixed served site, part of it (data) coming from the backend while development can occur locally - and served locally.

If I set privoxy back to 8118 (taking MII out of the way) then privoxy receives an answer, but I want privoxy to see the https traffic, so this is not really an option.

Do you have an idea how to avoid this and make privoxy work with MII?
The problem was that I had the old tag in place. I just had to make these amendments, that I have found here, after careful reading the fifth(! - concentrated too much on other details) time: https://sourceforge.net/p/ijbswa/support-requests/1667/

* Replace previous [email protected]: Proxomitron [email protected]$[email protected] (cf. user.filter) by new one: [email protected]^.*Tagged:.*ProxHTTPSProxyMII.*FrontProxy.*@$[email protected]

*Replace previous TAG:.*?Proxomitron (cf. user.action) by new one: TAG:.*?ProxHTTPSProxyMII
(Oct. 11, 2016 06:30 PM)szebenyib Wrote: [ -> ]The problem was that I had the old tag in place. I just had to make these amendments, that I have found here, after careful reading the fifth(! - concentrated too much on other details) time: https://sourceforge.net/p/ijbswa/support-requests/1667/

* Replace previous [email protected]: Proxomitron [email protected]$[email protected] (cf. user.filter) by new one: [email protected]^.*Tagged:.*ProxHTTPSProxyMII.*FrontProxy.*@$[email protected]

*Replace previous TAG:.*?Proxomitron (cf. user.action) by new one: TAG:.*?ProxHTTPSProxyMII

Thank you, so this is the change for ProxHTTPSProxy 1.3+. But the support ticket on Privoxy dev is no longer open so I will rewrite the tutorial here, I will try to add as much information as possible so end-user(s) can learn quickly:

To use Privoxy with ProxHTTPSProxy (also mean "to make Privoxy filter HTTPS websites"):

- Make sure you have both Privoxy (http://privoxy.org) and ProxHTTPSProxy (https://prxbx.com/forums/showthread.php?tid=2172 , don't worry about 1.3+ or 1.3-, my new filter will work on all version of ProxHTTPSProxy) in your computer.

- Open Privoxy's user.filter, add this filter and save:
Code:
CLIENT-HEADER-TAGGER: tagger4https
[email protected]:.*?(FrontProxy)@$[email protected]
- Open Privoxy's user.action, add and save:
Code:
{+client-header-tagger{tagger4https}}
/
{+forward-override{forward 127.0.0.1:8081}}
TAG:FrontProxy
- Open ProxHTTPSProxy's config.ini, replace and save:
Replace
Code:
ProxAddr = http://localhost:8080
With
Code:
ProxAddr = http://127.0.0.1:8118
- Change your web browser's HTTP Proxy to 127.0.0.1:8118 and HTTPS Proxy to 127.0.0.1:8079. (For Firefox's user: http://prntscr.com/d0kvom)
- Import ProxHTTPSProxy's CA.crt to your browser. (For Firefox's user: http://prntscr.com/d0kwca , http://prntscr.com/d0kwu7)

And everything is done! Happy surfing!

I just want to notice that you can use ProxHTTPSProxy on all operating system, you just need to use ProxHTTPSProxy.py and make sure you install Python on your operating system, then install colorama, urllib3, pyOpenSSL for Python.

Hope my tutorial will be helpful. Thanks for reading.
(Oct. 29, 2016 08:06 PM)cattleyavns Wrote: [ -> ]- Open Privoxy's user.action, add and save:
Code:
{+forward-override{forward 127.0.0.1:8081}}
TAG:FrontProxy

In the same user.action file, should we not add…
Code:
{+client-header-tagger{tagger4https}}
/
prior to your entry?
(Oct. 29, 2016 09:30 PM)Faxopita Wrote: [ -> ]
(Oct. 29, 2016 08:06 PM)cattleyavns Wrote: [ -> ]- Open Privoxy's user.action, add and save:
Code:
{+forward-override{forward 127.0.0.1:8081}}
TAG:FrontProxy

In the same user.action file, should we not add…
Code:
{+client-header-tagger{tagger4https}}
/
prior to your entry?

That is right, I really don't know why I can forget that. Thanks.
wrong thread Sad
Reference URL's