Shibboleth Developers

["Scott Cantor" <>]

> Potentially there is one change, but it doesn't affect any 
> part of the published protocol. If you want to know the URL 
> of the original resource, to do some form of RequestMap 
> processing, then the code that extracts and decodes the URL 
> from the target= parameter has to check for nested targets 
> and do a second parse-decode. Otherwise it will confuse the 
> URL of CAS with the URL of the Resource. I can write a method 
> that does this automatically. Since this is new function for 
> new configurations that don't exist yet, no existing code has 
> to change and new code can use the common method.

How would you know to do this (unless it was doing this all the time)? What
if it was just a regular resource that happened to have a query string
parameter called "target"?

-- Scott