You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2019. It is now read-only.
Just grabbed the source. Very compact :). We could do it in two steps I guess.
First step is supporting the following configuration like the way https://bitbucket.org/thetransactioncompany/cors-filter/ does. <init-param> <param-name>cors.configurationFile</param-name> <param-value>cors.properties</param-value> </init-param>
By doing that, after starting up, our CORSFilter will have internal state configuraed by cors.properties.
The second step (I feel it's still under thought in my mind): If we could have a separated object to represent cors.properties, we just need a 'flush' mechanism we could call from some where else. (I am avoiding race conditions ... and performance :()
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It will enable one scenario: changing CORS configuration without restarting the application server.
The text was updated successfully, but these errors were encountered: