curl error 18 - transfer closed with outstanding read data remaining

Question

when retrieving data from a URL using curl  I sometimes  in 80  of the cases  get  error 18  transfer closed with outstanding read data remaining  Part of the returned data is then missing  The weird thing is that this does never occur when the CURLOPT RETURNTRANSFER is set to false  that is the curl exec function doesn t return the data but displays the content directly   What could be the problem  Can I set some of the options to avoid such behaviour

User · Answer

I got this error when my server ran out of disk space and closed the connection midway during generating the response and simply closed the connection

User · Answer

The error string is quite simply exactly what libcurl sees  since it is receiving a chunked encoding stream it knows when there is data left in a chunk to receive  When the connection is closed  libcurl knows that the last received chunk was incomplete  Then you get this error code   There s nothing you can do to avoid this error with the request unmodified  but you can try to work around it by issuing a HTTP 1 0 request instead  since chunked encoding won t happen then  but the fact is that this is most likely a flaw in the server or in your network setup somehow

User · Answer

I ve solved this error by this way     ch   curl init     curl setopt    ch  CURLOPT URL   http   www someurl      curl setopt    ch  CURLOPT TIMEOUT  30   ob start     response   curl exec    ch     data   ob get clean    if curl getinfo  ch  CURLINFO HTTP CODE     200   success    Error still occurs  but I can handle response data in variable

User · Answer

Seeing this error during the use of Guzzle as well  The following header fixed it for me    headers    gt         accept-encoding    gt   gzip  deflate        I issued the request with Postman which gave me a complete response and no error   Then I started adding the headers that Postman sends to the Guzzle request and this was the one that fixed it

User · Answer

Encountered similar issue  my server is behind nginx  There s no error in web server s  Python flask  log  but some error messsage in nginx log       crit  31054 31054   269464 open     var cache nginx proxy temp 3 45 0000000453  failed  13  Permission denied  while reading upstream   I fixed this issue by correcting the permission of directory    var cache nginx

User · Answer

I had this problem working with pycurl and I solved it using   c setopt pycurl HTTP VERSION  pycurl CURL HTTP VERSION 1 0     like Eric Caron says

User · Answer

I had the same problem  but managed to fix it by suppressing the  Expect  100-continue  header that cURL usually sends  the following is PHP code  but should work similarly with other cURL APIs    curl setopt  curl  CURLOPT HTTPHEADER  array  Expect        By the way  I am sending calls to the HTTP server that is included in the JDK 6 REST stuff  which has all kinds of problems  In this case  it first sends a 100 response  and then with some requests doesn t send the subsequent 200 response correctly

User · Answer

I got this error when i was accidentally downloading a file onto itself   I had created a symlink in an sshfs mount of the remote directory to make it available for download  forgot to switch the working directory  and used -OJ      I guess it won   t really   help   you when you read this  since it means your file got trashed

User · Answer

I bet this is related to a wrong Content-Length header sent by the peer   My advice is to let curl set the length by itself

User · Answer

I got this error when my server process got an exception midway during generating the response and simply closed the connection without saying goodbye  curl still expected data from the connection and complained  rightfully

[php] curl error 18 - transfer closed with outstanding read data remaining

Examples related to php

Examples related to curl