On Mon, Feb 14, 2011 at 2:56 AM, Massimo Lusetti wrote:
> 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?
At least earlier www protocol specs didn'
On Sat, Feb 5, 2011 at 4:56 AM, Kalle Korhonen
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 fr
Thanks for the quick fix.
When I saw the "run as" and "remember me" support in Shiro I knew I
had to take a closer look and I think I'm out of the security business
now. This is the first package I've seen that easily solves the simple
problem like the one above, yet is robust enough for sites whe
On Mon, Feb 7, 2011 at 9:43 AM, Mark wrote:
> On Sun, Feb 6, 2011 at 8:22 AM, Kalle Korhonen
>> Made a patch release yesterday with a fix, use 0.2.2 or 0.3.1, see
>> http://tynamo.org/tapestry-security+guide
> I found this in the destination of your link:
> Use lowercase throughout the shiro.ini f
On Sun, Feb 6, 2011 at 8:22 AM, Kalle Korhonen
wrote:
> Made a patch release yesterday with a fix, use 0.2.2 or 0.3.1, see
> http://tynamo.org/tapestry-security+guide
>
> Kalle
I found this in the destination of your link:
Use lowercase throughout the shiro.ini file configuration If you want
to
Made a patch release yesterday with a fix, use 0.2.2 or 0.3.1, see
http://tynamo.org/tapestry-security+guide
Kalle
On Fri, Feb 4, 2011 at 7:56 PM, Kalle Korhonen
wrote:
> Sorry for being a bit late to the party. Thanks Barry for reporting
> and already proposing a patch. Yes, it really seems it
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'
The problem is fixable in the Tynamo library so I filed a Jira and
included a fix.
http://jira.codehaus.org/browse/TYNAMO-75
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h
The fact that /aDmin, /Admin, /ADmin etc all work is exactly the
problem. That makes the whole url protection mechanism useless and
even worse it's not obvious it's not going to work. I just followed
the example and it seemed to work.
It's not really a big deal to add the annotations but in my cas
Even if you map /Admin to /admin, wouldn't you also need to map
/aDmin, /adMin, /admIn, /admiN, /ADmin, /aDMin, etc. ?
Personally I just use the annotations, but I can see how that might be
a bit difficult to retrofit into an application.
Mark
On Fri, Feb 4, 2011 at 6:32 AM, Barry Books wrote:
10 matches
Mail list logo
