Re: forward-override based on user-agent tag does opposite of what it should
Fabian Keil <[email protected]> Wed, 18 Oct 2023 15:37:39 +0200
| Newsgroups | gmane.comp.web.privoxy.user |
|---|---|
| Message-ID | <[email protected]> |
--===============2805348379351850294== Content-Type: multipart/signed; boundary="Sig_/Vy2bK5UzkE1LshyN/E0fM42"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Sig_/Vy2bK5UzkE1LshyN/E0fM42 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Synan B <[email protected]> wrote on 2023-10-18 at 11:30:07: > 1. Enabled debug 128 & 65536 in privoxy/config > 2. # privoxy --no-daemon (to see headers output) You could also enable logging: https://www.privoxy.org/user-manual/config.html#LOGFILE > 3. In privoxy/user.action > {+client-header-tagger{user-agent}} > / >=20 > {+forward-override{forward-socks5t 127.0.0.1:9050 .} } > TAG:^User-Agent: FreeBSD >=20 > 4. Switch the user-agent of browser to custom testing entry: FreeBSD > http://config.privoxy.org/show-request confirms: User-Agent: FreeBSD >=20 > PROBLEM: > * Traffic from browser is NOT redirected to Tor proxy > * Traffic from browser to http://config.privoxy.org shows correct header > +forward-override{forward-socks5t 127.0.0.1:9050 .} It would help to see a Privoxy log excerpt. If you add: debug 4 # show tagging-related message You should get lines similar to this: 15:22:20.583 034 Tagging: Tagger 'user-agent' added tag 'User-Agent: Mozill= a/5.0 (X11; FreeBSD amd64; rv:109.0) Gecko/20100101 Firefox/115.0'. Action = bits updated accordingly. or: 15:26:02.603 013 Tagging: Tagger 'user-agent' added tag 'User-Agent: Mozill= a/5.0 (X11; FreeBSD amd64; rv:109.0) Gecko/20100101 Firefox/115.0'. No acti= on bits update necessary. The last sentence is relevant here. If Privoxy claims "No action bits update necessary." it means the tag didn't affect the action settings. If you modify the debug settings anyway you could enable the other debug settings suggested at: https://www.privoxy.org/user-manual/contact.html as well. > So packets to External are not redirected, but packets to Internal are? As an HTTP(S) proxy Privoxy only deals with connections not individual packets. Fabian --Sig_/Vy2bK5UzkE1LshyN/E0fM42 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEETzbBfzgWkTZUoehQaRgikYuiNxwFAmUv36MACgkQaRgikYui NxwdXxAAiaZGIw0bO9Vpkr1uqIa1EOruDvPcerxVSmcE3gKczKvgffXq7/9nPEz8 0rv4OeP4EdjxtoIeCyw8mERig/E53m/GmapJGJuz4g5JkAdGJGeAC7xX8ZSmGjvl kFDnX+4vrHpIIwY8qO8cRUDjRyHndS4E0gWGyqVVq7WMdbOUpSAEp1XkmvyQabvK WRNAC2nVoWX09T9uoW6RF1Lpor/NuRb5uevo+OItX52V1j9xSm7O2tu9hy5Hw/6Q ajeJqhYSRItZVWQpkyI10z2UofIGk34z3N4L4fhmVNuhNNxDd+0CexybkO3tkCxq uKdrQTGnLX4Q/oeb5Q2nxMT9OQYm7d7vru8cmSDynlBvDa5Hl2zPvV4SjdmYJ0+4 sJdftSi4Lgh3TxInay50Ip6/+WyK2t5PgniQm5VKlL5XNZArk0JaLIdo/QJOYPWQ aLs/yncg/WkJUg3vVH3ksXEsVt3Q+99RAOnrzAj9Sg0Ie2j9PLqJ9LQs1oFUA8bt n51ODp4IPmXq6UfcmJzzDTLf+3GVj04JbfhndT07ddlo8y+1v4V7IoOKukoSxOcO NeRnJ5QccmiImtZ6xrqQ8gkdPU4P633bcH/iXDOLw/NRQCvlNbgpICYSvNr0OWhB GtsVhofOBslbTubcwk8w0cEOfzS+VLGGpfSojmeB2itxsxdtZMQ= =Rcio -----END PGP SIGNATURE----- --Sig_/Vy2bK5UzkE1LshyN/E0fM42-- --===============2805348379351850294== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Privoxy-users mailing list [email protected] https://lists.privoxy.org/mailman/listinfo/privoxy-users --===============2805348379351850294==--