Status: New
Owner: ----
New issue 418 by hgschmie: Filters match on a servlet path, not the actual
request path
http://code.google.com/p/google-guice/issues/detail?id=418
In a Jersey based application (where all requests are handled by the Guice
based jersey filter, we use a single servlet as a "catchall". So we have
serve("*").with(JerseyContainer.class);
in the code. There are multiple endpoints mapped onto this servlet using
Jersey Resources. Some requests should now be processed by an additional
filter. So I added
filter("/special/*").through(MyFilter.class);
but MyFilter never gets triggered. The reason for this is that in line 126
of FilterDefinition, in doFilter() is a
final String path = ((HttpServletRequest) servletRequest).getServletPath();
This should be
final String path = ((HttpServletRequest) servletRequest).getRequestURI();
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"google-guice-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/google-guice-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
