Re: redirects for HTTPS (seems to) fail

Fabian Keil <[email protected]> Thu, 13 Feb 2020 12:26:55 +0100

Newsgroups	gmane.comp.web.privoxy.user
Message-ID	<[email protected]>

[email protected] wrote:

> I set this user-action
> 
> { +redirect{https://www.privoxy.org/user-manual/actions-file.html} }
> paf
> 
> so I expect http://paf or https://paf to get the 'actions' guide.
> But it works for http: only, whereas https: yields just (another)
> 'crunch' hence 'Unable to connect' from browser. Here's the log:
> 
> https://paf/ (url address in browser) -> privoxy log:
> 	
> 2114	Crunch: Redirected: paf:443
> 00000af4	Redirect: No pcrs command recognized, assuming that
> "https://www.privoxy.org/user-manual/actions-file.html" is already
> properly formatted. 00000af4	Redirect: New URL is:
> https://www.privoxy.org/user-manual/actions-file.html 00000af4
> Actions: +change-x-forwarded-for{block}
> +client-header-tagger{css-requests}
> +client-header-tagger{image-requests}
> +client-header-tagger{range-requests} +hide-from-header{block}
> +set-image-blocker{pattern} 00000af4	Crunch: Redirected: paf:443
> 
> isn't it supposed to work regardless of the protocol?
> 
> Using privosy 3.0.28 on Windows

Modern browsers no longer follow unencrypted redirects
in case of https requests.

Fabian

_______________________________________________
Privoxy-users mailing list
[email protected]
https://lists.privoxy.org/mailman/listinfo/privoxy-users

signature.asc (application/pgp-signature, 833 B)