--- [EMAIL PROTECTED] wrote:

> Where in your config should come the https from ?
> 
> If you want a secure communication to the backend than make a virtual host on
> Port 80 for the frontend, rewrite than all incoming requests from the second
> virtual host which is listening on Port 443 of your frontend server and put
> there (in the 443 Virtuel Host Config )your ProxyPass Lines. 
> 
> bye
> 
> Oliver
> 

Hi Oliver,

 thanks for the offered help, but either I don't understand your answer, or
maybe I did not illustrate my problem good enough. Let me try again.

It goes like this (fe - fronted, be - backend):

Browser--------------------------Proxy(fe)------------------------Backend
  |-------http:/fe/b-end/----------->|                             
                                     |-------http://be/----------->|
                                     |<--(302)--http://be/Login/---|
  |<--(302)--http://fe/b-end/Login/--|
  |-----http://fe/b-end/Login/------>|
                                     |-----http://be/Login/------->|
                                     |<--(302)-https://be/Login/---|
  |<--(302)--http://fe/b-end/Login/--|

Now, the last response from the backend indicates that the browsers next
request should go to the https port, however, ProxyPassReverse translates it to
http instead to https. Even if I try: ProxyPassReverse https:/fe/b-end/
https://be/

What am I missing here?

BR,
Kresimir



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

---------------------------------------------------------------------
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: [EMAIL PROTECTED]
   "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to