[Privoxy-users] Text replacement doesn't work

[Fabian Keil]

Matteo Spigolon <ns at fabbricapolitica.com> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.privoxy.org/pipermail/privoxy-users/attachments/20220127/40f71547/attachment.bin>