Re: HTTP status code for blocked pages
Fabian Keil <[email protected]> Sat, 31 Jul 2021 15:09:13 +0200
| Newsgroups | gmane.comp.web.privoxy.user |
|---|---|
| Message-ID | <[email protected]> |
Jamie <[email protected]> wrote on 2021-07-30: > Is there any way to alter the HTTP status code returned by Privoxy when > a page is blocked? The "normal" action is to present a response page > with a "Go there anyway" link, but that page isn't being shown for me in > Firefox -- instead it shows the default Firefox error page "The proxy > server is refusing connections". As such, I can't click through. > > If I examine the network traffic, I can see the "403 Request blocked by > Privoxy" response, so I'm fairly certain I'm getting to Privoxy. I > think it's because of the 403 status code. If I'm reading Firefox's > Bugzilla 493699 (https://bugzilla.mozilla.org/show_bug.cgi?id=493699, > closed WONTFIX), Firefox does not show the custom content for > non-successful proxy responses. > > While 403 is probably the right status code, I'd like to alter this to > something 2xx (maybe 202 or 203) to bypass this behaviour. I appreciate > that this change might not be for everyone, so I am hoping for a config > value somewhere. > > I'm running an older release at the moment (and am constrained by my > OS's packaging), so I'm happy if the answer is "has been fixed/provided > in vX" but, if it hasn't been considered, is there any mileage in a > config/override setting? There currently I no option to change the status code for the "Blocked" page and I think having such an option would not solve your problem anyway. I suspect you're only seeing the issue for HTTPS requests with https-inspection disabled. https-inspection has been added in Privoxy 3.0.29 and allows Privoxy to send the "Blocked" page encrypted in which case it appears to the client as if it was sent by a server. 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----- iQIzBAEBCAAdFiEETzbBfzgWkTZUoehQaRgikYuiNxwFAmEFS3kACgkQaRgikYui NxyI1A/8CACt9G1zrnyXzZjBlgNlNKkYIZpGrgsaG7CMQSLboInrX3aeEI0tI1s+ iqLG8sTOg9I/6l2Ls+m7rxc+kcpM/DC2GwOthMZnng8q4xX6euo4EIAprVPlF67J 4IpdBO3JOZJTHw0bcBzZWkNH1b2D34LcNL6gJ6R6Nzd5Ie084SWJdqqjVcfoBmMH /5sCaDr5mEwpyvgqKDzr+yePyOCPyZwLzEKdEwciON/tSoPwlk4txZgD77cYy0Ww 8UKtq1rnzBJL3ztJpuxqj9qmjHyWoKd1Iy/vT9Ok8qCLwrSmFrFrbOxgfafq+Mjz QspFYd1o2Va4EOlGweEd8qCk1M4/R737l62bdbE9suN+2EcTiZNbSzeK/I/8Tucp Kis4t5wBTHFEHCpRFtc9xi/rSXCv2intZTA/bUF4Y9vx0OnbXzmKJ+CwpcyTIQK+ gx4yGvE4fnwZcbGxDLCCKWW/CfCJckenT79Dd5pTbFlVbvjKA6a4c6F/kdcWx3Rj +VYTU1daePuq7GDzeN+xb7sXwwR4tA7cZcXSOk9Nh5OOJUuPM5ozNEgoyqtgFzKb 2SuPRJgmjW7QjvvTAj+yFH/areNuq5Rvgh4GOUnQTeyfzvpsnBpT5M+LA0AuG1id e5XpAUUTAf4iOJyUn5QLOFVE6oKmmwVZ1RIGWallGmkW9vqBOJU= =zEmt -----END PGP SIGNATURE-----