Hi,
Is it possible to alter a response header in a filter?
I already add some response headers with Response.setHeader(...), but I
want to add "HttpOnly" to every Set-Cookie header. Or is there an
alternative way to achieve this?
The JSESSIONID is apparently always set with HttpOnly, but not
Hi Thiago,
Thanks a lot for your concern!!!
Just about the time I found the solution, I got your email :)
Yes you are right, about the way ApplicationStateManager works.
I just debugged and verified it. It becomes bit difficult for someone new ,
that too when you have to make changes to the ta
On Tue, 07 Oct 2014 16:10:07 -0300, akshay
wrote:
Hi Thiago,
Hi!
In the application ,the SSO object is created by the
contributeApplicationstateManager method().
No. It's created by the ApplicationStateManager service, using the
contributed ApplicationStateCreator implementations, whe
Hi Thiago,
In the application ,the SSO object is created by the
contributeApplicationstateManager method().
When I debug, I see that the requestHandler method gets called first. Since
I try to use a SSO object, which is infact not created and only gets
created post the contributeApplicationstateM
On Tue, 07 Oct 2014 14:03:09 -0300, akshay
wrote:
Hi,
Hi!
As we know that the contributeRequestHandler(...) is called before the
contributeApplicationStateManager(...) method.
Why do you say that? I'm not sure that's correct. Anyway, the order here
doesn't make a difference.
--
Thia
eRequestHandler(...) is called before the
contributeApplicationStateManager(...) method.
Do we have a way through which I can access SSO in the request filter class
or the request Filter call can take place after the
contributeApplicationStateManager() method.
Regards!!
Akshay
I am trying to figure out how to implement a RequestFilter such that when a
session time out occurs, Tapestry can redirect user to my error page saying
“Your session has timed out”.
Here is my code, take from examples posted by Taha in the past
public class RequireSessionFilter implements Com
So, is there any mean to log onto the real class when a logger in injected in
that class ?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Request-Filter-not-called-if-declared-with-addInstance-vs-add-tp5715859p5715964.html
Sent from the Tapestry - User mailing list
.tapestry5.services.TapestryModule.RequestHandler"
In my config, tapestry log level was set to "info", and my project to all;
which explains the issue.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Request-Filter-not-called-if-declared-with-addInstance-vs-add-tp5715859p5
> With
"after:CheckForUpdates,before:URLRewriter" the behavior is the same.
You can't comma separate constraints in a single string like this. Use two
strings in the varargs method.
Try using system.out.println instead (or a debug breakpoint) but I doubt
that tapestry is logging at different log
/tapestry.1045711.n5.nabble.com/Request-Filter-not-called-if-declared-with-addInstance-vs-add-tp5715859p5715959.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tap
in context:
http://tapestry.1045711.n5.nabble.com/Request-Filter-not-called-if-declared-with-addInstance-vs-add-tp5715859p5715958.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
/tapestry.1045711.n5.nabble.com/Request-Filter-not-called-if-declared-with-addInstance-vs-add-tp5715859p5715903.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tap
(and additional annotations if provided).
>
> Is your logger of type org.slf4j.Logger?
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://tapestry.1045711.n5.nabble.com/Request-Filter-not-cal
.nabble.com/Request-Filter-not-called-if-declared-with-addInstance-vs-add-tp5715859p5715870.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For
Sorry, I was mistaken: lit does note work when I use:
filters.addInstance("myRequestFilter", MyRequestFilter.class,
"after:CheckForUpdates")
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Request-Filter-not-called-if-declared-with-addInstance-vs-a
I've tried to add a Request Filter (T 5.3.4)
In my module, I've added this :
and my filter is:
But my filter is not called (I see not log).
However, if I declare my filter with :
filters.add("myRequestFilter", new MyRequestFilter(log),
"after:CheckForUpdates&
I think, at the very least, we need to handle the null case better,
with a message that explains what property of what object/service is
null.
Further, it's looking like the current approach is a little
heavy-handed; perhaps the Request and Response objects should be
created earlier and stored int
Hi Richard,
Thanks a lot for your response! on your first point, I have tried this
with no luck... so your second observation may be more likely, although
the documentation just leaves me with more questions, i'm not convinced
that the state manager should ever turn up null, but it's not a bi
Hi Peter,
My guess is that for a RequestFilter, you need to ensure that your
filter is contributed after the default Tap5 filter that wires up the
HttpServletRequest object to the Tap5 Request object (which is what is
causing the NPE). However, I think on reading the RequestHandler
pipeline s
Hi,
Perhaps I haven't phrased this question quite right since I didn't get a
response... Let me try it again.
What I have is two contributions, a RequestFilter and a Dispatcher (the
code is just about identicle) both services have a dependancy on the
ApplicationStateManager, so I wire it by
Hi All,
I can get hold of the ApplicationStateManager using the Dispatcher
interface without a problem, however the same code fails using the
Tapestry RequestFilter interface? specifically
*if(asm_.exists(**UserAsoObject.class)**)) *returns a NPE. Would this be
a bug or shouldn't I be using
22 matches
Mail list logo