Get HttpServletRequest in RequestHandledEvent Spring

Question

I have a real nice application listener registered as seen below.

@Component
public class MyLogger implements ApplicationListener {

    @Override
    public void onApplicationEvent(ApplicationEvent event) {
        // not doing anything here
        // Check out the 'RequestHandledEvent' below though.
    }

    @EventListener(RequestHandledEvent.class)
    public void onApplicationEvent(RequestHandledEvent event) {
        // I'd like to get the HttpServletRequest that was just handled.
        // Furthermore, I'd really like to get the userPrincipal that was
        // on the request, so that I can know made the request

        // it seems I can do this
        // but the principal seems to already have been cleared.
        // is there a more straightforward way to get the request?
        HttpServletRequest request = ((ServletRequestAttributes) RequestContextHolder.getRequestAttributes()).getRequest();
    }

}

I feel like I should be able to do something like

event.getRequest()

But I haven't found a successful way to do so.

Long story short, I'd like like ONE PLACE in my application that I can get at the request that came in, and the principal that was on that request, so that I can do some logging, etc.

Should I be looking at a different application event maybe?

Alexander Yanyshin · Accepted Answer · 2016-12-17 16:16:50Z

2

You can get request with proper security principal by registering servlet filter like:

@Component
public static class RequestLoggingFilter extends OncePerRequestFilter {

    @Override
    protected void doFilterInternal(HttpServletRequest request, HttpServletResponse response, FilterChain filterChain) throws ServletException, IOException {
        final Principal userPrincipal = request.getUserPrincipal();
        // ...do what you want with principal and request info here
        filterChain.doFilter(request, response);
    }
}

To control order of fiters in filter chain you can either annotate your filter class with @Order annotation or register filter like this:

@Bean
public FilterRegistrationBean filterRegistrationBean() {
    FilterRegistrationBean registrationBean = new FilterRegistrationBean();
    RequestLoggingFilter filter = new RequestLoggingFilter();
    registrationBean.setFilter(flter);
    registrationBean.setOrder(Ordered.LOWEST_PRECEDENCE);
    return registrationBean;
}

edited Dec 17, 2016 at 16:16

answered Dec 17, 2016 at 11:22

Alexander Yanyshin

1,40011 silver badges9 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Jeff Over a year ago

How do I made sure this filter is the LAST thing that handles the request before the response is sent back to the client? Is there ordering configuration that I can read about?

Alexander Yanyshin Over a year ago

Added info about filters ordering.

Jeff Over a year ago

Okay. This seems to work pretty good. Problem is, this filter doesn't get hit if something happens up in Spring Security's chain (example - bad token gets passed in). I'm trying to find a single spot to be able to handle all these workflows, and find a single point of exit for my application where I'm able to log.

Jeff Over a year ago

Lastly. This filter gets hit BEFORE the controller is called. Is there a filter/auditor/event listener I can use to get the request and response AFTER a controller has done it's thing?

Collectives™ on Stack Overflow

Get HttpServletRequest in RequestHandledEvent Spring

1 Answer 1

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related