attribute checker template & content negotiation

Peter Schober peter.schober at
Tue Feb 26 14:16:32 EST 2013

* Peter Schober <peter.schober at> [2013-02-26 16:50]:
> > It's actually an open Jira issue. Much of the work of course was
> > exactly the header parsing to do language negotiation, and then I
> > just didn't get around to adding code to the error handling.

Not sure I understand the planned consequences of that for the error

> > But I'm also sensitive to pushing more and more into the SP vs. just
> > relying on redirects to custom pages that can do whatever people
> > like.
> ACK.
> That (redirects and remote handling) is kind of where I started from
> (cf. the "AttributeChecker and redirectErrors" thread on the dev
> list). I have yet to try the sessionHook feature (outside the
> provided attribute checker), though.

OK, I'm rolling my own attribute checker sessionHook for local usage
now. Maybe I'll make it more generic later and have it send expected
and recieved attributes to some central handler, where the error pages
would be generated/rendered. Then the code on the SPs could remain the
same everywhere.

More information about the users mailing list