Hi Carl,
Sorry it has taken a while to respond. An example like this should
make things clear:
External user URL:
http://www.example.com/app/Internal server URL:
http://internal.example.com/CASRootProxiedAs
http://www.example.com/app/If the user requests
http://www.example.com/app/foo/bar/ then this
will be proxied through to the internal server as
http://internal.example.com/foo/bar/. The service URL will be
constructed as [CASRootProxiedAs][Local URL] where the "Local URL" in
this case would be /foo/bar/ (the first proxy will strip the leading
/app/). A limitation is if you have
http://www.example.com/app/proxied to
http://internal.example.com/TheRealFancyNameOfTheApp/.
This is where another directive might come in handy to remove a
leading portion of the URI from the returned URL.
HTH,
-Phil
On Tue, Oct 6, 2009 at 1:54 PM, Carl Hall <
[hidden email]> wrote:
> Thanks for the link to the conversation.
>
> I believe that Nicolas' strategy will work just fine for me. How do you plan to append the requested URL to the service URL (querystring, etc)?
> --
> You are currently subscribed to
[hidden email] as:
[hidden email]
> To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user>
--
You are currently subscribed to
[hidden email] as:
[hidden email]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user