Am 21.05.2013 um 14:39 schrieb Robert Zacherl <[email protected]>:
> Hello, > > Everything works fine as long as the asset's file size doesn't exceed a > certain limit (I'm not sure yet where this limit is but it's definitely > somewhere between 5 and 15 MB). Can you enable Trace and see what parameters you pass to functions? Also use CURL.SetOptionVerbose to get debug messages collected. What result does Perform method give you? For me a 50 MB upload is not an issue from a file or container. > I'm aware that the CURL component offers a couple of function which > influence the size of certain CURL options like e.q. SetOptionMaxFileSize > or SetOptionMaxFileSizeLarge (btw what is the difference between the two?) large is for 64bit, other for 32bit file sizes. But I'll change that for 3.3 release, so we internally always use the large method. Also I'll change OpenInputFile function to query file size and pass it to curl, so we can better show progress. > The strange thing > is that the correct amount of data for each uploaded file arrives at the DAM > server but the whole data only consists only of zero bytes. That sounds very strange. Greetings Christian -- Read our blog about news on our plugins: http://www.mbsplugins.de/ _______________________________________________ Mbsfmplugin_monkeybreadsoftware.info mailing list [email protected] https://ml01.ispgateway.de/mailman/listinfo/mbsfmplugin_monkeybreadsoftware.info
