Re: How can the client visit the origin server via HTTPS proxy?

2017-02-22 Thread Daniel Stenberg
On Thu, 23 Feb 2017, Tanyaofeng wrote: If I call curl_easy_setopt(curl, CURLOPT_URL, "https://IP4:port4/xxx/xx;); in scenario 2, how can the HTTPS message reach origin server via HTTPS reverse proxy? You can't, unless you have some special entrance you know of, or know how to reach that

How can the client visit the origin server via HTTPS proxy?

2017-02-22 Thread Tanyaofeng
> we have three scenario, > 1.The first one is like this: > Terminal ---> HTTPS proxy ---> origin server > IP1 IP2:port2 IP4:port4 > > 2.The second one is like this: > Terminal ---> HTTPS reverse proxy ---> origin server > IP1

Re: possible patch release?

2017-02-22 Thread Jan Ehrhardt
Michael Felt in gmane.comp.web.curl.library (Wed, 22 Feb 2017 19:21:16 +0100): >Well, I am about to test build for AIX - but if I understand correctly - >SSPI - is a windows only issue, i.e., not something expected on Linux or >POSIX platforms. > >If so, - it might be +1 for Windows platform.

Re: How can the client visit the origin server via HTTPS proxy?

2017-02-22 Thread Daniel Stenberg
On Wed, 22 Feb 2017, Tanyaofeng wrote: 1.The first one is like this: Terminal ---> HTTPS proxy ---> origin server IP1 IP2:port2 IP4:port4 I set these options: curl_easy_setopt(curl, CURLOPT_URL, "http://IP2:port2/xxx/xx;); The URL should always mention

Re: possible patch release?

2017-02-22 Thread Ray Satiro via curl-library
On 2/22/2017 1:21 PM, Michael Felt wrote: > make check gives: > > TESTDONE: 808 tests out of 810 reported OK: 99% > TESTFAIL: These test cases failed: 1139 1140 > TESTDONE: 1073 tests were considered during 398 seconds. > Makefile:767: recipe for target 'quiet-test' failed > make[1]: ***

Re: possible patch release?

2017-02-22 Thread Dan Fandrich
On Wed, Feb 22, 2017 at 07:21:16PM +0100, Michael Felt wrote: > Well, I am about to test build for AIX - but if I understand correctly - > SSPI - is a windows only issue, i.e., not something expected on Linux or > POSIX platforms. One of the problems right now is that the autobuilds are currently

HTTP PUT Without Callbacks

2017-02-22 Thread corey kasten
Hi: I have been using HTTP POST method, via CURLOPT_POSTFIELDS and CURLOPT_POSTFIELDSIZE, which I like, since I can just specify the pointer to the data that I have in memory and don't need to use callbacks or files to provide the data. Now, I'd like to additionally make use of HTTP PUT, via the

Re: How can the client visit the origin server via HTTPS proxy?

2017-02-22 Thread moparisthebest
Hi, On 02/22/2017 09:45 AM, Tanyaofeng wrote: > we have three scenario, > 1.The first one is like this: > Terminal ---> HTTPS proxy ---> origin server > IP1 IP2:port2 IP4:port4 > > 2.The second one is like this: > Terminal ---> HTTPS reserve proxy --->

How can the client visit the origin server via HTTPS proxy?

2017-02-22 Thread Tanyaofeng
we have three scenario, 1.The first one is like this: Terminal ---> HTTPS proxy ---> origin server IP1 IP2:port2 IP4:port4 I set these options: curl_easy_setopt(curl, CURLOPT_URL, "http://IP2:port2/xxx/xx;); curl_easy_setopt(curl, CURLOPT_PROXY, "IP2");

Re: possible patch release?

2017-02-22 Thread Jan Ehrhardt
Daniel Stenberg in gmane.comp.web.curl.library (Wed, 22 Feb 2017 08:16:42 +0100 (CET)): >Due to issue #1276 [1] that was reported within an hour of the 7.53.0 release, >we're contemplating a follow-up patch release. All opinions and arguments for >or against are welcome. +1, as I said in the