OK Oleg,
I've created issue in JIRA HTTPASYNC-51

Alex


On Tue, Aug 6, 2013 at 9:09 AM, Alex Oscherov <[email protected]>wrote:

> Oleg,
> thanks a lot for a fast turnaround. I am going to file JIRA issue shortly.
>
> Alex
>
>
> On Tue, Aug 6, 2013 at 12:55 AM, Oleg Kalnichevski <[email protected]>wrote:
>
>> On Mon, 2013-08-05 at 10:59 -0700, Alex Oscherov wrote:
>> > I have a problem making http async client working with Exchange server
>> > through IIS 7.5. Everything works fine as long as requests are small
>> > but as soon as size of requests increases communication fails with the
>> > HTTP 400 response from the server.
>> >
>> >
>> > Analysing log (attached) I observe following behaviour from the HTTP
>> > async client :
>> >
>> > 1. on line 2013/08/05 10:30:42:497 PDT [DEBUG] client starts sending
>> > request to the server
>> >
>> > 2. on line 2013/08/05 10:30:42:515 PDT client while sending request
>> > not finished receives authentication challenge from server
>> >
>> > 3. on line 2013/08/05 10:30:42:552 PDT client sends to the server new
>> > authenticated request but instead of starting to send body of the
>> > request from the beginning it just sends body of the request from the
>> > point where it was interrupted first time.
>> >
>> >
>> > As a result server can't process request and sends back HTTP 400.
>> >
>> > I am not an experienced http async client library user so it is quite
>> > possible that I am doing something wrong.
>> >
>> >
>> > Any advice or recommendation will be highly appreciated and any
>> > additional information if it is needed could be provided.
>> >
>> >
>> > Thank you,
>> >
>> >      Alex Oscherov
>> >
>>
>> Alex
>>
>> I think I figured the cause of the problem. Essentially, as a result of
>> out of sequence response HttpAsyncClient fails to reset the state of the
>> request producer, which results in garbled content of the second POST
>> message. Please raise a JIRA for this defect.
>>
>> Oleg
>>
>> PS: The way IIS 7.5 responds with an out of sequence HTTP response over
>> a _persistent_ connection is completely insane.
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>

Reply via email to