Re: SecuritySymbols.UNAUTHORIZED_URL isn't working in 0.6.1

2014-10-19 Thread George Christman
Awesome, I got it. I had app /* REQUEST ERROR but was missing 401 /error/unauthorized On Sun, Oct 19, 2014 at 10:59 PM, Kalle Korhonen wrote: > By the spec, application filters don't handle error requests by default > (Jetty, at least the o

Re: SecuritySymbols.UNAUTHORIZED_URL isn't working in 0.6.1

2014-10-19 Thread Kalle Korhonen
Yeah, omitting that certainly leaves it up to the container as well. Perhaps technically not a tapestry-security issue, but I added a note of it to the guide regardless. Kalle On Sun, Oct 19, 2014 at 9:24 PM, George Christman wrote: > Awesome, I got it. I had > > > app > /* >

Re: SecuritySymbols.UNAUTHORIZED_URL isn't working in 0.6.1

2014-10-19 Thread Kalle Korhonen
By the spec, application filters don't handle error requests by default (Jetty, at least the old versions, didn't conform). You need to have: app /* REQUEST ERROR as noted in http://tapestry.apache.org/error-page-recipe.html. I suspect you don't. Kalle

SecuritySymbols.UNAUTHORIZED_URL isn't working in 0.6.1

2014-10-19 Thread George Christman
Hi, I have the following configuration configuration.add(SecuritySymbols.LOGIN_URL, "/signin"); configuration.add(SecuritySymbols.UNAUTHORIZED_URL, "/error/unauthorized"); configuration.add(SecuritySymbols.SUCCESS_URL, "/account"); configuration.add(SecuritySymbols.REDIREC