Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Mar 22, 2012
  1. @yangtse
Commits on Mar 21, 2012
  1. CONNECT: fix multi interface regression

    The refactoring of HTTP CONNECT handling in commit 41b0237 that
    made it protocol independent broke it for the multi interface. This fix
    now introduce a better state handling and moved some logic to the
    http_proxy.c source file.
    Reported by: Yang Tse
Commits on May 24, 2011
  1. @yangtse

    build: inclusion guard

    yangtse authored
    Enclose header file in an inclusion guard
Commits on Apr 6, 2011
  1. @dfandrich

    Don't list NTLM in curl-config when HTTP is disabled

    dfandrich authored
    Also, fixed Curl_proxyCONNECT() stub with HTTP disabled.
Commits on Apr 5, 2011
  1. return code cleanup: build, init and run-time errors

    Stop the abuse of CURLE_FAILED_INIT as return code for things not being
    init related by introducing two new return codes:
    CURLE_NOT_BUILT_IN replaces return code 4 that has been obsoleted for
    several years. It is used for returning error when something is
    attempted to be used but the feature/option was not enabled or
    explictitly disabled at build-time. Getting this error mostly means that
    libcurl needs to be rebuilt.
    CURLE_FAILED_INIT is now saved and used strictly for init
    failures. Getting this problem means something went seriously wrong,
    like a resource shortage or similar.
    CURLE_UNKNOWN_OPTION is the option formerly known as
    CURLE_UNKNOWN_TELNET_OPTION (and the old name is still present,
    separately defined to be removed in a very distant future). This error
    code is meant to be used to return when an option is given to libcurl
    that isn't known. This problem would mostly indicate a problem in the
    program that uses libcurl.
Commits on Apr 4, 2011
  1. http-proxy: move proxy code to http_proxy.c

    The new http_proxy.* files now host HTTP proxy specific code (500+ lines
    moved out from http.c), and as a consequence there is a macro introduced
    for the Curl_proxyCONNECT() function so that code can use it without
    actually supporting proxy (or HTTP) in builds.
Something went wrong with that request. Please try again.