title: Grails Spring security controller specific weird behaviour
body: <p>We are using grails 2.3.3 and spring-security-cas:1.0.5</p>
  
  <p>It all works perfectly until we deploy a new version, in which case, the browser sends the ticket again for some controllers. </p>
  
  <p>Which controller will be sent the security check is random. Clearing the browser cache fixes the issue.</p>
  
  <p>So when trying to reach some parts of the application, the user is taken to the application index page instead of the controller index page.</p>
  
  <p>Here is what we have in Config.groovy:</p>
  
  <pre><code>grails.plugins.springsecurity.userLookup.userDomainClassName = 'myApp.User'
  grails.plugins.springsecurity.userLookup.authorityJoinClassName = 'myApp.UserRole'
  grails.plugins.springsecurity.authority.className = 'myApp.Role'
  grails.plugins.springsecurity.cas.serverUrlPrefix = "https://sso-cas/myCAS"
  grails.plugins.springsecurity.cas.loginUri = "/login"
  grails.plugins.springsecurity.cas.serviceUrl = "http://localhost:8080/myApp/j_spring_cas_security_check"
  grails.plugins.springsecurity.cas.useSingleSignout = false
  grails.plugins.springsecurity.cas.proxyCallbackUrl = 'http://localhost:8080/myApp/secure/receptor'
  grails.plugins.springsecurity.cas.proxyReceptorUrl = '/secure/receptor'
  </code></pre>
  
  <p>Is there a way to avoid having to clear the user's cache after a redeploy?</p>