Shibboleth Developers

["Scott Cantor" <>]

> So the URL has to have something in it that matches the servlet-mapping
> and filter-mapping of the two WEB-INF/web.xml files in the CAS and
> Resource contexts. For example, right now I do a mapping on "*.shire" 
> to the Filter because that's the way the C++ Filter installation 
> instructions tell me to map the ISAPI Filter.

Ok, thanks, that makes sense.

> In practice, the only actual SHIRE URL is typically
> /contextname/Shibboleth.shire and, I suppose, the mapping is too general
> if anyone ever writes an application with files that actually 
> end in .shire.

Right, though of course any extension needed to avoid a conflict is fine.
Somebody already got confused and tried to invoke a script with that
extension to test the target with predictably bad results.

Note I still think we should rework the TARGET approach in 1.3 anyway, just
to get a jump on 2.0. If we can better accommodate what you're working on at
that point, we should do that.

-- Scott