cURL / Mailing Lists / curl-library / Single Mail


Re: Webdav over SSL; IIS 7.5; Files larger than ~7.5MB

From: Chris Knight <>
Date: Sun, 6 Jan 2013 12:06:33 +0000

So just to give an update on this,

After receiving a tip off I managed to get a work around for this issue.
 It turns out the problem was to do with using libcurl and openssl because
when I use polarssl there is no problem.

I tried figuring out exactly what the issue was but given ssl is not my
area of expertise I can't dig too deep before I get a little bit lost, just
thought I should let people know that there is a way round the issue if
they come across it.


On 28 December 2012 18:34, Chris Knight <> wrote:

> Hi Daniel,
> Thank you very much for your reply.
> I completely understand where you are coming from as this was also my
> initial conclusion. However the only limit on the server is 30MB but the
> real reason why I suspect its either libcurl or perhaps more likely me
> missing a trick is that all of the third party webdav clients I have used
> work without this limitation.
> I am by no means ruling out a server config issue as I'm not an IIS expert
> by any means, I know enough to get by but thats all. I was kind of hoping
> that since I am using near the http put example and all the IIS servers I
> am having issues with are vanilla installs plus the webdav module that
> perhaps someone else has come across this issue and knows how to solve it?
> I'm not being lazy as I truly have spent a lot of time trying to figure
> this out as I do prefer learning that way however I have ran out of places
> to look. Any new directions or hints would be warmly welcomed as like I
> said I have no problem doing the leg work so long as I have some sort of
> lead.
> Chris
> On 27 December 2012 22:21, Daniel Stenberg <> wrote:
>> On Wed, 26 Dec 2012, Chris Knight wrote:
>> uploading files to both Apache and IIS servers using basic auth and ssl.
>>> The only time I have an issues is with IIS and when a file is larger than
>>> 7716864 bytes.
>> Since there's just nothing in libcurl or OpenSSL that knows about such a
>> limit, I would say that it points clearly to a problem in the other end.
>> Also the fact that it sends a 500 eventually says that the server-side
>> makes the decision and acts on it. I would advice you to read up in the
>> server logs and ask server admins/support for guidance.
>> --
>> /
>> ------------------------------**------------------------------**-------
>> List admin:**listinfo/curl-library<>
>> Etiquette:**etiquette.html<>

List admin:
Received on 2013-01-06