| Age | Commit message (Collapse) | Author | 
|---|
|  |  | 
|  | should be used | 
|  |  | 
|  | now cause the resolve function to return NULL immediately | 
|  | some bad thinking on my part. | 
|  | when not using ares. | 
|  |  | 
|  | instead to make it easier to find/read | 
|  | sessionhandle to make the duphandle() function work as supposed. Also tried
to start document functions the doxygen way (in the headers of the functions).
Can't make it work though... | 
|  | even such platforms?) | 
|  |  | 
|  |  | 
|  | is now treated as an error by libcurl | 
|  | concept, and added lib/README.curlx to explain details about it | 
|  | with Digest or NTLM. libcurl will now use HEAD to negotiate the authentication
and when done perform the requested POST. | 
|  | time to restructure this source file! | 
|  | Good enough? | 
|  |  | 
|  |  | 
|  | re-use these sources and functions for subsecond resolution timing | 
|  |  | 
|  |  | 
|  | * bring back subsecond resolution to CURLINFO_TOTAL_TIME
* Fix the Curl_pgrsDone() so that the final progress update is shown properly | 
|  |  | 
|  | from a name resolve. Without this, we leak memory! | 
|  |  | 
|  | existance of NI_WITHSCOPEID since some platforms have that define but still
can't function with it set. | 
|  |  | 
|  |  | 
|  | the specific time to wait for a resolve. The definition is at the top of
this source file. | 
|  |  | 
|  |  | 
|  | * Made the incoming line parser more forgiving to allow "name=contents" pairs
where the contents isn't within double quotes.
* Made the digest code return CURLDIGEST_BADALGO if a requested algorithm
isn't supported by the code. | 
|  | we use the NIFLAGS properly on both places in the code that use getnameinfo(). | 
|  | when set. | 
|  |  | 
|  |  | 
|  | less | 
|  |  | 
|  | of Curl_is_resolved() to address Roy Shan's reported problem. | 
|  |  | 
|  |  | 
|  | the new "fail with auth" code | 
|  |  | 
|  |  | 
|  | or Digest. | 
|  | argument to the NTLM function(s) | 
|  |  | 
|  | might change it. I don't *think* it does it when the timeout is 0,0 but it
is better to be sure... | 
|  |  |