New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP and SOCKS proxy support #87
Comments
From fli...@gmail.com on August 10, 2012 06:51:35 still not resolved?! |
From rmis...@google.com on August 10, 2012 06:53:37 Labels: Milestone-Version1.12.0 |
From yan...@google.com on September 26, 2012 05:15:59 Labels: -Milestone-Version1.12.0 |
From yan...@google.com on November 10, 2012 05:00:14 Owner: ngmic...@google.com |
From yan...@google.com on December 14, 2012 08:19:40 This adds HTTP and SOCKS proxy support for NetHttpTransport, as well as HTTP proxy support to ApacheHttpTransport: https://codereview.appspot.com/6944046/ SOCKS support for ApacheHttpTransport is now moved over to: https://code.google.com/p/google-http-java-client/issues/detail?id=174 Status: Started |
From yan...@google.com on December 16, 2012 07:07:55 Status: Fixed |
From yan...@google.com on March 28, 2013 20:42:03 Owner: yan...@google.com |
From yan...@google.com on April 13, 2012 22:05:14
External references, such as a standards document, or specification? HTTP proxy RFC: http://tools.ietf.org/html/rfc2068#section-8.1.3 SOCKS proxy RFC: http://tools.ietf.org/html/rfc1928 https://code.google.com/r/viallyichb-google-api-proxy-support/ Java environments (e.g. Java 6, Android 2.3, App Engine, or All)? All Please describe the feature requested. Add support for HTTP and SOCKS proxy. This should be implemented in NetHttpTransport and ApacheHttpTransport. I'm not sure if it makes sense for UrlFetchTransport.
For reference, an implementation based on Apache HTTP transport was implemented above by a contributor over a year ago based on an older version of the client library.
Original issue: http://code.google.com/p/google-http-java-client/issues/detail?id=87
The text was updated successfully, but these errors were encountered: