David Chandler's Journal of Java Web and Mobile Development

  • David M. Chandler

    Web app developer since 1994 and former Developer Advocate with Google now residing in Colorado. Besides tech, I enjoy landscape photography and share my work at ColoradoPhoto.gallery.

  • Subscribe

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 242 other followers

  • Sleepless Nights…

    June 2012
    S M T W T F S
    « May   Jul »
  • Blog Stats

    • 849,257 hits

A basic HTTP client for Android (and more)

Posted by David Chandler on June 12, 2012

TL;DR http://code.google.com/p/basic-http-client/

Last year, the Android team recommended the use of java.net.HttpURLConnection instead of Apache HttpClient for Gingerbread and up. Unfortunately, HttpURLConnection is a lower-level API, so now everyone has to do their own URL encoding, set MIME type application/x-www-form-urlencoded, read InputStream and ErrorStream, wrap with try/catch, finally close streams, etc.

Rather than write all that code one-off for each request, I’ve created a basic HTTP client which lets you easily

  • make GET, POST, PUT, and DELETE requests
  • make asynchronous requests with automatic retries and exponential backoff
  • customize requests using a RequestHandler
  • automatically wrap requests in an AsyncTask (Android-specific)

It has a very simple API, and the jar weighs in at only 40kB (basic) or 45kb (Android), including source. It is Android-independent by design, although Android developers will find it especially useful.

Basic usage

    // Example code to login to App Engine dev server
    public void loginDev(String userEmail) {
        BasicHttpClient httpClient = new BasicHttpClient("http://localhost:8888");
        ParameterMap params = httpClient.newParams()
                .add("continue", "/")
                .add("email", userEmail)
                .add("action", "Log In");
        httpClient.addHeader("someheader", "value");
        httpClient.setConnectionTimeout(2000); // 2s
        HttpResponse httpResponse = httpClient.post("/_ah/login", params);

    // Example code to log in to App Engine production app with an auth token
    // from Android's AccountManager
    public void loginProd(String authToken) {
        BasicHttpClient httpClient = new BasicHttpClient("http://localhost:8888");
        ParameterMap params = httpClient.newParams()
                .add("auth", authToken);
        HttpResponse httpResponse = httpClient.get("/_ah/login", params);

Make an asynchronous request

        AndroidHttpClient httpClient = new AndroidHttpClient("");
        ParameterMap params = httpClient.newParams()
                .add("continue", "/")
                .add("email", "test@example.com")
                .add("action", "Log In");
        httpClient.post("/_ah/login", params, new AsyncCallback() {
            public void onComplete(HttpResponse httpResponse) {
            public void onError(Exception e) {

To make an asynchronous request, you invoke the request methods (get, post, etc.) with an additional argument, an AsyncCallback, which can be easily implemented in an anonymous inner class as shown above. Here’s a quick tour of the various clients you can use.


BasicHttpClient has no Android dependencies so it can be used on any platform which provides java.net.HttpURLConnection. It offers a synchronous interface only via get, post, put, and delete methods. Note that there are two post methods, one for posting form data (a ParameterMap) and one for uploading content of any type you specify. If you prefer, you can make a new HttpGetRequest and execute() it instead of using the get() method. In fact, all the request methods do this under the covers.


AndroidHttpClient extends both AbstractHttpClient and AsyncHttpClient so it can used synchronously or asynchronously. Remember that you should not invoke the immediate (non-async) methods on the UI thread. Android will throw an exception if you do. Besides automatically wrapping requests in an AsyncTask via the async methods, AndroidHttpClient automatically includes the workaround for a major bug in HttpURLConnection in earlier versions of Android as discussed in the Android Developers blog post above.

Cookie management

AbstractHttpClient (the base class for everything) registers a default java.net.CookieManager that is used by all HttpURLConnection requests in your VM (= app on Android). The default CookieManager acts just like a browser, remembering cookies it receives and sending them on subsequent requests. You shouldn’t need to set or read cookie headers manually at all. In fact, you can’t. When the CookieManager is in use, it consumes the cookie headers.

Under the covers

AbstractHttpClient is the base client from which all the others flow. It implements a synchronous API and can be instantiated using an anonymous inner class if you just want the base functionality: new AbstractHttpClient() {}.

AsyncHttpClient adds an asynchronous API where each request method takes an extra callback argument. It is intended to be extended like AndroidHttpClient. Subclasses should provide a platform-specific wrapper for async requests. AndroidHttpClient provides an AsyncTask wrapper that AsyncHttpClient uses to make requests in the background.

BasicHttpClient and AndroidHttpClient both delegate the actual I/O to a BasicRequestHandler, which implements a simple request lifecycle (open, prepare, write, read, error). You can construct any of the clients with a custom RequestHandler. BasicRequestHandler is abstract so you can easily override only one method using an anonymous inner class. This is shown on the project home page. A common use for this may be to provide your own onError() method which determines whether a given error condition is recoverable for your application.


There are no automated tests yet because I haven’t made the effort to simulate connections, timeouts, etc. I have done considerable manual testing, however, of the async capabilities with retries. The basic recipe is as follows:

  • Try an async request to an unreachable IP address (say, or This lets you observe connection timeouts and retries.
  • Copy the SleepServlet in the test package to a Web project and add the servlet mapping in web.xml. Start the server and try an async request. This lets you observe read timeouts and retries.
  • Try an async request to a functioning URL and observe success.


The code is copiously commented with hopefully non-trivial observations about function and intended use. Planned enhancements include a MappingJsonClient which can take POJO arguments instead of raw bytes or Strings. Spring for Android already has a nice RestTemplate, but like Apache HttpClient, is fairly heavyweight on account of its configurability.


70 Responses to “A basic HTTP client for Android (and more)”

  1. jessedavidbrucewilson said

    I’m the author of the Android Developers’ Blog post. This is nice work!

    Does it enable the HTTP response cache on Android 4.0? Craig Andrews did a backport here:

    Also take a look at MockWebServer, which makes unit testing this kind of code easy.

  2. Thanks very much, Jesse. No response caching yet. I’ll look into it. Thanks for the pointers.

  3. Anatoly said

    what if someone develops an application for froyo and up, so according to the blog you mentioned in text, are we supposed to switch on algorithm depending on platform version?
    or we just have to deside what is more suitable for the app ( HttpURLConnection feautures or some kind of unknown, or known bugs of httpclient) ? What do you think?

    • If you’re writing code for Froyo and above, your best bet is HttpURLConnection. Just use the blog posts’ disableConnectionReuseIfNecessary() workaround to avoid Froyo-only bugs.

    • Hmmm, the blog post I referenced is conflicted. It recommends HttpURLConnection for Gingerbread and up, but elsewhere says “Prior to Froyo, HttpURLConnection had some frustrating bugs.” The worst bug pre-Froyo was presumably the one mentioned in that article, and I’ve included the workaround for it in my code, so you should be covered there. From peeking around StackOverflow, it looks like a lot of the older bugs in HttpURLConnection have to do with things like chunked input streaming that basic-http-client doesn’t use, anyway. But… I’ve only tested on ICS.

      Let me add that I think Apache HttpClient remains a solid all-around choice. I wrote basic-http-client mainly because I wanted something really lightweight with a really simple API. It’s not intended to be a one-size-fits-all HTTP client. I haven’t used buffered readers or writers or chunked input streaming and haven’t tested with large data at all. But it beats writing the same 20 lines of code over and over to use HttpURLConnection directly, especially with the AsyncTask wrapper.

      Should you wish to switch between HttpURLConnection and Apache based on Android version, the Spring for Android project does this automatically. The Spring RestTemplate is super easy.

  4. Besides Apache HttpClient, a couple other libraries of interest:

    Google HTTP Java Client is a solid, full-featured client written by some of my favorite Java programmers at Google and is Android-compatible.

    JAX-RS 2.0 Client API looks promising.

    I probably should have called this minimal-http-client because that’s really my intent. I do think the async calling mechanism is really cool (and haven’t seen it elsewhere). That’s no doubt the GWT programmer coming out in me.

  5. […] to have a look at their tutorial and how to set up a more stable client in your App. Also check David Chandler’s BasicHttpClient which he considers as simpler to use because it already implements all basic operations such as URL […]

  6. geezenslaw said

    Hi David, I created a new Android project using your LoginDev example in my Intellij and dropped in the jar. No unresolved references. All looked good except httpresponse returns NULL! No exceptions or logs to examine. I used my public blog url that I have in the past succesfully logged into using Apache HttpClient. Any ideas as how to debug this? Pleas advise, David.

    • Nothing in logcat? By default, you should see the request at INFO level.

      • geezenslaw said

        Hi David, pls excuse the top post but I insert a couple of Log.d’s:

        Log.d(TAG, params.get(“j_username”)); Log.d(TAG, params.get(“j_password”));

        The params seem to be satisfied correctly but yet don’t show up in the request URL.

        A mystery.


  7. geezenslaw said

    Hi David, I have tried the AndroidHttpClient example instead and it is working with the same params.

    I suspect the issue w/ the Basic client is running it on the main UI thread.

    Thanks for the nice API!

  8. geezenslaw said

    Hi David, I am not able to use ArrayAdapter for a ListView object inside of onComplete().

    The compile time complaint is: Cannot resolve constructor ‘ArrayAdapter'(com.turbomanage.httpclient.AsyncCallback, int, int, String[]) using for the context.

    If I try to use ArrayAdapter and ListView outside of the onComplete() the String[] array data is not available.

    Does it make sense to get onComplete() to return a String[] array?

    • David,

      It looks you’re trying to construct an ArrayAdapter with an AsyncCallback. Instead, onComplete() should call a method in your Activity and pass it the HttpResponse or response body. The Activity method can then create or update an ArrayAdapter.

      HTH, /dmc

  9. lindo said

    I use and contribute to https://github.com/loopj/android-async-http for all my http needs

  10. Hey Dave. We met at a meetup in NY in Sep. I help run the meetup group. You mentioned this project, which I finally tracked down. Just the kind of thing I’ve been looking for. I’ve had an open source project in a state of partial completion for a year or so. It facilitates offline editing and syncing for Android. One of the big problems was distinguishing between “hard” exceptions, and simple temporary network issues. I added an extension of the BasicHttpClient to better handle that. Result: problem (basically) solved. All future projects will include your http project. Seems crazy not to.

    If you get some free time, take a look at the offline sync bus and give feedback:


    The docs in the blog have horrible formatting. It was a copy/paste from confluence. Will edit given time. Had a 12 hour day at new client, so my tolerance for doc editing is at an all time low 😉

    Short intro. To enable offline data editing and sync, the project provides a “command bus”. Commands are abstract classes. The implementation is the “work” needed to be done, basically. The bus provides the serialization and proper ordering and management. Most sync we’ve done prior was “state based”. Set an “updated” flag on an entity. Simple, but problematic for a number of reasons. This project attempts to solve that problem.

    Its a hard “sell”. Its one of those things you don’t “get” until you need it, but its been in several of our projects to date, although the current state is far more robust than older ones.

    Anyway, dig the http project!

  11. Thanks a lot for this, David.
    When I try to implement your client, my app fails with:

    “Could not find class ‘java.net.CookieManager’, referenced from method com.turbomanage.httpclient.AbstractHttpClient.ensureCookieManager”

    What am I missing?

  12. humsuplow said

    I am not sure on this, but I am having some trouble with https secure request. How do we handle secure request?

    • I haven’t tested specifically with https. What happens if you put https://in the URL? Any clues in logcat?

      • zgzong said

        12-19 14:11:57.291: W/System.err(10303): java.net.SocketTimeoutException: Read timed out
        12-19 14:11:57.296: W/System.err(10303): at org.apache.harmony.xnet.provider.jsse.NativeCrypto.SSL_read(Native Method)
        12-19 14:11:57.296: W/System.err(10303): at org.apache.harmony.xnet.provider.jsse.OpenSSLSocketImpl$SSLInputStream.read(OpenSSLSocketImpl.java:671)
        12-19 14:11:57.296: W/System.err(10303): at libcore.io.Streams.readSingleByte(Streams.java:41)
        12-19 14:11:57.301: W/System.err(10303): at org.apache.harmony.xnet.provider.jsse.OpenSSLSocketImpl$SSLInputStream.read(OpenSSLSocketImpl.java:655)
        12-19 14:11:57.301: W/System.err(10303): at libcore.io.Streams.readAsciiLine(Streams.java:201)
        12-19 14:11:57.301: W/System.err(10303): at libcore.net.http.HttpEngine.readResponseHeaders(HttpEngine.java:544)
        12-19 14:11:57.301: W/System.err(10303): at libcore.net.http.HttpEngine.readResponse(HttpEngine.java:784)
        12-19 14:11:57.306: W/System.err(10303): at libcore.net.http.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:274)
        12-19 14:11:57.306: W/System.err(10303): at libcore.net.http.HttpURLConnectionImpl.getResponseCode(HttpURLConnectionImpl.java:479)
        12-19 14:11:57.311: W/System.err(10303): at libcore.net.http.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:133)
        12-19 14:11:57.311: W/System.err(10303): at com.turbomanage.httpclient.AbstractHttpClient.writeOutputStream(AbstractHttpClient.java:311)
        12-19 14:11:57.311: W/System.err(10303): at com.turbomanage.httpclient.AbstractHttpClient.doHttpMethod(AbstractHttpClient.java:224)
        12-19 14:11:57.311: W/System.err(10303): at com.turbomanage.httpclient.AsyncHttpClient.tryMany(AsyncHttpClient.java:185)
        12-19 14:11:57.316: W/System.err(10303): at com.turbomanage.httpclient.android.DoHttpRequestTask.doInBackground(DoHttpRequestTask.java:40)
        12-19 14:11:57.316: W/System.err(10303): at com.turbomanage.httpclient.android.DoHttpRequestTask.doInBackground(DoHttpRequestTask.java:1)
        12-19 14:11:57.316: W/System.err(10303): at android.os.AsyncTask$2.call(AsyncTask.java:264)
        12-19 14:11:57.321: W/System.err(10303): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
        12-19 14:11:57.321: W/System.err(10303): at java.util.concurrent.FutureTask.run(FutureTask.java:137)
        12-19 14:11:57.321: W/System.err(10303): at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:208)
        12-19 14:11:57.321: W/System.err(10303): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
        12-19 14:11:57.326: W/System.err(10303): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
        12-19 14:11:57.326: W/System.err(10303): at java.lang.Thread.run(Thread.java:856)

      • Timeouts are not uncommon on the Web. If you think it’s a bug in basic-http-client, please note the version and file in the issue tracker.

    • zgzong said

      It seems doesn’t support post json raw data. “application/json”

      • You can use post(String path, String contentType, byte[] data) to post raw content of any type.

      • zgzong said

        thanks for your quick reply. It works fine and read time out issue seems caused by slow internet connection. I will keep you informed when I found out what caused that timeout issue.

  13. Janna said

    AnroidHttpClient is missing a ‘d’.

  14. Benny Khoo said

    Hi David,

    This is a beautifully designed framework for using HttpUrlConnection. I am looking forward to incorporate it in my app. I still find that there are quite some coding to post upload file request. I am wondering how this can be done using this framework.

  15. Mohd said

    Hi David..
    I am new to android development and implementing your framework for my final year project. I am trying to post json object and calling AsyncTask on the same time but cant figure up which post class should i use.

  16. Federico said

    Hello Mr. David Chandler,
    I have some problem using this library. When I use the post method – in particular, the post method with the async callback – of an AndroidHttpClient object, it seems that the method startActivity(new Intent(FromActivity.this, ToActivity.class)) doesn’t work. The connection works perfectly, only the method startActivity within the onComplete method doesn’t work. This is my code snippet

    AndroidHttpClient request = new AndroidHttpClient(
    ParameterMap paramMap = new ParameterMap();
    paramMap.add(“DATA”, json_req);

    request.post(“”, paramMap, new AsyncCallback() {

    public void onComplete(HttpResponse httpResponse) {
    try {
    JSONObject resp = JsonCR2.readRequest(response.getBodyAsString());
    if (resp.get(“response”).toString().equalsIgnoreCase(“success”)) {

    startActivity(new Intent(this, IndexActivity.class));
    } else {
    //some error
    } catch (ParseException e) {
    } catch (Exception e) {


    Can you explain me where I wrong? Thanks.

    • Hi Federico, it should be possible to start an Activity from the callback since the callback’s onComplete() method is invoked within the AsyncTask’s onPostExecute() method, which runs on the UI thread. I suspect the issue has to do with passing the correct Context. In your example, is this code located in an Activity? Is any exception being thrown?

      • Federico said

        Yes, the code is within the method loginService from the main activity of the project. This method runs when a button is clicked. It seems that no exceptions are thrown

      • You might try getApplicationContext().startActivity(). Failing that, you could try using a Handler to communicate back to the parent Activity instead of invoking startActivity() directly. stORM is just using an AsyncTask internally, so anything you can do ordinarily within onPostExecute() should be possible, but the stORM AsyncTask does not have a reference to the Context, and I wonder if that’s the issue. There are a number of questions on SO about starting an Activity within an AsyncTask, and it seems one solution is to provide the application context to the AsyncTask in a constructor. To do that with stORM, you could subclass DoHttpRequestTask and call it the same way that the post() method does.

        On Tue, Jan 15, 2013 at 11:07 AM, TurboManage

      • Federico said

        Hi Mr. David Chandler, my problem is finally resolved. There were several problems related to other classes that I use; once solved these problems, the application works as expected. Thank you for the help.

  17. Hi,

    i have a question on uploading images (byte arrays) with the BasicHttpClient.
    Before i used the DefaultHttpClient with multipart like this:

    final HttpClient httpClient = new DefaultHttpClient();
    final HttpPost httpPostReq = new HttpPost(ApplicationConfig.SCREENSHOT_UPLOAD_URL);
    final MultipartEntity mimeEntity = new MultipartEntity(HttpMultipartMode.BROWSER_COMPATIBLE);
    mimeEntity.addPart(“image”, new ByteArrayBody(imageData, params[0].getName()));
    final HttpResponse response = httpClient.execute(httpPostReq);

    How can i achieve this kind of multipart upload with yout very excellent BasicHttpCLlent ?

    Thanks and best regards

    • Hi Sebastian,

      You can use post(String path, String contentType, byte[] data) to post raw bytes of any content type you specify; however, basic-http-client doesn’t have any abstraction specifically for multipart entities. I suspect that you could extend BasicHttpClient’s HttpPost and copy MultipartEntity from another HTTP client library like Apache. Then you could invoke BasicHttpClient.execute(YourCustomPost post).

  18. michel said

    Hi, tnk for the android client 🙂 but i have a problem :
    Could not find method com.turbomanage.httpclient.android.AndroidHttpClient.ensureCookieManager, referenced from method com.turbomanage.httpclient.android.AndroidHttpClient.
    VFY: unable to resolve static method 3169: Lcom/turbomanage/httpclient/android/AndroidHttpClient;.ensureCookieManager ()V
    why this?
    i was building on Android 2.2 (API 8)

    • Hi Michel, see https://code.google.com/p/basic-http-client/issues/detail?id=8. This has been fixed, but be aware that there is no CookieManager prior to Gingerbread (2.3) so it will compile but won’t automatically manage cookies.

      • michel said

        Hi, yes i read iusse 8 and infact i use the 0.88 version, and with android 2.2 work (the output is ok) even if I get the warning, but with android 2.3+ i have this error:

        03-23 11:31:59.344: E/AndroidRuntime(780): FATAL EXCEPTION: main
        03-23 11:31:59.344: E/AndroidRuntime(780): java.lang.ExceptionInInitializerError
        03-23 11:31:59.344: E/AndroidRuntime(780): at com.example.helloworld.MainActivity.onCreate(MainActivity.java:32)
        03-23 11:31:59.344: E/AndroidRuntime(780): at android.app.Activity.performCreate(Activity.java:5104)
        03-23 11:31:59.344: E/AndroidRuntime(780): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1080)
        03-23 11:31:59.344: E/AndroidRuntime(780): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2144)
        03-23 11:31:59.344: E/AndroidRuntime(780): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2230)
        03-23 11:31:59.344: E/AndroidRuntime(780): at android.app.ActivityThread.access$600(ActivityThread.java:141)
        03-23 11:31:59.344: E/AndroidRuntime(780): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1234)
        03-23 11:31:59.344: E/AndroidRuntime(780): at android.os.Handler.dispatchMessage(Handler.java:99)
        03-23 11:31:59.344: E/AndroidRuntime(780): at android.os.Looper.loop(Looper.java:137)
        03-23 11:31:59.344: E/AndroidRuntime(780): at android.app.ActivityThread.main(ActivityThread.java:5041)
        03-23 11:31:59.344: E/AndroidRuntime(780): at java.lang.reflect.Method.invokeNative(Native Method)
        03-23 11:31:59.344: E/AndroidRuntime(780): at java.lang.reflect.Method.invoke(Method.java:511)
        03-23 11:31:59.344: E/AndroidRuntime(780): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
        03-23 11:31:59.344: E/AndroidRuntime(780): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
        03-23 11:31:59.344: E/AndroidRuntime(780): at dalvik.system.NativeStart.main(Native Method)
        03-23 11:31:59.344: E/AndroidRuntime(780): Caused by: java.lang.NoSuchMethodError: com.turbomanage.httpclient.android.AndroidHttpClient.ensureCookieManager
        03-23 11:31:59.344: E/AndroidRuntime(780): at com.turbomanage.httpclient.android.AndroidHttpClient.(AndroidHttpClient.java:49)
        03-23 11:31:59.344: E/AndroidRuntime(780): … 15 more

        java.lang.NoSuchMethodError and not class not found.
        static {
        // See http://code.google.com/p/basic-http-client/issues/detail?id=8
        if (Build.VERSION.SDK_INT > 8)

        I do not understand, it would find the method ensureCookieManager() in com.turbomanage.httpclient.android.AndroidHttpClient class?

      • Please comment on issue 8 and I’ll take a look.

  19. Juan Jose Alonso (@JJoseAlonso) said

    Hi ! fantastic library, but im having troubles trying to put to a URL.

    I need to send a multipart form data to the server, (usually strings values and keys). But the data type is byte[]… How i can send this fields key-value in byte[] type? What is the way?


    • Hi, if you haven’t worked it out yet I leave you the answer to this question with an example:

      AndroidHttpClient httpClient = new AndroidHttpClient(“”);

      ParameterMap params = httpClient.newParams()
      .add(“password”, “12345”);

      httpClient.put(“route”, “text/html; charset=UTF-8”, params.urlEncodedBytes(), callback);

      I used it the same way as Post but I do “urlEncodedBytes()” to my params var, in order to convert my ParameterMap var to a Byte [] type.

  20. SreePreeti said

    can you please explain about the IP addresses. because i tried my computer’s IP and android IP. but my application crashes.

  21. Ernie said

    Thanks a lot for this library, simplifies my life!

    One question: Are instances of AndroidHttpClient thread-safe?

    I.e. can I just create one singleton instance of AndroidHttpClient with a given URL and use it globally in all threads of my Application?


  22. Ernie said

    Great, thanks a bunch!

  23. devilmac said

    Hi David Chandler,

    I have a request: is it possible to have a method in the HttpResponse class that disable logging of its content?
    Because now in my log there are too much log’s data when I get informations from the net 🙂


    • Sure, go ahead and add this to the issue tracker. In the mean time, you can replace the default ConsoleRequestLogger with your own implementation and supply it to BasicRequestHandler using the constructor that takes a RequestLogger. There’s an example of customizing BasicRequestHandler in the section Understanding the Code on the project home page.

  24. Neurohobbit said

    I’m trying to do:

    AndroidHttpClient httpClient = new AndroidHttpClient(“https://api.vlct.by”);
    ParameterMap params = httpClient.newParams().add(“session_id”, “3968b8ff93eff03b21016efb9c63fb4e”);
    httpClient.post(“/users/info”, params, new AsyncCallback() {
    public void onComplete(HttpResponse httpResponse) {

    public void onError(Exception e) {

    But I do have problems:
    com.turbomanage.httpclient.HttpRequestException: java.io.IOException: Hostname ‘api.vlct.by’ was not verified

    What I`m doing wrong?

  25. jul said

    How do you catche timeout error with AndroidHttpClient? (from doc: onError is “Timeout exceptions are considered recoverable and won’t trigger this call.”)

  26. Jose Casas said

    Hi David,

    Thanks a lot for this library. I’m currently using it on my first android app, but somtimes, I´m having the following timeout exception:

    [message] com.turbomanage.httpclient.HttpRequestException: java.net.SocketTimeoutException: failed to connect to [my url] after 1000ms.

    I’ve set the client to do 8 retrys and to have a timeout of 5000ms:


    Also, I’m checking for the active network to be connected before calling the get method (asyncronously).

    Why do I get a message showing a timeout after 1000ms if the client is set to 5000ms?, I’m setting this well?

  27. Spencer Morris said

    How do I disable retries? The setMaxRetries(int) method doesn’t allow ‘0’ as the integer (requires 1-18).

  28. Alex said

    can I have an example how I can upload a file with some other parameter at the same time to server side? my php…thanks,

  29. chitgoks said

    hi question. can the basichttpclient be set a max amount of bytea to dowblpad from stream? then cut off after total max bytes is reached?

    • This is not currently not a way to do this, sorry.

      • chitgoks said

        ok thank you. how about an onProgress or something while getting the inputstream to show the progress? sorry im away from pc right now, cant check your code i thought id ask.

        regardless, your lib is great. at least i can access urls as fast as when it is run as an application. i had probs with httpurlconnection and defaulthttpclient timing out at some point.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: