After asking some questions at JavaOne, I was told I could get more complete answers here. My question is about authentication mechanisms and support for native network configurations.
Is the new client going to have access to the system proxy configuration settings? It would be nice if there was a natural way to use the system keystores as well. This is a real pain-point for our rollouts. People log in to their computers (generally Windows and Macs for our users) and, if they can access the web in their browser, they think that our application should be able to as well. However, we have to ask them to try to duplicate their settings in our application. Many times this involves an authenticating proxy. Is this possible to do with the new HttpClient? Is it possible without jumping through a lot of hoops? (Currently we are using the Apache HttpClient library, which has hooks where we can do some proxy authentication.) Thanks, Mark Disclaimer: The opinions provided herein do not necessarily state or reflect those of Donnell Systems, Inc.(DSI). DSI makes no warranty for and assumes no legal liability or responsibility for the posting.
