[prev in list] [next in list] [prev in thread] [next in thread] 

List:       privoxy-developers
Subject:    [privoxy-devel] [ ijbswa-Bugs-1401974 ] Empty documents with HTTPS
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2006-08-29 12:48:57
Message-ID: E1GI31V-0002Wx-43 () sc8-sf-web4 ! sourceforge ! net
[Download RAW message or body]

Bugs item #1401974, was opened at 2006-01-10 19:36
Message generated for change (Comment added) made by fabiankeil
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=111118&aid=1401974&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: other
Group: version 3.3
>Status: Pending
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Fabian Keil (fabiankeil)
Summary: Empty documents with HTTPS on ports other than 443

Initial Comment:
HTTPS on ports other than 443 is resulting always in an
empty document.

There are no entries in the log files, no browser
error messages.  Nothing.

That is the rule:

forward / proxy.somedomain.tld:3128

Even if I set up such kind of rules:

forward / proxy.somedomain.tld:3128
forward proxy.somedomain.tld:3000 .
forward proxy.somedomain.tld:10000 .

Versions:
privoxy 3.0.3-3
Debian 3.1
Squid 2.5Stable5 on proxy.somedomain.tld:3128
Problem exists with IE, Firefox and Opera
On port 10000 is webmin
on port 3000 is ntop

No change if privoxy is forwarding to local address, i.e.

forward / 127.0.0.1:3128
forward proxy.somedomain.tld:3000 .
forward proxy.somedomain.tld:10000 .

If privoxy isn't used at all, it's running fine.

Please advice.

mail (at) uwe (dash) disch (dot) de


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

>Comment By: Fabian Keil (fabiankeil)
Date: 2006-08-29 12:48

Message:
Logged In: YES 
user_id=875547

Either disable limit-connect by default,
or make exceptions for the sites where you
need Connect requests to ports other than 443.

In the next Privoxy release (or in the current
cvs version) you can also enable
treat-forbidden-connects-like-blocks to get
the error message inside the body instead of
the headers where nobody is looking.

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

Comment By: Fabian Keil (fabiankeil)
Date: 2006-01-19 11:50

Message:
Logged In: YES 
user_id=875547

You probably are using limit-connect.

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

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

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Ijbswa-developers mailing list
Ijbswa-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ijbswa-developers
[prev in list] [next in list] [prev in thread] [next in thread]