| Age | Commit message (Collapse) | Author |
|---|
|
possibly only on some platforms, but it happens on my Solaris 2.7 box and I
don't know anyone else that regularly build curl with krb4 support.
|
|
picky warnings
|
|
|
|
functions (and prevent warnings)
|
|
|
|
|
|
|
|
report #1004105
|
|
|
|
by Gisle Vanem's patch, only modified by me.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the digest code. This fixes it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
a connection is re-used, when a proxy is in use.
|
|
connections.
|
|
|
|
|
|
|
|
|
|
|
|
that particular index. Reported in bug report 997536.
|
|
|
|
|
|
|
|
Basically in loops like handle_errors(), 'query->next' was assigned a local
variable and then query was referenced after the memory was freed by
next_server(). I've changed that so next_server() and end_query() returns the
next query. So callers should use this ret-value.
The next problem was that 'server->tcp_buffer_pos' had a random value at entry
to 1st recv() (luckily causing Winsock to return ENOBUFS).
I've also added a ares_writev() for Windows to streamline the code
a bit more.
|
|
|
|
the initial setting up the struct should use this single function to avoid
having the initialisation code at two places.
|
|
|
|
we run configure.
|
|
get problems
|
|
|
|
|
|
|
|
|
|
|
