Re: Text replacement doesn't work
Fabian Keil <[email protected]> Thu, 27 Jan 2022 17:26:35 +0100
| Newsgroups | gmane.comp.web.privoxy.user |
|---|---|
| Message-ID | <[email protected]> |
Matteo Spigolon <[email protected]> wrote on 2022-01-27 at 14:31:55: > Verified in http://config.privoxy.org/show-status > <http://config.privoxy.org/show-status> > > #define Enabled > FEATURE_HTTPS_INSPECTION Yes > > In /etc/privoxy/config I made these changes: > > - uncommented the "ca-directory /etc/privoxy/CA" row > - uncommented the "ca-cert-file cacert.crt” row > - uncommented the "ca-key-file cakey.pem” row > - uncommented the "certificate-directory /var/lib/privoxy/certs” row > - uncommented all the rows of the cipher lists > - generated caret.crt and cakey.pem and put them in /etc/privoxy/CA > (command: openssl req -new -x509 -extensions v3_ca -keyout cakey.pem > -out cacert.crt -days 3650) > - uncommented the "trusted-cas-file trusted_cas_file.pem”, downloaded > the example file "https://curl.se/ca/cacert.pem > <https://curl.se/ca/cacert.pem>” and renamed it. > > In /etc/privoxy/user.action Inserted these rows: > > +ignore-certificate-errors > {+https-inspection} Both actions should be inside the curly braces. > corriere.it > www.corriere.it > it.wikipedia.org > wikipedia.org > www.wikipedia.org <http://www.wikipedia.org/> > > Then I restarted the privoxy service without errors In the log file. Unfortunately currently many configuration problems are only detected when actual requests are made that are affected by them. The following TODO list items are relevant here: | 22) Verify action files properly (Including arguments) and | act accordingly (should probably intercept all requests | with a "Invalid option foo detected" CGI page). | | 23) Do the same in case of syntax errors in the configuration file, | instead of just exiting or ignoring the problem. https://www.privoxy.org/gitweb/?p=privoxy.git;a=blob;f=TODO;hb=HEAD#l57 > When I visit one of that sites I got this error: error during the > connection at it.wikipedia.org. PR_END_OF_FILE_ERROR > > Which mistakes I made? The PR_END_OF_FILE_ERROR error often indicates that Privoxy shutdown without properly serving the browsers request due to a configuration problem. If logging is enabled the Privoxy log file should contain an explanation for this. 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----- iQIzBAEBCAAdFiEETzbBfzgWkTZUoehQaRgikYuiNxwFAmHyx7wACgkQaRgikYui Nxy8lg/+L8ZOntsfSGA7zzmOi5UW8yCLLMz4ZvJpQv7pWXzMPit56r6YvZYdgBsb 4oydGOXG6J4B3Uh6rEVN2UlyQ2DZLBuEjnK7saRlXE/TVaPRZj2CprvoJnfCpMb9 3zkBAKHzxh7PwDQTnnnStS2VS+Dr7DkEv3SeAAt5QqaZDzqbitLrsE8T2O6TZEAj QryuaXwu2jRWTGxPszrdAmKFFhyv3rVsAca6GXm6wy/QJ6p4A5ao8SJjztvYUeOq zZLvM+kFoHxOKn7EnJ5dK8sczlgu9rR/mcuEsqFy5Cdg+FageB/PuOWp70FYswAc cB3Wob/IjtV64zdYDNZhSrzYM8jK1dZufkedYHyj0obTE6nh4fx8qh2MYCw3YyBG ZoCUcwOE6DMLaiGMdu/219FyRNuNeZEzaae8DYz/fFA5WCMxLWM4WRdLnqBzDdM7 5rBq86l7a2AQz1Suo7xjusuq9C5Qlwuaa0RcBhLHKcW3WLx/83y+UKfznDbTcU6H qmGJ4maZ+mjATzXrX9O0Kf+Ppv1z1XQP3Dzmf7BVpgi5J6JigwlWQMTnz213NhZ2 J4yBEK+opz01vfnYjIZbT1mTG6kI4skm8Xznc//tsm2RvypWjRSKNURGeHu1hzmk Vyp273ZB0H4a+Gjc4DUxyJbYf7h56oHDH4IFJ3PElYJvu5xqHIo= =LJ1r -----END PGP SIGNATURE-----