You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Phillip Wang (Created) (JIRA)" <ji...@apache.org> on 2012/01/12 21:18:39 UTC
[jira] [Created] (HTTPASYNC-11) Default Async HTTP Client Fails to
get response for an Digest Authenticated HTTP 1.0 style connection
Default Async HTTP Client Fails to get response for an Digest Authenticated HTTP 1.0 style connection
-----------------------------------------------------------------------------------------------------
Key: HTTPASYNC-11
URL: https://issues.apache.org/jira/browse/HTTPASYNC-11
Project: HttpComponents HttpAsyncClient
Issue Type: Bug
Affects Versions: 4.0-alpha3
Environment: Ubuntu 10.4.3, Java 6
Reporter: Phillip Wang
I'm trying to use the HTTP Async client v4.0 alpha 3 to communicate with a HTTP v1.0-style server with Basic Digest authentication. I started with the basic example "Asynchronous HTTP exchange", and updated the first couple lines to this:
DefaultHttpAsyncClient httpclient = new DefaultHttpAsyncClient();
httpclient.getCredentialsProvider().setCredentials(
new AuthScope("localhost", 8080),
new UsernamePasswordCredentials("super", "super1"));
The server actually returns in the response HTTP 1.1 but includes "Connection: close" in the response header. Right after the response is done sending, the server closes the connection. This is a wireshark capture of the transaction:
GET / HTTP/1.1
Host: localhost:8080
Connection: Keep-Alive
User-Agent: Apache-HttpAsyncClient/4.0-alpha3 (java 1.5)
HTTP/1.1 401 Unauthorized
Content-Type: application/json
Connection: close
WWW-Authenticate: Digest realm="@127.0.0.1", qop="auth", nonce="44", opaque="deadbeef"
Transfer-Encoding: chunked
4b
{"status":{"code":401,"commandResult":1,"msg":"Unauthorized.","query":"/"}}
0
When I run the modified example, the future.get() call returns with null, and the program errors out on a null exception (due to the response.getStatusLine()).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Commented] (HTTPASYNC-11) Default Async HTTP Client Fails
to get response for an Digest Authenticated HTTP 1.0 style connection
Posted by "Phillip Wang (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185822#comment-13185822 ]
Phillip Wang commented on HTTPASYNC-11:
---------------------------------------
Thanks for the ultra quick turnaround! I really appreciate it.
I picked up the latest trunk in httpasyncclient and httpcore and try to use it in my project, but I got link errors on packages like org.apache.http.impl.nio.DefaultClientIODispatch. It looks like it was a deprecated package, and was remove in the trunk. The build/test for httpasyncclient seems to be against the older libraries, so the latest trunk of both httpasyncclient and httpcore doesn't link correctly for me to test (httpasyncclient is linked against httpcore 4.2 alpha 2?). Is it possible that it's an operator error on my part?
> Default Async HTTP Client Fails to get response for an Digest Authenticated HTTP 1.0 style connection
> -----------------------------------------------------------------------------------------------------
>
> Key: HTTPASYNC-11
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-11
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-alpha3
> Environment: Ubuntu 10.4.3, Java 6
> Reporter: Phillip Wang
> Fix For: 4.0-alpha4
>
> Attachments: nullresponse
>
>
> I'm trying to use the HTTP Async client v4.0 alpha 3 to communicate with a HTTP v1.0-style server with Basic Digest authentication. I started with the basic example "Asynchronous HTTP exchange", and updated the first couple lines to this:
> DefaultHttpAsyncClient httpclient = new DefaultHttpAsyncClient();
> httpclient.getCredentialsProvider().setCredentials(
> new AuthScope("localhost", 8080),
> new UsernamePasswordCredentials("super", "super1"));
> The server actually returns in the response HTTP 1.1 but includes "Connection: close" in the response header. Right after the response is done sending, the server closes the connection. This is a wireshark capture of the transaction:
> GET / HTTP/1.1
> Host: localhost:8080
> Connection: Keep-Alive
> User-Agent: Apache-HttpAsyncClient/4.0-alpha3 (java 1.5)
> HTTP/1.1 401 Unauthorized
> Content-Type: application/json
> Connection: close
> WWW-Authenticate: Digest realm="@127.0.0.1", qop="auth", nonce="44", opaque="deadbeef"
> Transfer-Encoding: chunked
> 4b
> {"status":{"code":401,"commandResult":1,"msg":"Unauthorized.","query":"/"}}
> 0
> When I run the modified example, the future.get() call returns with null, and the program errors out on a null exception (due to the response.getStatusLine()).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Updated] (HTTPASYNC-11) Default Async HTTP Client Fails to
get response for an Digest Authenticated HTTP 1.0 style connection
Posted by "Phillip Wang (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phillip Wang updated HTTPASYNC-11:
----------------------------------
Attachment: nullresponse
This is the log4j wire/context log
> Default Async HTTP Client Fails to get response for an Digest Authenticated HTTP 1.0 style connection
> -----------------------------------------------------------------------------------------------------
>
> Key: HTTPASYNC-11
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-11
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-alpha3
> Environment: Ubuntu 10.4.3, Java 6
> Reporter: Phillip Wang
> Attachments: nullresponse
>
>
> I'm trying to use the HTTP Async client v4.0 alpha 3 to communicate with a HTTP v1.0-style server with Basic Digest authentication. I started with the basic example "Asynchronous HTTP exchange", and updated the first couple lines to this:
> DefaultHttpAsyncClient httpclient = new DefaultHttpAsyncClient();
> httpclient.getCredentialsProvider().setCredentials(
> new AuthScope("localhost", 8080),
> new UsernamePasswordCredentials("super", "super1"));
> The server actually returns in the response HTTP 1.1 but includes "Connection: close" in the response header. Right after the response is done sending, the server closes the connection. This is a wireshark capture of the transaction:
> GET / HTTP/1.1
> Host: localhost:8080
> Connection: Keep-Alive
> User-Agent: Apache-HttpAsyncClient/4.0-alpha3 (java 1.5)
> HTTP/1.1 401 Unauthorized
> Content-Type: application/json
> Connection: close
> WWW-Authenticate: Digest realm="@127.0.0.1", qop="auth", nonce="44", opaque="deadbeef"
> Transfer-Encoding: chunked
> 4b
> {"status":{"code":401,"commandResult":1,"msg":"Unauthorized.","query":"/"}}
> 0
> When I run the modified example, the future.get() call returns with null, and the program errors out on a null exception (due to the response.getStatusLine()).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Resolved] (HTTPASYNC-11) Default Async HTTP Client Fails to
get response for an Digest Authenticated HTTP 1.0 style connection
Posted by "Oleg Kalnichevski (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPASYNC-11.
----------------------------------------
Resolution: Fixed
I committed a fix for the bug to SVN trunk. Could you please retest your application with the latest SVN snapshot and re-open the issue if the problem still persists.
Oleg
> Default Async HTTP Client Fails to get response for an Digest Authenticated HTTP 1.0 style connection
> -----------------------------------------------------------------------------------------------------
>
> Key: HTTPASYNC-11
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-11
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-alpha3
> Environment: Ubuntu 10.4.3, Java 6
> Reporter: Phillip Wang
> Fix For: 4.0-alpha4
>
> Attachments: nullresponse
>
>
> I'm trying to use the HTTP Async client v4.0 alpha 3 to communicate with a HTTP v1.0-style server with Basic Digest authentication. I started with the basic example "Asynchronous HTTP exchange", and updated the first couple lines to this:
> DefaultHttpAsyncClient httpclient = new DefaultHttpAsyncClient();
> httpclient.getCredentialsProvider().setCredentials(
> new AuthScope("localhost", 8080),
> new UsernamePasswordCredentials("super", "super1"));
> The server actually returns in the response HTTP 1.1 but includes "Connection: close" in the response header. Right after the response is done sending, the server closes the connection. This is a wireshark capture of the transaction:
> GET / HTTP/1.1
> Host: localhost:8080
> Connection: Keep-Alive
> User-Agent: Apache-HttpAsyncClient/4.0-alpha3 (java 1.5)
> HTTP/1.1 401 Unauthorized
> Content-Type: application/json
> Connection: close
> WWW-Authenticate: Digest realm="@127.0.0.1", qop="auth", nonce="44", opaque="deadbeef"
> Transfer-Encoding: chunked
> 4b
> {"status":{"code":401,"commandResult":1,"msg":"Unauthorized.","query":"/"}}
> 0
> When I run the modified example, the future.get() call returns with null, and the program errors out on a null exception (due to the response.getStatusLine()).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Commented] (HTTPASYNC-11) Default Async HTTP Client Fails
to get response for an Digest Authenticated HTTP 1.0 style connection
Posted by "Oleg Kalnichevski (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185845#comment-13185845 ]
Oleg Kalnichevski commented on HTTPASYNC-11:
--------------------------------------------
HttpAsyncClient trunk depends on HttpCore 4.2-alpha2. There have been API breaking changes in HttpCore trunk since 4.2-alpha2. Just revert back to HttpCore 4.2-alpha2.
Oleg
> Default Async HTTP Client Fails to get response for an Digest Authenticated HTTP 1.0 style connection
> -----------------------------------------------------------------------------------------------------
>
> Key: HTTPASYNC-11
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-11
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-alpha3
> Environment: Ubuntu 10.4.3, Java 6
> Reporter: Phillip Wang
> Fix For: 4.0-alpha4
>
> Attachments: nullresponse
>
>
> I'm trying to use the HTTP Async client v4.0 alpha 3 to communicate with a HTTP v1.0-style server with Basic Digest authentication. I started with the basic example "Asynchronous HTTP exchange", and updated the first couple lines to this:
> DefaultHttpAsyncClient httpclient = new DefaultHttpAsyncClient();
> httpclient.getCredentialsProvider().setCredentials(
> new AuthScope("localhost", 8080),
> new UsernamePasswordCredentials("super", "super1"));
> The server actually returns in the response HTTP 1.1 but includes "Connection: close" in the response header. Right after the response is done sending, the server closes the connection. This is a wireshark capture of the transaction:
> GET / HTTP/1.1
> Host: localhost:8080
> Connection: Keep-Alive
> User-Agent: Apache-HttpAsyncClient/4.0-alpha3 (java 1.5)
> HTTP/1.1 401 Unauthorized
> Content-Type: application/json
> Connection: close
> WWW-Authenticate: Digest realm="@127.0.0.1", qop="auth", nonce="44", opaque="deadbeef"
> Transfer-Encoding: chunked
> 4b
> {"status":{"code":401,"commandResult":1,"msg":"Unauthorized.","query":"/"}}
> 0
> When I run the modified example, the future.get() call returns with null, and the program errors out on a null exception (due to the response.getStatusLine()).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Updated] (HTTPASYNC-11) Default Async HTTP Client Fails to
get response for an Digest Authenticated HTTP 1.0 style connection
Posted by "Oleg Kalnichevski (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski updated HTTPASYNC-11:
---------------------------------------
Fix Version/s: 4.0-alpha4
I can confirm the problem is caused by a bug in HttpAsyncClient.
Oleg
> Default Async HTTP Client Fails to get response for an Digest Authenticated HTTP 1.0 style connection
> -----------------------------------------------------------------------------------------------------
>
> Key: HTTPASYNC-11
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-11
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-alpha3
> Environment: Ubuntu 10.4.3, Java 6
> Reporter: Phillip Wang
> Fix For: 4.0-alpha4
>
> Attachments: nullresponse
>
>
> I'm trying to use the HTTP Async client v4.0 alpha 3 to communicate with a HTTP v1.0-style server with Basic Digest authentication. I started with the basic example "Asynchronous HTTP exchange", and updated the first couple lines to this:
> DefaultHttpAsyncClient httpclient = new DefaultHttpAsyncClient();
> httpclient.getCredentialsProvider().setCredentials(
> new AuthScope("localhost", 8080),
> new UsernamePasswordCredentials("super", "super1"));
> The server actually returns in the response HTTP 1.1 but includes "Connection: close" in the response header. Right after the response is done sending, the server closes the connection. This is a wireshark capture of the transaction:
> GET / HTTP/1.1
> Host: localhost:8080
> Connection: Keep-Alive
> User-Agent: Apache-HttpAsyncClient/4.0-alpha3 (java 1.5)
> HTTP/1.1 401 Unauthorized
> Content-Type: application/json
> Connection: close
> WWW-Authenticate: Digest realm="@127.0.0.1", qop="auth", nonce="44", opaque="deadbeef"
> Transfer-Encoding: chunked
> 4b
> {"status":{"code":401,"commandResult":1,"msg":"Unauthorized.","query":"/"}}
> 0
> When I run the modified example, the future.get() call returns with null, and the program errors out on a null exception (due to the response.getStatusLine()).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Commented] (HTTPASYNC-11) Default Async HTTP Client Fails
to get response for an Digest Authenticated HTTP 1.0 style connection
Posted by "Oleg Kalnichevski (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185218#comment-13185218 ]
Oleg Kalnichevski commented on HTTPASYNC-11:
--------------------------------------------
Please generate a wire / context log of the session as described here [1] and attach the log to the issue.
Oleg
[1] http://hc.apache.org/httpcomponents-client-ga/logging.html
> Default Async HTTP Client Fails to get response for an Digest Authenticated HTTP 1.0 style connection
> -----------------------------------------------------------------------------------------------------
>
> Key: HTTPASYNC-11
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-11
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-alpha3
> Environment: Ubuntu 10.4.3, Java 6
> Reporter: Phillip Wang
>
> I'm trying to use the HTTP Async client v4.0 alpha 3 to communicate with a HTTP v1.0-style server with Basic Digest authentication. I started with the basic example "Asynchronous HTTP exchange", and updated the first couple lines to this:
> DefaultHttpAsyncClient httpclient = new DefaultHttpAsyncClient();
> httpclient.getCredentialsProvider().setCredentials(
> new AuthScope("localhost", 8080),
> new UsernamePasswordCredentials("super", "super1"));
> The server actually returns in the response HTTP 1.1 but includes "Connection: close" in the response header. Right after the response is done sending, the server closes the connection. This is a wireshark capture of the transaction:
> GET / HTTP/1.1
> Host: localhost:8080
> Connection: Keep-Alive
> User-Agent: Apache-HttpAsyncClient/4.0-alpha3 (java 1.5)
> HTTP/1.1 401 Unauthorized
> Content-Type: application/json
> Connection: close
> WWW-Authenticate: Digest realm="@127.0.0.1", qop="auth", nonce="44", opaque="deadbeef"
> Transfer-Encoding: chunked
> 4b
> {"status":{"code":401,"commandResult":1,"msg":"Unauthorized.","query":"/"}}
> 0
> When I run the modified example, the future.get() call returns with null, and the program errors out on a null exception (due to the response.getStatusLine()).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Commented] (HTTPASYNC-11) Default Async HTTP Client Fails
to get response for an Digest Authenticated HTTP 1.0 style connection
Posted by "Phillip Wang (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185854#comment-13185854 ]
Phillip Wang commented on HTTPASYNC-11:
---------------------------------------
That seems to fixed the problem. I will use the modified library in my stress test to see if anything else pops up there. Thanks!
> Default Async HTTP Client Fails to get response for an Digest Authenticated HTTP 1.0 style connection
> -----------------------------------------------------------------------------------------------------
>
> Key: HTTPASYNC-11
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-11
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-alpha3
> Environment: Ubuntu 10.4.3, Java 6
> Reporter: Phillip Wang
> Fix For: 4.0-alpha4
>
> Attachments: nullresponse
>
>
> I'm trying to use the HTTP Async client v4.0 alpha 3 to communicate with a HTTP v1.0-style server with Basic Digest authentication. I started with the basic example "Asynchronous HTTP exchange", and updated the first couple lines to this:
> DefaultHttpAsyncClient httpclient = new DefaultHttpAsyncClient();
> httpclient.getCredentialsProvider().setCredentials(
> new AuthScope("localhost", 8080),
> new UsernamePasswordCredentials("super", "super1"));
> The server actually returns in the response HTTP 1.1 but includes "Connection: close" in the response header. Right after the response is done sending, the server closes the connection. This is a wireshark capture of the transaction:
> GET / HTTP/1.1
> Host: localhost:8080
> Connection: Keep-Alive
> User-Agent: Apache-HttpAsyncClient/4.0-alpha3 (java 1.5)
> HTTP/1.1 401 Unauthorized
> Content-Type: application/json
> Connection: close
> WWW-Authenticate: Digest realm="@127.0.0.1", qop="auth", nonce="44", opaque="deadbeef"
> Transfer-Encoding: chunked
> 4b
> {"status":{"code":401,"commandResult":1,"msg":"Unauthorized.","query":"/"}}
> 0
> When I run the modified example, the future.get() call returns with null, and the program errors out on a null exception (due to the response.getStatusLine()).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Commented] (HTTPASYNC-11) Default Async HTTP Client Fails
to get response for an Digest Authenticated HTTP 1.0 style connection
Posted by "Oleg Kalnichevski (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185867#comment-13185867 ]
Oleg Kalnichevski commented on HTTPASYNC-11:
--------------------------------------------
I am pretty close to finishing the last round of changes for HttpCore 4.2-beta1 release. If any bugs are found within a week or so, I'll make sure they get fixed before the official release.
Oleg
> Default Async HTTP Client Fails to get response for an Digest Authenticated HTTP 1.0 style connection
> -----------------------------------------------------------------------------------------------------
>
> Key: HTTPASYNC-11
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-11
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-alpha3
> Environment: Ubuntu 10.4.3, Java 6
> Reporter: Phillip Wang
> Fix For: 4.0-alpha4
>
> Attachments: nullresponse
>
>
> I'm trying to use the HTTP Async client v4.0 alpha 3 to communicate with a HTTP v1.0-style server with Basic Digest authentication. I started with the basic example "Asynchronous HTTP exchange", and updated the first couple lines to this:
> DefaultHttpAsyncClient httpclient = new DefaultHttpAsyncClient();
> httpclient.getCredentialsProvider().setCredentials(
> new AuthScope("localhost", 8080),
> new UsernamePasswordCredentials("super", "super1"));
> The server actually returns in the response HTTP 1.1 but includes "Connection: close" in the response header. Right after the response is done sending, the server closes the connection. This is a wireshark capture of the transaction:
> GET / HTTP/1.1
> Host: localhost:8080
> Connection: Keep-Alive
> User-Agent: Apache-HttpAsyncClient/4.0-alpha3 (java 1.5)
> HTTP/1.1 401 Unauthorized
> Content-Type: application/json
> Connection: close
> WWW-Authenticate: Digest realm="@127.0.0.1", qop="auth", nonce="44", opaque="deadbeef"
> Transfer-Encoding: chunked
> 4b
> {"status":{"code":401,"commandResult":1,"msg":"Unauthorized.","query":"/"}}
> 0
> When I run the modified example, the future.get() call returns with null, and the program errors out on a null exception (due to the response.getStatusLine()).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org