[privoxy-users] [ ijbswa-Support Requests-1466386 ] https

[SourceForge.net <no...@so...>]

Support Requests item #1466386, was opened at 2006-04-07 11:14
Message generated for change (Settings changed) made by hal9
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=211118&aid=1466386&group_id=11118

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuration
Group: None
>Status: Pending
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: https

Initial Comment:
I would want to know as I can make in order to visualize the pages that they begin for es: https://www.nome dominio.com:8443/ 



naz...@ca... 

tank you

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2006-07-22 13:35

Message:
Logged In: NO 

I think, the problem is, that novadays more and more "evil" 
sites use https to protect their evil jscode and cookies 
from proxy servers.
Since https requests can not be filtered, Privoxy is 
useless if you ever click on a https link!

No, that is not a bug, but it is a lack of usability.
What is Privoxy good for, if you just need to use https to 
get all the referer and cookies and make the boring ads 
displayed again (and the webbugs too)?
There should be an option to use Privoxy to intercept https:
1. Privoxy could act as the server and the browser will get 
a secure connection to the proxy insteed of the original 
server.
2. Privoxy decrypts the request from the Browser and makes 
a new https request to the original server.
3. Privoxy receives the content from the original server, 
decrypts and filters ist - then it encrypts it for the 
browser.
4. The browser displays the "washed" page.

Sure, the browser will issue warnings about not matching 
certificates - but who cares, if i haveto click once more 
to be safe?

Allan Wegan (all...@al...)

----------------------------------------------------------------------

Comment By: zanni (zanni06)
Date: 2006-04-10 22:13

Message:
Logged In: YES 
user_id=1498470

This sentence does not make sense in English. Could you
please try explaining the problem another time? 

http://www.nome domino.com:8443 is not correct. Also, please
give your OS and browser versions (firefox, ie, etc).

-----

Esta oración no tiene razón en ingles. Por favor, usted
podría explicar la problema otra vez? 

http://www.nome domino.com:8443 no es correcto. Tambíen, por
favor, da su OS y browser versiones (firefox, ie, etc).

-----

Cette phrase ne se comprend pas en anglais. Pourriez-vous
svp essayer d'expliquer le problème une autre heure ? 

http://www.nome domino.com:8443 n'est pas correct. Donnez en
outre, svp votre l'OS et versions de navigateur (firefox,
IE, etc..)

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2006-04-09 15:56

Message:
Logged In: NO 

I think you are looking for the config option to allow 
CONNECT method for SSL to ports other than :443.

+limit-connect{443,8443}

----------------------------------------------------------------------

Comment By: Andrew J. Caines (cainesaj)
Date: 2006-04-09 15:29

Message:
Logged In: YES 
user_id=10334

HTTPS pages are encrypted with SSL/TLS between the client
(browser) and the server and therefore cannot be filtered by
the proxy.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=211118&aid=1466386&group_id=11118