{"id":26376,"date":"2016-02-11T13:35:43","date_gmt":"2016-02-11T08:05:43","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=26376"},"modified":"2016-03-03T17:24:37","modified_gmt":"2016-03-03T11:54:37","slug":"restrict-ajax-request-caching-in-springsecurity","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/restrict-ajax-request-caching-in-springsecurity\/","title":{"rendered":"Restrict Ajax request caching in SpringSecurity"},"content":{"rendered":"

Spring Security has a nice feature of request caching. When user try to access secured resource without logging in into the system, spring security caches that request and redirect the user to the login page. After successful authentication it redirects user to that cached request. This works for both Ajax and non-ajax requests. To restrict request caching for Ajax request in Grails App<\/a>, we just need to follow some steps.<\/p>\n

    \n
  1. Create a class and extends it with HttpSessionRequestCache.<\/li>\n
  2. Override its saveRequest() method<\/li>\n<\/ol>\n

    [java]<\/p>\n

    class CustomHttpSessionRequestCache extends HttpSessionRequestCache {
    \n\tpublic void saveRequest(HttpServletRequest request, HttpServletResponse response) {
    \n\t\tif(!"XMLHttpRequest".equals(request.getHeader("X-Requested-With"))) {
    \n\t\t\tsuper.saveReqeust(request, response);
    \n\t\t}
    \n\t}
    \n}<\/p>\n

    [\/java]<\/p>\n

    Now register it as spring bean with name requestCache <\/strong>in your resources.groovy file<\/p>\n

    [java]<\/p>\n

    requestCache(ApplicationHttpSessionRequestCache) {
    \n\tportResolver = ref(‘portResolver’)
    \n\tcreateSessionAllowed = conf.requestCache.createSession \/\/ true
    \n\trequestMatcher = ref(‘requestMatcher’)
    \n}<\/p>\n

    [\/java]<\/p>\n

     <\/p>\n

    Thats it \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"

    Spring Security has a nice feature of request caching. When user try to access secured resource without logging in into the system, spring security caches that request and redirect the user to the login page. After successful authentication it redirects user to that cached request. This works for both Ajax and non-ajax requests. To restrict […]<\/p>\n","protected":false},"author":185,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":5,"footnotes":""},"categories":[7],"tags":[672],"class_list":["post-26376","post","type-post","status-publish","format-standard","hentry","category-grails","tag-spring-security"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t