On Mon, 17 Dec 2007, McLean, Peter wrote:

This is a libcurl issue, please take follow-ups to the curl-library list where
I'm CCing this reply.

> I found a case where write access on the host is denied the user and so the
> transfer fails. I would expect in this case that the CURLcode 'result'
> returned in the 'data' element of the CURLMsg structure would be something
> other than CURLE_OK.

I agree completely.

> I found I can catch the HTTP error code with a call to curl_easy_getinfo
> requesting CURLINFO_HTTP_CODE (libcurl 7.10.6) but I'm not sure if this will
> work in all transfer cases or is the correct use of this function. Is this
> a known bug with curl_multi_info_read? If so what is the recommended work
> around?

It is not a known bug afaicr. What libcurl version are you using?

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html