From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by hurricane.the-brannons.com (Postfix) with ESMTP id 8A61A77CD1 for ; Thu, 3 Jul 2014 02:21:23 -0700 (PDT) Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta05.westchester.pa.mail.comcast.net with comcast id MlMN1o0010SCNGk55lMNSg; Thu, 03 Jul 2014 09:21:22 +0000 Received: from eklhad ([IPv6:2601:4:53c0:29b:21e:4fff:fec2:a0f1]) by omta09.westchester.pa.mail.comcast.net with comcast id MlMM1o00B1A47pm3VlMMV1; Thu, 03 Jul 2014 09:21:21 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.1 Date: Thu, 03 Jul 2014 05:19:51 -0400 Message-ID: <20140603051951.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1404379282; bh=zpZDliZ09SdYsiEhThHHkODIFrr1fCMjW425yVoZXW4=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=j2JqaboxLhLq4kmv00LP8mc6w9En70W2EgO/KrZP9k39QVNX0AXiFUz1tYpCbG1ZQ PmXnWvMOJPEvQyigbsgl3x/vlyEgFMA1Kds1E//PHDexTKZ6hLCsNUL347QJXM7QK1 DpiszUyQj0JFKRz9fsJGq8Ny8nO0kSz0sKnMBG2o/FaTdATv4ClG5St2ejwC5QN116 Kpjsici5YHP25Ejhs6gSwJoqUcduZQ/9VIw04cLP5SxR8NNYKpfmZIhFTnm4AZGeVy nJ8p756Jgc4GvuyxxRxC5zG0xnbfC2gwKbWuXzKvAzhEEEfUHIAd5lso0uQH/G2XMQ N5P6rwGWyqJTA== Subject: [Edbrowse-dev] A couple of feature requests X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2014 09:21:23 -0000 > As far as I'm aware there's no way in edbrowse to support proxy exceptions, Chris you've done more curling than the rest of us. Can you specify proxy exceptions within curl? If not, and I'm guessing not, then we have to move the PROXY curl call from my_curl_init() into httpConnect, so it can be done per host. If we had set a proxy on the last http fetch, can we then unset it, or set it to null or "" or some such, so as not to use any proxy on this fetch? Will that work? If yes then I could implement this one without a lot of fuss. I may start by setting up noprox in the config file, the way we have nojs now. That would build the list of exceptions, which is the needed infrastructure. I'll have to think about your 401 request, there's more going on there. Karl Dahlke