From: Jack <gi...@ti...> - 2005-09-19 09:48:46
|
SourceForge.net <noreply <at> sourceforge.net> writes: > >Comment By: Greg Wilkins (gregwilkins) > Date: 2005-09-16 22:30 > > The fix for this is to check for the proxy system properties > and if > one exists, the out going connection should be made to it and a > CONNECT request sent, a response read and then the handling > continue as normal. > This is what class ChainedProxyHandler does ;) I don't know if you had time to look at it, yet. Maybe you don't want a new class to provide such a feature, instead of integrating it directly into ProxyHandler? I'd gladly rearrange my code to fit at best your requirements, just let me know :) cheers |
From: Greg W. <gr...@mo...> - 2005-10-02 23:21:25
|
Jack wrote: > This is what class ChainedProxyHandler does ;) > I don't know if you had time to look at it, yet. Maybe you don't want a new > class to provide such a feature, instead of integrating it directly into > ProxyHandler? > I'd gladly rearrange my code to fit at best your requirements, just let me > know :) I've merged the latest patch provided with my working copy and am just searching for the hour I need to understand and test it before committing.... sorry yet again for the slow response.... cheers |