You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Ol...@unilog.de on 2006/02/14 12:44:58 UTC
[users@httpd] AW: RE [users@httpd] ProxyPass/ProxyPassReverse switch from http to https on redirect? (Apache 2.2.0)
Can you turn on "LogLevel Debug" and post some lines out of it.
If occur, Lines around "proxy: HTTPS: declining URL" or "proxy: HTTP: serving URL"
bye
Oliver
-----Ursprüngliche Nachricht-----
Von: Oliver.Schaudt@unilog.de [mailto:Oliver.Schaudt@unilog.de]
Gesendet: Mo 13.02.2006 19:41
An: users@httpd.apache.org
Betreff: RE [users@httpd] ProxyPass/ProxyPassReverse switch from http to https on redirect? (Apache 2.2.0)
Only to make a ProxyPassReverse is not enough to make https
Do you have in your httpd.conf at least Lines like this ?
SSLEngine On
SSLProxyEngine On
Listen fe:443
Your four lines with the Location shows a ProxyPass Directive with an absolute URL to the backend, which is normal.
You cannot go to the backend with only 1 Location, you have to do this at least twice.
1 for http and 1 for https. This was the intention why i said you need 2 virtual hosts.
Here are some examples
http://httpd.apache.org/docs/2.2/en/vhosts/examples.html
bye
Oliver
-----Ursprüngliche Nachricht-----
Von: Kresimir Peharda [mailto:kpeharda@yahoo.com]
Gesendet: Mo 13.02.2006 12:16
An: users@httpd.apache.org
Betreff: Re: [users@httpd] RE [users@httpd] ProxyPass/ProxyPassReverse switch from http to https on redirect? (Apache 2.2.0)
--- Oliver.Schaudt@unilog.de 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: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org