Downloading a SMB file larger than 16K (CURL_MAX_WRITE_SIZE) with a
DEBUGBUILD curl gives:
Warning: Data size exceeds single call write limit!
and the corresponding data is lost.
Obviously, SMB writes data chunks larger than CURL_MAX_WRITE_SIZE!
I don't know how (where) you want to
On Mon, 8 Dec 2014, Patrick Monnerat wrote:
Downloading a SMB file larger than 16K (CURL_MAX_WRITE_SIZE) with a
DEBUGBUILD curl gives:
Warning: Data size exceeds single call write limit!
and the corresponding data is lost.
Obviously, SMB writes data chunks larger than
On Mon, 8 Dec 2014, Daniel Stenberg wrote:
Additionally: Curl_client_write() is used without checking the return code
which is a major nono [*]. It MUST check the return code and bail out on
errors.
I added a warning now which makes smb.c no longer build with gcc. I left the
error in the
Daniel Stenberg wrote:
Warning: Data size exceeds single call write limit!
... It must thus at least be converted into a loop of calls.
Indeed :-) The question is: do we set this loop in smb or in Curl_client
write()? The later will resolve this problem for other protocols too.
It
It also makes me curious where the values for MAX_PAYLOAD_SIZE and
MAX_MESSAGE_SIZE come from? Also, if we could be happy with
CURL_MAX_WRITE_SIZE sized buffer we could aavoid the extra allocations in
smb.c compeletely! They are a bit disturbing since we already alloc two 16K
buffers that are
BTW: I have the pleasure to tell that, with the work done on NTLM and SMB,
I've seen a few minutes ago the first SMB curl-download of a Linux remote
file from the OS/400 :-))
Awesome. I had not yet tested on a big endian machine, so thanks for your
fixes.
-Bill
Daniel,
I discovered something in the code that might explain the cause of this
error - however I am not sure why the 900 second inactivity timeout works
on Windows and not on our Linux target where we get an error after exactly
60 seconds of inactivity at the end of the transfer just prior to
Patrick Monnerat wrote:
Downloading a SMB file larger than 16K (CURL_MAX_WRITE_SIZE) with a
DEBUGBUILD curl gives:
Warning: Data size exceeds single call write limit!
and the corresponding data is lost.
I noted this too, but curl -i smb://local-url removes this warning.
I have no
FYI I found the bug
On Mon, Dec 8, 2014 at 11:48 AM, John Coffey john...@gmail.com wrote:
Daniel,
I discovered something in the code that might explain the cause of this
error - however I am not sure why the 900 second inactivity timeout works
on Windows and not on our Linux target where we
On 12/8/2014 12:33 PM, John Coffey wrote:
FYI I found the bug
um... can you tell us please? :)
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
After looking for the correct line all day long I came up with this:
$ *CPPFLAGS=-I$HOME/zlib-1.2.8 -I$HOME/openssl-1.0.1j
-I$HOME/openssl-1.0.1j/include LDFLAGS=-L$HOME/zlib-1.2.8
-L$HOME/openssl-1.0.1j LIBS=-ldl ./configure --disable-shared
--with-zlib --with-ssl*
I had to add:
LIBS=-ldl as
Hi Arif,
On 08.12.2014 07:31, Arif Ali wrote:
Hello Guenter, I downloaded these binaries , but I also need the
libcurl.lib inorder to link it with my visual studio project. Are those
filea also posted somewhere?
yes, but unfortunately the devel packages are *not* build with WinSSL
which is what
On Mon, 8 Dec 2014, Patrick Monnerat wrote:
... It must thus at least be converted into a loop of calls.
Indeed :-) The question is: do we set this loop in smb or in Curl_client
write()? The later will resolve this problem for other protocols too.
Yeah, that would be better approach
fixing bugs!
If you have a few minutes, please consider browsing our bug tracker at:
https://sourceforge.net/p/curl/bugs/
and see if you can help us fix a bug, reproduce a bug or just add more
findings or ideas to the existing ones.
There are currently 23 open issues, most of them are
Hello Guenter,
Thanks for taking time and responding.
I am on Visual Studio 2008 , though I am on Windows87 64 bit . I want
binaries for 32 bit because my app is 32 bit. I did try building myself.
1. I downloaded the latest code from tarbal( earlier I had downloaded from
GIT
Hello Daniel,
after much debugging and sprinkling of printouts on our target platform, it
turns out that the source of the bug was 75% an application problem (mine)
and 25% (in my opinion) an libCurl issue due to the weakness of using
loosely coupled va_args to extract arguments from a variable
16 matches
Mail list logo
