On Fri, Jun 11, 2010 at 2:13 PM, Tom Evans wrote:
> How is this different from your previous email thread on the same
> topic from yesterday
Sorry about that I have got very confused so I started fresh thread.
>, apart from to show that you completely ignored
No no its not that I ignore I am conf
On Fri, Jun 11, 2010 at 6:59 AM, Tapas Mishra wrote:
> Hi,
>
> We installed mingle (an application running on port 8080) on a
> computer on our LAN.
>
> It is accessible http://:8080
>
> Some one can within LAN can see a URL
>
> http://192.168.1.5:8080/profile/login
>
> and a login page he gets.
>
On Wed, Dec 16, 2009 at 11:24 AM, Rabadan Palenque, Jose
wrote:
> Hi,
>
> Whit the help of other member of the list (Antonio) I understood rewriterules
> is not what I need, the best option is mod_proxy
mod:proxy is one way, and mod_rewrite another. Basically mod_proxy is
for simple cases, but f
he url and showing https://server.apache
Now I'm reading documentation about mod_proxy
Thanks!
Saludos,
Jose Rabadán
-Mensaje original-
De: Krist van Besien [mailto:krist.vanbes...@gmail.com]
Enviado el: miércoles, 16 de diciembre de 2009 10:21
Para: users@httpd.apache.org
On Mon, Dec 14, 2009 at 12:51 PM, Rabadan Palenque, Jose
wrote:
> RewriteRule ^/(.*)
> http://ploneserver:8080/VirtualHostBase/https/%{SERVER_NAME}:443/$1 [P]
It is perfectly possible to use RewriteRules to proxy a particular URL
to another server. And the general pattern is indeed:
Rabadan Palenque, Jose wrote:
RewriteEngine On
RewriteRule ^/(.*)
http://localhost:8080/VirtualHostBase/https/%{SERVER_NAME}:443/$1 [P]
This works fine. But now I need to put the apache on other server
behind DMZ
I thought that this work fine but doesn’t work
RewriteEngine On
Rewr
