1

I have configured apache reverse proxy. In that configuration https connection is possible between client to reverse proxy and again reverse proxy to server. But I want https connection between client to server like forward proxy. The https connection should not be broken at reverse proxy. 

     Https tunnel                   New Https tunnel
    <===============>             <===================>

Client-----------------------Apache Reverse proxy ----------------------------Server

Above solution is not desirable. 

                  Https Tunnel
   <========================================>

Client--------------------Apache Reverse proxy ----------------Server

Above solution is desirable.

If end to end https tunnel is not possible in reverse proxy then how can it be ensured that ssl proxying option is safe and even the Reverse proxy administrator(if reverse proxy got compromised) can not decrypt the tunnel or man in middle attack can't be done.

user3245862
  • 23
  • 1
  • 3
  • 1
    This question appears to be off-topic because it is not about programming. See [What topics can I ask about here](http://stackoverflow.com/help/on-topic) in the Help Center. Perhaps [Server Fault](http://serverfault.com/) or [Webmaster Stack Exchange](http://webmasters.stackexchange.com/) would be a better place to ask. – jww Jul 13 '14 at 22:17
  • You can't. You could implement a load balancer at a lower level (e.g. via `ipchains`). – Bruno Jul 14 '14 at 01:09

1 Answers1

1

You can't. Because HTTPS by design guarantees that the sender is talking to the receiver via certificates. Your proxy here would be "the man in the middle" :-)

See http://en.wikipedia.org/wiki/Reverse_proxy

In the case of secure websites, a web server may not perform SSL encryption itself, but instead offloads the task to a reverse proxy that may be equipped with SSL acceleration hardware. (See SSL termination proxy.)

What you can do

Client------Apache Reverse proxy----SC--------------SS---------Server
            HTTPS                           SSL           HTTP        
            (listen to 443)

Where SC = Stunnel Client and SS = Stunnel Server

SC must run in the same machine as your apache reverse proxy, while SS must run in your server target.

Leo
  • 6,480
  • 4
  • 37
  • 52