Changes between Version 1 and Version 2 of Ticket #31232, comment 1
- Timestamp:
- 02/05/2015 02:14:22 AM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #31232, comment 1
v1 v2 1 According to http://php.net/manual/en/function.curl-setopt.php the `CURLOPT_PROXYAUTH` field accetps the same options as `CURLOPT_HTTPAUTH`, however, only supports the subset of `CURLAUTH_BASIC` and `CURLAUTH_NTLM `.1 According to http://php.net/manual/en/function.curl-setopt.php the `CURLOPT_PROXYAUTH` field accetps the same options as `CURLOPT_HTTPAUTH`, however, only supports the subset of `CURLAUTH_BASIC` and `CURLAUTH_NTLM`. 2 2 3 3 {{{ … … 7 7 As a result, passing `CURLAUTH_ANY` should work fine, it's the same as effectively passing `CURLAUTH_BASIC | CURLAUTH_NTLM`. 8 8 9 Can you explain a little more about the environment it's failing in, and if altering WordPress to pass `CURLAUTH_BASIC` or `CURLAUTH_NTLM ` fixes it for you?9 Can you explain a little more about the environment it's failing in, and if altering WordPress to pass `CURLAUTH_BASIC` or `CURLAUTH_NTLM` fixes it for you?