[isamudaison]

This may be a global issue, but I have only tested on osX. Here is my advancedsettings.xml:

Code:

<advancedsettings>
                                              <network>
                                                <curlclienttimeout>45</curlclienttimeout>
                                              </network>
                                            </advancedsettings>

My problem is I have one https remote location that is very slow in it's directory listing. I can get it fine through a browser. I have another directory on the same server that isn't slow, that listing works fine in xbmc. I can narrow down the directory from the 'slow' one to a sub-directory and THAT works fine. I know it's not the ssl cert because of this.

Debug log (username, password & hostname have been censored out).

I notice in the log that there is this line:
WARNING: FillBuffer: curl failed with code 28

looking up the libcurl error code (http://curl.haxx.se/libcurl/c/libcurl-errors.html) I see that 28 is a 'Operation timeout. The specified time-out period was reached according to the conditions.' which is understandable if the timeout period is set too low, but 45 seconds is more than enough for this location (note that the error occurs well before 45 seconds have passed).

[isamudaison]

It looks like you have to set both options for timeout to have any effect:

Code:

<advancedsettings>
<network>
  <curlclienttimeout>45</curlclienttimeout>
  <curllowspeedtime>45</curllowspeedtime>
</network>
</advancedsettings>