From owner-freebsd-questions@FreeBSD.ORG  Wed Nov 21 15:37:51 2007
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3B0AB16A418
	for <questions@freebsd.org>; Wed, 21 Nov 2007 15:37:51 +0000 (UTC)
	(envelope-from wmoran@collaborativefusion.com)
Received: from mx00.pub.collaborativefusion.com
	(mx00.pub.collaborativefusion.com [206.210.89.199])
	by mx1.freebsd.org (Postfix) with ESMTP id CEF4013C46B
	for <questions@freebsd.org>; Wed, 21 Nov 2007 15:37:50 +0000 (UTC)
	(envelope-from wmoran@collaborativefusion.com)
Received: from vanquish.pitbpa0.priv.collaborativefusion.com
	(vanquish.pitbpa0.priv.collaborativefusion.com [192.168.2.61])
	(SSL: TLSv1/SSLv3,256bits,AES256-SHA)
	by wingspan with esmtp; Wed, 21 Nov 2007 10:27:48 -0500
	id 0005644A.47444E74.0000731D
Date: Wed, 21 Nov 2007 10:27:48 -0500
From: Bill Moran <wmoran@collaborativefusion.com>
To: questions@freebsd.org
Message-Id: <20071121102748.4a05333f.wmoran@collaborativefusion.com>
Organization: Collaborative Fusion
X-Mailer: Sylpheed 2.4.4 (GTK+ 2.10.14; i386-portbld-freebsd6.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: 
Subject: Questions on behaviour of fetch(3) regarding HTTPS + proxy
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2007 15:37:51 -0000


It seems that if I set HTTP_PROXY, fetch(1) works just dandy, _UNLESS_
I'm trying to fetch an https document, in which case it seems to
ignore HTTP_PROXY.

I suspect that this is occurring somewhere in the fetch(3) library, as
the htmldoc port behaves the same way.

Is this intended behaviour?  If so, how can I control it?  The systems
in question have no way to connect without using the proxy, and I'd
like to convince fetch(3) to use the proxy for https as well.  My
perusal of the documentation hasn't turned up anything related to this,
so I'm grepping through the source code right now.

-- 
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran@collaborativefusion.com
Phone: 412-422-3463x4023