On Sat, Feb 5, 2011 at 4:56 AM, Kalle Korhonen <kalle.o.korho...@gmail.com> wrote:
> Sorry for being a bit late to the party. Thanks Barry for reporting > and already proposing a patch. Yes, it really seems it's a feature of > Shiro. I do a find it a bit funny though (yes, I'm a Shiro committer > but haven't been on board from the beginning) that it's the default > behavior and that there's no configurable option to make it case > insensitive even if this is never an issue if your resource urls are > case sensitive. Regardless, Tapestry treating urls as case insensitive > makes this a bug in tapestry-security. Lowercasing all urls repeatedly BTW URL should be considered in a case sensitive manner expect for the machine name part which could be considered case insensitive. Could that open up a discussion on how Tapestry5 treats URL? > releasing tap-sec is quite a bit faster than for Shiro. And just a > note on annotations vs url matching - I always suggest using both if > you are serious about security. Totally agree, using annotation should be mandatory IMHO. Cheers -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
