| commit | f47a061928a8b9ab657a9164bae31029a5829082 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 11 May 2008 21:01:35 +0000 (11 17:01 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 11 May 2008 21:13:19 +0000 (11 17:13 -0400) | ||
| tree | 345b62d29eb7f7f643b24c5a365472be40400da8 | treesnapshot (tar.gz zip) |
| parent | 12eaf0cd19d0398a972627aa226706b99f63d183 | commitdiff |
Use the Eclipse network proxy configuration for HTTP connections
Eclipse provides support for proxy configuration within the workbench,
but this information is not pushed down into the J2SE library itself
so our naive use of java.net.URL to open connections cannot get to the
proxy information.
By installing our own ProxySelector and Authenticator implementations
we can push the Eclipse proxy information down into the J2SE library
and make use of it during transport operations.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Eclipse provides support for proxy configuration within the workbench,
but this information is not pushed down into the J2SE library itself
so our naive use of java.net.URL to open connections cannot get to the
proxy information.
By installing our own ProxySelector and Authenticator implementations
we can push the Eclipse proxy information down into the J2SE library
and make use of it during transport operations.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>