Tapestry 4.0.x with tacos probably doesn't add the request header...
just the parameter. So, what you're seeing is consistent, and if
you want to plan ahead, check for the existence of either of those
On Thu, Mar 27, 2008 at 11:32 PM, Kelly Merrell <[EMAIL PROTECTED]> wrote:
> Thanks for the examp
I'm using 4.1.5 and I think I wrote that code against 4.1.3. I agree
that you shouldn't move your auth code into a filter - I only mentioned
that to explain why I wasn't handing you the whole filter code. You may
have to tweak the generated code a bit for 4.0.2. I just used firebug
to grab a
Thanks for the example Steve. My only issue is that I don't seem to be
getting a "dojo-ajax-request" header in the request. There is a
"dojoRequest" parameter, which seems like I can use it for the same
purpose. Are you using a version of Tapestry greater than 4.02?
I'm going to try to adopt
I already had a servlet filter doing some custom authentication and
handling redirects to a separate login service for expired sessions, so
I added a little extra code in there. First off, you can identify ajax
requests by the presence of an HttpServletRequest header called
"dojo-ajax-request"
I'm having a problem with my authentication redirect when using Ajax to
update page components. I use PageRedirectException on each page to
redirect to a login page if the user is not logged in when the page
validates. This works as expected when hitting the page normally, but if
I am using an
