Date: Fri, 12 Apr 2013 14:58:23 -0400 From: Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> To: Bernhard =?iso-8859-1?Q?Fr=F6hlich?= <decke@FreeBSD.org> Cc: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= <des@des.no>, freebsd-ports@freebsd.org, Fernando =?iso-8859-1?Q?Apestegu=EDa?= <fernando.apesteguia@gmail.com> Subject: Re: redports.org No address record Message-ID: <44k3o78tkg.fsf@lowell-desk.lan> In-Reply-To: <CAE-m3X3y-vf2HvXSY6-DF70j5F0HUnDJ-uBbWQ6-CD_5jyE5LA@mail.gmail.com> ("Bernhard =?iso-8859-1?Q?Fr=F6hlich=22's?= message of "Fri, 12 Apr 2013 20:08:33 %2B0200") References: <CAGwOe2ZeF-19Geam=JovJZytcp6LqaMg-KLrL7sLtwOw39CGnQ@mail.gmail.com> <CAE-m3X3y-vf2HvXSY6-DF70j5F0HUnDJ-uBbWQ6-CD_5jyE5LA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Bernhard Fr=F6hlich <decke@FreeBSD.org> writes: > Since our fetch(1) does not support proxies for HTTPS connections > it tries to lookup the domain himself and fails because it does not > have a DNS server or direct internet access. So in the end it is a > bug or missing feature of our fetch. I've CCD des@ just in case he > has a good idea. Is there some reason proxy support for HTTPS would be particularly difficult? There's already per-scheme handling for proxies, as I recall. I could try to make some time to implement this, if it's just=20 a matter of coding it up.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44k3o78tkg.fsf>