Re: HTTPS over mod_proxy

Rainer Jung <rainer.jung@xxxxxxxxxxx> · Tue, 19 Oct 2010 06:05:09 +0200

On 18.10.2010 16:30, Hendrik Schmieder wrote:

Rainer Jung schrieb:

Sorry, I meant:

CONNECT 192.168.2.234:7777 HTTP/1.1

(no path)

Regards,

Rainer

OK,

I hope I get it know:

I make the following sequence:

<request>
CONNECT http://192.168.2.234:7777 HTTP/1.1

</request>

wait for response

if response.statuscode == 200 send

<request>
GET http://192.168.2.234:7777/server/info HTTP/1.1
Content-Length: 0
Host: 192.168.2.234:7777
Connection: Keep-Alive
Accept-Encoding: identity, *;q=0

</request>

Hmm, after the CONNECT you are supposed to talk whatever protocol 

192.168.2.234 expects on port 7777. So if that is https, no more clear 

text :)

The proxy only forwards the raw packets. You wanted end-to-end security, 

you got it :)

And if the back-end realy talks http (no "s"), then it would be

GET /server/info HTTP/1.1

Regards,

Rainer

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx