Am 2021-09-23 um 10:42 schrieb Oleg Kalnichevski:
On 9/23/2021 9:21 AM, Nitish Chitta wrote:
When I try to hit the server with the wrong credentials for basic
authentication, I am getting a *socket-write exception* which should
ideally return a 401 status code. The server is closing the connection
immediately after it finds the credentials incorrect while the client is
still sending the body.
This is happening when the payload in the POST request is a large one.
There is no issue with the request that has correct credentials.
Is there is any possible solution for this? or is it a limitation on the
client due to blocking IO?
Appreciate any help! Thanks!
This is indeed a limitation of the classic (blocking) i/o.
As of version 5.1 one can use ResponseOutOfOrderStrategy to monitor HTTP
connections for out of sequence responses. This, however, involves a
certain performance penalty for SSL/TLS connections.
What a nice coincedence! Oleg, me and other committers worked hard on
this Strategy. It should what you need. Please search the mailing lists
for my indepth analysis of the problem and our solution for this.
If your server is not able to handle expect continue, you must use this
to avoid exceptions. Try expect continue first.
M
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org
For additional commands, e-mail: httpclient-users-h...@hc.apache.org
