| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
any name resolved data in any curl handle struct. That way, we won't mind
if the cache entries are pruned for the next time we need them. We'll just
resolve them again instead.
This changes the Curl_resolv() proto. It modifies the SessionHandle struct
but perhaps most importantly, it'll make the internals somewhat dependent
on the DNS cache not being disabled as that will cripple operations somewhat.
Especially for persistant connections.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
from the host names before comparing
|
|
|
|
now have --interface working properly
|
|
|
|
|
|
|
|
|
|
by Daniel.
|
|
A Bjørn Reese patch.
|
|
This can be optimized a tidbit, but this is a start.
|
|
|
|
browsers do. Which thus *breaks* the RFC 2616...
|
|
CURLINFO_REDIRECT_TIME and CURLINFO_REDIRECT_COUNT.
|
|
connected with reality! ;-)
|
|
will then return CURLE_READ_ERROR.
|
|
|
|
contents.
|
|
or not
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
better for FTP (any protocol with protocol-specific connect actions)
|
|
|
|
|
|
CURLOPT_DEBUGFUNCTION and CURLOPT_DEBUGDATA.
|
|
|
|
|
|
|
|
|
|
|
|
connect() so that it tells to which host and what port it is about to
attempt the connection
|
|
|
|
|
|
|
