Improve support for port numbers in allowedOriginPattern of CorsConfiguration #26926
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
status: superseded
An issue that has been superseded by another
type: enhancement
A general enhancement
Currently it's not possible to support any port or multiple, specific ports with a single pattern. The workaround is to create two origin patterns such as
"https://*.example.com"
and"https://*.example.com:*"
.One idea is to enhance the pattern syntax with a comma separated list of ports or a wildcard:
This was originally reported in #26892.
The text was updated successfully, but these errors were encountered: