If it almost works, we are almost not going to change it.
Actually I do not understand how your configuration can possibly work for any
other URL than http://app.mydomain.com/client1 which would be passed to the
backend as http://client1.app.mydomain.com/b2b, whereas
http://app.mydomain.com/cli
Hi, this is my vhost configuration:
DocumentRoot /var/www/htdocs
ServerName app.mydomain.com
RewriteEngine On
RewriteLog "/var/log/apache/rewrite.log"
RewriteLogLevel 9
RewriteRule ^/(.*) http:/%{REQUEST_URI}.app.mydomain.com:8080/b2b
[P]
The application that runs on J
Ian,
It rewrites an URL like "http://app.mydomain.com:8080/client1";, and I
wan´t to keep the default port (80) on URL, like:
"http://app.mydomain.com/client1";.
Understood ?
Sorry about my poor english...
Regards,
Fabricio.
--- Ian Huynh <[EMAIL PROTECTED]> escreveu:
> Fabricio
>
> Sorry
You probably get a redirection to http://localhost:8080, right?
Add
ProxyPassReverse / http://localhost:8080/
This will replace any redirection to http://localhost:8080/ with a redirection
to /.
If that does not work, try to explain more thoroughly what the problem is, i.e.
exactly wh
Fabricio
Sorry I don't understand exactly what's not working for you. Are you saying you
want to make the port # dynamic as well?
-Original Message-
From: Fabricio Luiz Machado [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 15, 2005 6:00 PM
To: users@httpd.apache.org
Subject: RE: [EMAI
Thanks Ian, it works.
But I can´t use it, because it loads an URL with '8080' port... :-(
Are there another way ?
regards,
Fabricio.
--- Ian Huynh <[EMAIL PROTECTED]> escreveu:
>
> you can use mod_rewrite to change the URL and proxy at the same time.
>
> add these lines in your httpd.conf
>
you can use mod_rewrite to change the URL and proxy at the same time.
add these lines in your httpd.conf
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule rewrite_module modules/mod_rewrite.so
Rewri
Hi there!
I integrate Apache + JBOSS with mod_proxy and it´s working fine to me.
Now, I will have a big application, for hundreds of different profile
clients.
These clients must access the application with an URL like this:
http://app.mydomain.com/client1
http://app.mydomain.com/client2
http://
