On Fri, 28 Nov 2003, Hrvoje Niksic's patch:
This patch implements a first attempt of using the CONNECT method to
establish passthrough of SSL communication over non-SSL proxies. This will
require testing.
I find this wording a bit funny. What is a non-SSL proxy? CONNECT is the
defined way to
On Fri, 28 Nov 2003, Hrvoje Niksic wrote:
I find this wording a bit funny. What is a non-SSL proxy? CONNECT is the
defined way to speak SSL when using a http proxy...
What if someone explicitly uses http_proxy=https://...? Or even
https_proxy=https://...?
Ah, right! *That* is indeed a
Karsten Hopp [EMAIL PROTECTED] writes:
I'm working on it ;-) I'd like to put a CVS version into rawhide to
get more feedback about the current status but that makes only sense
when the next official version will be released before 'Fedora Core
2' as I won't put a beta version into a Fedora
On Fri, 28 Nov 2003, Hrvoje Niksic wrote:
The bottom line is: should I even acknowledge `https' proxies?
I don't think you'll ever run into any.
Do the browsers work with them?
I don't know. I've never seen anyone use a proxy like that.
Does curl handle `https_proxy' or `http_proxy' being
I tested the Windows binary against the only SSL-enabled web server outside
our firewall that I could think of at the moment, and it worked for me.
Mark Post
-Original Message-
From: Herold Heiko [mailto:[EMAIL PROTECTED]
Sent: Friday, November 28, 2003 3:18 AM
To: [EMAIL PROTECTED]
Cc:
