Re: Configure privoxy to proxy all requests to the same web page

Fabian Keil <[email protected]> Thu, 11 Nov 2021 12:01:56 +0100

Newsgroups	gmane.comp.web.privoxy.user
Message-ID	<[email protected]>

Steven Smith <[email protected]> wrote on 2021-09-27:

> I’ve set match-all.action to:
> 
> > { \                                                                             
> > +redirect{http://localhost:8119/} \                                             
> > }                                                                               
> > / # Match all URLs                                                              
> 
> 
> 
> This works as expected for HTTP:
> 
> > curl -I -L --proxy http://localhost:8118 http://whatever.com/
> 
> This problem is with HTTPS:
> 
> > curl -I -L --proxy-insecure --proxy http://localhost:8118 <http://localhost:8118/> https://google.com/?q=foobar

I assume the "<http://localhost:8118/>" is the result of
Mailman trying to convert HTML to text?

> > HTTP/1.1 302 Local Redirect from Privoxy
> > Location: http://localhost:8119/
> > Content-Length: 0
> > Date: Mon, 27 Sep 2021 17:47:49 GMT
> > Connection: close
> > 
> > curl: (56) Received HTTP code 302 from proxy after CONNECT

Note that the use of "--proxy-insecure" is pointless as
the connection between curl and Privoxy is not actually
encrypted until the CONNECT request has been answered.

Having said that, the command:

curl -I -L --proxy-insecure --proxy http://privoxy-jail:8118  https://google.com/?q=foobar

seems to work as expected for me
using curl 7.79.1 and Privoxy 3.0.33 build from git on
ElectroBSD 12.3-STABLE d61efdec91d1.

If you can still reproduce the issue, please add "--trace -"
to the curl command.

Fabian

_______________________________________________
Privoxy-users mailing list
[email protected]
https://lists.privoxy.org/mailman/listinfo/privoxy-users

signature.asc (application/pgp-signature, 833 B)