Return-Path: X-Original-To: apmail-hc-httpclient-users-archive@www.apache.org Delivered-To: apmail-hc-httpclient-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 04B7D99C7 for ; Sun, 18 Mar 2012 19:18:00 +0000 (UTC) Received: (qmail 37304 invoked by uid 500); 18 Mar 2012 19:18:00 -0000 Delivered-To: apmail-hc-httpclient-users-archive@hc.apache.org Received: (qmail 37274 invoked by uid 500); 18 Mar 2012 19:18:00 -0000 Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-users@hc.apache.org Received: (qmail 37262 invoked by uid 99); 18 Mar 2012 19:18:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Mar 2012 19:18:00 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ideawheel@gmail.com designates 209.85.210.179 as permitted sender) Received: from [209.85.210.179] (HELO mail-iy0-f179.google.com) (209.85.210.179) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Mar 2012 19:17:54 +0000 Received: by iakh37 with SMTP id h37so8747257iak.10 for ; Sun, 18 Mar 2012 12:17:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=SS/cgSi7PoY/criojenDcMQkTRNpER4A6DgjTN1/Fjg=; b=A0YF/RaCZX3jJocF2iCkfD32sx/NwLXF9ClWcj6AnH3zocbDEZUFqsn0mxN05SdnS6 GJXYWtcBgEcw+z3lItKNucd9UqlzoQBPFGNVIo9piFa+VvDweIzLpHT6uOMa6XTDL5IA jPHXjSvJhVr+UHLOj828mAlAUFEXgvp/jB69D+gEPZ6o4inHsGpMG2NG9UG+cdCHbcKA fxnf7Tn9ejLVFeakZWu2hHovPMdkceiMJJ/mm1nDE6pCm/FKV9mKzAUWq7XM0/oBFcJQ 0fqsFIfvJjHs51n0D6VpqrzJJ/RUI7/ZjFLBFvPtBjBquVDAArgNk7hiCWhzgp7PFmsp AMEQ== Received: by 10.60.7.200 with SMTP id l8mr11105949oea.52.1332098253445; Sun, 18 Mar 2012 12:17:33 -0700 (PDT) Received: from [10.0.1.6] (cpe-70-112-20-219.austin.res.rr.com. [70.112.20.219]) by mx.google.com with ESMTPS id w4sm905161obx.2.2012.03.18.12.17.31 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 18 Mar 2012 12:17:32 -0700 (PDT) References: In-Reply-To: Mime-Version: 1.0 (iPhone Mail 8G4) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <5B51A967-FCD8-475E-8DFB-A831B8E89350@gmail.com> Cc: "httpclient-users@hc.apache.org" X-Mailer: iPhone Mail (8G4) From: Alan Ho Subject: Re: Implementing Proxy Chaining in Apache HTTP Date: Sun, 18 Mar 2012 14:17:28 -0500 To: HttpClient User Discussion , Toby X-Virus-Checked: Checked by ClamAV on apache.org Hi Toby, I've implemented a statistics recorder that I'd be happy to share with you. W= e are planning to opensource the statistics recorder, but haven't got around= to it. Let me know if you would want to look at the code or get a demo. (or if anyo= ne wants to take a look) Regards, Alan Ho On Mar 17, 2012, at 7:27 AM, Toby wrote: > Hi Folks, >=20 > I posted a question on Stack Overflow (at > http://stackoverflow.com/questions/9698935/proxy-chaining-in-apache-http) > and it was suggested I ask here so here goes... >=20 > I'd like to send http messages through something that I can control (mainl= y > so that I can record statistics and stash the request/response along with > the headers for auditing etc). So far, I'm using LittleProxy as a proxy to= > do this but I'd like to be able to send the messages through say, a > corporate proxy before sending it onto my proxy. Hence I was looking at > proxy tunnelling with Apache HTTP. >=20 > I've found the source that says "Proxy chains are not supported." along > with a developer comment suggesting it can be done and where to start > looking. I'm happy to get stuck into the source and attempt to do so but > it'd be great if I can get a few pointers (especially around how to hook > any 'customisation' in). >=20 > oh, I'd be happy to be corrected if I am on the wrong track. I'm assuming > 'proxy tunnelling' is what I've tried to describe above and so is the righ= t > avenue... >=20 > I should say that I'm open to alternative ideas too, I had originally trie= d > to redirect all messages to a socket that I control, record the message > details then send on to the original port but I didn't get very far with > that. >=20 > Thanks for any pointers, > Toby --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org For additional commands, e-mail: httpclient-users-help@hc.apache.org