transfer closed with outstanding read data remaining

Two days ago I've started receiving the above error message when trying to get data via curl from my web tool.
The date I'm trying to access is ~850kb XML but it stops the transfer at ~800kb, varying between attempts. I've never had this problem before and the code was running fine for months.

The code runs perfectly fine on my localhost! Has something changed recently in altervista? Why is this happening?

Here's my curl code:

    $ch = curl_init();
    
    if(!empty($post)) {
        curl_setopt($ch, CURLOPT_POST      ,1);
        curl_setopt ($ch, CURLOPT_POSTFIELDS, $post);
    }

    curl_setopt($ch, CURLOPT_URL, $url);

    if (ini_get('open_basedir') == '' && ini_get('safe_mode' == 'Off'))
        curl_setopt ($ch, CURLOPT_FOLLOWLOCATION, 1);
        
    curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, 60);
    curl_setopt($ch, CURLOPT_TIMEOUT, 60);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
    curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
    
        
    if (strpos ($url, "AssetList.xml") !== false) {
           $fp = fopen('../transfer.log', 'w');
           curl_setopt($ch, CURLOPT_VERBOSE, TRUE);
           curl_setopt($ch, CURLOPT_STDERR, $fp);
        }
    $data = curl_exec($ch);
    curl_close($ch);

[karl94]

Could you please specify the URL of the request?

This is the general URL: https://api.eveonline.com/corp/AssetList.xml.aspx

However, it requires some code to get to the full list I'm trying to reach. I'm not comfortable publishing this code on a public forum. Shall I PM you?

[karl94]

Shall I PM you?

Yes, it's necessary in order to verify the problem.
http://forum.en.altervista.org/priva...ewpm&u=4238108

Mail sent. Thanks!

The problem seem to have been fixed.
Was it something on your end?

[karl94]

The problem seem to have been fixed.
Was it something on your end?

No, we didn't change anything. The cause might have been not on our end, we didn't had the time to verify properly.
However, if the problem comes up again, let us know.

Hi there,

The problem has come up again. I tried running the code on my local server and it runs fine, so I suspect it *is* on your end.

[saitfainder]

The problem has been confirmed and we are investigating about it. I think we can say something more in a few days.

Good news!
It is important to clarify that the problem is intermittent, so sometimes it works while others it doesn't