Re: rewriting the Host header, switching protocols
Fabian Keil <[email protected]> Thu, 23 Mar 2023 08:54:48 +0100
| Newsgroups | gmane.comp.web.privoxy.user |
|---|---|
| Message-ID | <[email protected]> |
Madhu <[email protected]> wrote on 2023-03-23 at 09:55:27: > Hello, thanks for publishing privoxy. There are two strange scenarios > that have cropped up (don't ask why) > > 1. To rewrite the Host: header of a forwarded request to a target > webserver (based on certain criteria) This is supported and can be done with a client-header filter: https://www.privoxy.org/user-manual/actions-file.html#CLIENT-HEADER-FILTER You can use tags or URL patterns to decide when to apply the filter. > 2. To switch the protocol from HTTPS to HTTP when forwarding a request > to another proxy (typically local, again based on certain criteria) This can be done by rewriting the protocol in the URL in the request line with a client-header filter. Upgrading from HTTP to HTTPS is currently unsupported, though. Fabian _______________________________________________ Privoxy-users mailing list [email protected] https://lists.privoxy.org/mailman/listinfo/privoxy-users
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEETzbBfzgWkTZUoehQaRgikYuiNxwFAmQcBcgACgkQaRgikYui Nxwo/g//WuXcna4NESW/ksYNeKacdYyH96oXGp1yIf60OBs2+LGpBNpA9lSjoEO7 Q2k+njz5IlfFeZRl/qyv5RYPDLE4IrjYI1LXtVGyk8jehtTUbV23nvuGyVHu0feq XB8NYTCpH7SC6Ym8fafpk//XO3f4BcLkeLOYOcQ+tQswyoIXtSYGqI2QVxn+j+Fm i0O9tgvFBs7USbG0Ke7qiOvwnR3MMbF5kU5YWCE7roa+Ss41VzbX/d7ETRFeg+fu excZ98o+S8knk9tTHVJSuRFrISQjzRl5Y8mr3b8aNq1OXyBNtv1Q0NZkhhIvI4ya ms6Q+iLjtpE13FxNeeX+VfWP9uAaFk4rN6EYYouO8WoJSAWu3OVHH5qi3g7U7CCh Y/68IhG78aXPHNQ0sIWWwBC2rN2f7cF6F99dY0uhbNG0nx5O61mdQbkHvHwY6mho EiY4S68W8PCprosv93tq0+2NrXI4+YRlU2pb30KudLmklx6sf1YrCppH0nrns/tH gEY27RgvXxM39BDe/xwHLCclUGzXbZLJlkS6hOR4AT+Gh6aejvlwHtvZYtfbr0Gb 6MVXKtIsMWUsyaxG5N/6Eef/8U5GLj4pHNkHWbbgf4xtiyg4gxZTs4+G7aqMg9Se +yynt/CuykVwGN/qQ6C7AKH7YkEaMzYikzuoOfQUZdKfSCgQSwo= =SrJU -----END PGP SIGNATURE-----