On Wed, Feb 18, 2009 at 8:27 PM, Andreas Dahlen wrote:
> The rewrite statements was wrong (I accidently changed one / to ?), should
> be "Location:
> http://login.internal.com/LoginSuccess?servername=http://backend1.internal.c
> om"
>
> Since RewriteRules doesn't operate on what goes out, is ther
On Fri, Feb 13, 2009 at 12:52 PM, Andreas Dahlén wrote:
> A succefull LoginRequest is redirected by the Location-header
> Location:
> http://login.internal.com?LoginSuccess?servername=http://backend1.internal.com
>
> I need to rewrite "servername=http://backend1.internal.com"; to
> "servername=ht
On Wed, 18 Feb 2009 20:27:21 +0100
Andreas Dahlen wrote:
> The rewrite statements was wrong (I accidently changed one / to ?),
> should be "Location:
> http://login.internal.com/LoginSuccess?servername=http://backend1.internal.c
> om"
>
> Since RewriteRules doesn't operate on what goes out, is t
> > A succefull LoginRequest is redirected by the Location-header
> > Location:
http://login.internal.com?LoginSuccess?servername=http://backend1.internal.c
om
>
> This isn't a legal URL. Is this really what is returned?
>
> RewriteRules don't operate on what goes out, only on what comes in.
> Prox
On Fri, Feb 13, 2009 at 12:52 PM, Andreas Dahlén wrote:
> A succefull LoginRequest is redirected by the Location-header
> Location:
> http://login.internal.com?LoginSuccess?servername=http://backend1.internal.com
This isn't a legal URL. Is this really what is returned?
RewriteRules don't operat
Hi!
I've got a webapplication that the login functionality is placed on
one server, and the
application is running on three other server (sort of loadbalancing).
A parameter on a
successfull login tells which backendserver that should handle the
requests. Everything
is placed behind a fro
