Age | Commit message (Collapse) | Author |
|
memory.h is included everywhere for this.
|
|
|
|
for the return code
|
|
160 shows.
We got no data and we attempted to re-use a connection. This might happen if
the connection was left alive when we were done using it before, but that was
closed when we wanted to read from it again. Bad luck. Retry the same request
on a fresh connect!
Deleted the sockerror variable again, it serves no purpose anymore.
|
|
within the switch.
|
|
defines are in setup.h.
|
|
|
|
|
|
|
|
so that the automatic testing hosts will test these changes over the weekend.
|
|
warnings. Minor edits by me.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
EAGAIN but only EWOULDBLOCK, which caused badness on HPUX. We also check for
and act the same on EINTR errors as well now.
|
|
portability. Also use Andy Cedilnik's compiler warning fixes.
|
|
|
|
|
|
systems. Bug report #701749.
|
|
way for emacs, and vim users should provide a similar non-polluting style
|
|
|
|
that the output looks better
|
|
care how many bytes that is readable NOW. Philippe Raoult reported the
bug in 7.10.3-pre3.
|
|
situation occurs, which it previously didn't!
This was reptoed by Evan Jordan in bug report #653022.
Also, if ERROR_SYSCALL is returned from SSL_write(), include the errno number
in the error string for easier error detection.
|
|
debug wasn't enabled
|
|
|
|
|
|
I reformatted some functions using a different indent than the rest
of the file.
|
|
by the internal debugfunction callback
|
|
CURLOPT_DEBUGFUNCTION and CURLOPT_DEBUGDATA.
|
|
|
|
|
|
|
|
do if the write would've blocked
|
|
|
|
on my test machine! :-)
|
|
This was a real bummer!
|
|
|
|
boxes.
|
|
|
|
cases where EWOULDBLOCK or equivalent is returned. We must not block.
|
|
|
|
over to non-blocking sockets, but this loops very nastily. We should return
back to the select() and wait there until more data arrives, not just blindly
attempt again and again...
|
|
|