Feature/cors filter

Based on http://www.w3.org/TR/cors/
The filter is called at the earliest possible point
Only works on preflight requests.
Created as a ConfigurationFactory and hence each host will have its own configurations
Junits available for the util class 
Since the filter had just string compares , have not created a junit.
If this throws a URISyntaxException, then host, port and scheme are uninitialized, no?
I believe this could lead to NPE's in the CorsFilter where you go things like `origin.getScheme().equals(...)`

Also, should this silently eat a bad URI? Seems like the cors processing should abort if it cant get a URI since it cant perform alot of the checks it needs to?

Generally its "safer" to user StringUtils for comparisons like `StringUtils.equals(..)` and `StringUtils.isNotBlank(..)` since they are "null friendly"