On Mon, 2012-03-19 at 07:00 +0000, Toby wrote: > Hi folks, > > Alan, I'd certainly like to take a look at what you did. Did you use a > similar approach or something completely different. > > Thanks Oleg too, i plan to sit down and have a go at implementing something. > Do you suggest cloning the source and working directly with it or do you > think I can extend it working with just the binaries? >
It might be possible just override DefaultRequestDirector#createTunnelToProxy without having to make modification to other parts of the class, but I guess it is going to be easier to clone the project at github and hack up a working prototype without constraints of backward compatibility as the first step. Oleg > Thanks again, > Toby > > > On 18 Mar 2012, at 19:17, Alan Ho <[email protected]> wrote: > > > Hi Toby, > > > > I've implemented a statistics recorder that I'd be happy to share with you. > > We 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 > > anyone wants to take a look) > > > > Regards, > > Alan Ho > > > > On Mar 17, 2012, at 7:27 AM, Toby <[email protected]> wrote: > > > >> Hi Folks, > >> > >> 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... > >> > >> I'd like to send http messages through something that I can control (mainly > >> 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. > >> > >> 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). > >> > >> 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 right > >> avenue... > >> > >> I should say that I'm open to alternative ideas too, I had originally tried > >> 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. > >> > >> Thanks for any pointers, > >> Toby > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
