> The request method doesn't matter for this. libcurl handles the end of the
> response the same way no matter which.
Will debug it next time if encounter that problem again.
Thank you!
Spirent Communications e-mail confidentiality.
On Wed, 9 Aug 2017, Novoseltsev, Igor via curl-library wrote:
* no chunk, no close, no size. Assume close to signal end
Could you kindly check the same for POST? While looking into log, I
discovered that it was 200 for POST. Body was in POST and body was in 200. I
would reproduce it, but
>> My application sends GET and receives 200 with body in response. The
>> 200 response has no Content-Length header. That causes libcurl not to
>> report DONE for the Easy, even whole body was reed from socket.
>>
>> To indicate end of body the server closes connection.
> I can't reproduce this
On Tue, 8 Aug 2017, Novoseltsev, Igor via curl-library wrote:
My application sends GET and receives 200 with body in response. The 200
response has no Content-Length header. That causes libcurl not to report
DONE for the Easy, even whole body was reed from socket.
To indicate end of body the
Hello folks,
I encountered issue while using libcurl 7.54.1 on Win7 (though OS does not
matter).
My application sends GET and receives 200 with body in response.
The 200 response has no Content-Length header.
That causes libcurl not to report DONE for the Easy, even whole body was reed
from
