On Wed, 2010-04-14 at 08:03 -0400, Eric Covener wrote: > On Wed, Apr 14, 2010 at 6:32 AM, <achristian...@softreset.de> wrote: > > On Wed, 14 Apr 2010 05:44:26 -0400, Eric Covener <cove...@gmail.com> wrote: > >>> RewriteRule ^(.*)$ http://localhost:9090/index.jsp [P] > >> > >>> The browser ends up with a not working URL: > >>> http://localhost:9090/setup/login.jsp > >> > >> http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypassreverse > > > > I did not mention in this case it is about a full managed > > Linux box. Access to the Apache config is not permitted. > > One hat to use a .htaccess file. > > > > Is there something similar to ProxyPassReverse which works > > in the .htaccess? > > Maybe 'Header edit Location ...' but I'm not sure if Header directives > in your htaccess will still be applicable after all the proxying work > is done (it wouldn't with ProxyPass, but it might since you had > mod_rewrite in htaccess) > >
Eric - what makes [P] valid in an htaccess, but not ProxyPass/ProxyPassReverse ? Mark. -- Mark Watts BSc RHCE MBCS Senior Systems Engineer, Managed Services Manpower www.QinetiQ.com QinetiQ - Delivering customer-focused solutions GPG Key: http://www.linux-corner.info/mwatts.gpg
signature.asc
Description: This is a digitally signed message part
