Thanks
The ProxyPassReverse was the issue... It works
Greetings,
Herwarth
-Original Message-
From: Axel-Stéphane SMORGRAV [mailto:[EMAIL PROTECTED]
Sent: Friday, June 24, 2005 13:31
To: users@httpd.apache.org
Subject: RE: [EMAIL PROTECTED] apache 2.0 as reverse proxy using mod_
HTTP 302 is not an error: it is a redirection. The thing which is wrong with
that is the Location header which makes a reference to a server which is not
known to the clients: webserver-internal. In other words, the backend server
tells the browser to make a request for
http://webserver-interna
Ok I made a mistake in the initial question
When someone goes to https://webserver it has to be redirected to
http://webserver-internal/dealer/start
You were right on https://login it has no subdirectory redirect and this works
without the rewrite...
I got the following 302 found error from th
OK Here is the deal: Your rewriterule is unnecessary. That's probably what
caused the 302.
What your rewriterule does is to send a redirect to https://webserver/ in
response to a request for the root path https://webserver/ (or a redirect to
https://login/ in response to a request for the root
Hello,
The configuration of virtual host https://login is the same:
Listen ip-address:443
ServerAdmin [EMAIL PROTECTED]
ServerName webserver
ProxyPass / http://login-internal/
ProxyPassReverse / http://login-internal/
SSLEngine on
SSLCertificateFile /etc/httpd/conf/ssl.
What is the configuration of the virtual host for https://login/ ???
What did you intend that the following line would do ?
RewriteRule ^/$ https://webserverl/$1 [R,L]
What host is it supposed to redirect to? Is "webserverl" (_l_) a typo?? If it
is a typo and you intended to make it "webse
Title: Message
hello,
i have some
difficulties using apache webserver as a reverse proxy. i am sure it has to do
something with url rewriting.
the situation is as
follows.
- at our company we
have some external ip address accessible via the internet. these ip addresses
has to be assig
