sdeleuze 43d3abdfd5 Fix SockJs CorsConfiguration for forbidden origins ...

After this commit, AbstractSockJsService uses the configured allowed
origins when generating the CorsConfiguration instead of "*".

As a consequence, forbidden origin requests still result in a 403
response but now with no CORS headers in order to improve consistency
between the status code and the headers.

Issue: SPR-16304

2018-01-15 18:07:24 +01:00

..

src

Fix SockJs CorsConfiguration for forbidden origins

2018-01-15 18:07:24 +01:00

spring-websocket.gradle

Latest dependency updates (POI 3.17, Rome 1.8, EhCache 3.4, Caffeine 2.5.6, RxJava 2.1.4, Tomcat 8.5.21, JRuby 9.1.13, Rhino 1.7.7.2)

2017-09-23 11:28:19 +02:00