You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@commons.apache.org by Mahendran Pirinthapan <mp...@gmail.com> on 2015/05/12 17:18:00 UTC

[commons-httpclient] Continuously getting 401 response when using commons-httpclient

Hi all,

We are using apache commons-httpclient-3.1.0 in our project to send Rest
call requests to Jenkins server, which is deployed in our environment. We
have the following code to set the credentials for the requests.

httpClient.getState().setCredentials(AuthScope.ANY,new
UsernamePasswordCredentials(
                                                         username,
password));
httpClient.getParams().setAuthenticationPreemptive(true);

In our production environment if one request is responded with 401 status
code by Jenkins then the subsequent requests also fails with 401 status
code. Please find the debug log in [1].

Since our production environment is a long running server we can not
restart it frequently. So the above issue affects all the users if it
occurred once.

I kindly expect your thoughts on resolving this issue.

1.
https://drive.google.com/file/d/0B4YeqhMGkQxvZzYzVEVZVWgyUXc/view?usp=sharing


Thanks & Regards,
M.Pirinthapan


<https://plus.google.com/u/0/+MahendranPirinthapan/about>
<http://lk.linkedin.com/in/pirinthapan>
<https://www.facebook.com/MahendranPrinthapan/about>

Re: [commons-httpclient] Continuously getting 401 response when using commons-httpclient

Posted by Benedikt Ritter <br...@apache.org>.

Hello Mahendran,

2015-05-12 17:18 GMT+02:00 Mahendran Pirinthapan <mp...@gmail.com>:

> Hi all,
>
> We are using apache commons-httpclient-3.1.0 in our project to send Rest
> call requests to Jenkins server, which is deployed in our environment. We
> have the following code to set the credentials for the requests.
>
> httpClient.getState().setCredentials(AuthScope.ANY,new
> UsernamePasswordCredentials(
>                                                          username,
> password));
> httpClient.getParams().setAuthenticationPreemptive(true);
>
> In our production environment if one request is responded with 401 status
> code by Jenkins then the subsequent requests also fails with 401 status
> code. Please find the debug log in [1].
>
> Since our production environment is a long running server we can not
> restart it frequently. So the above issue affects all the users if it
> occurred once.
>
> I kindly expect your thoughts on resolving this issue.
>
> 1.
>
> https://drive.google.com/file/d/0B4YeqhMGkQxvZzYzVEVZVWgyUXc/view?usp=sharing


HttpClient has become it's own Top Level Project in the ASF. I recommend
upgrading to the latest version (if possible). If problems persist you
shoulg get in touch with the Http Components community [1].

Best regards,
Benedikt

[1] https://hc.apache.org/


>
>
>
> Thanks & Regards,
> M.Pirinthapan
>
>
> <https://plus.google.com/u/0/+MahendranPirinthapan/about>
> <http://lk.linkedin.com/in/pirinthapan>
> <https://www.facebook.com/MahendranPrinthapan/about>
>



-- 
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter