Hi Oleg, > The fact that protocol interceptors do not get called when executing > CONNECT methods is clearly a bug. Please open a JIRA issue for this > problem. Preemptive authentication should work for tunneled connections > exactly the same way for the direct ones.
Have opened an issue for this on JIRA. >This is intentional. Execution of potentially blocking operations such >as UI dialogs inside the main request execution loops is a bad idea, >because such blocking operations will prevent the connection from being >returned to the connection manager for a long period of time. I've ended up subclassing the DefaultRequestDirector as I want some automated handling of this but I'm not sure if there are any issues in my implementation. Could you have a quick look and see if there's anything I've failed to take into account? Thanks! http://gemz.org/temp/httpclient/InteractiveAuthenticationRequestDirector.java http://gemz.org/temp/httpclient/InteractiveAuthenticationHandler.java http://gemz.org/temp/httpclient/InteractiveProxyAuthenticationHandler.java >> Hope this helps You've been a great help and I'm impressed with the design of the library. Thanks! Regards, Justin Tay -- View this message in context: http://www.nabble.com/Proxy-Authentication-tp18813008p18841433.html Sent from the HttpClient-User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
