Skip to content

Document behavior when multiple CorsConfigurationSource beans are present#19036

Open
hqqw2h-lgtm wants to merge 1 commit intospring-projects:mainfrom
hqqw2h-lgtm:gh-18583
Open

Document behavior when multiple CorsConfigurationSource beans are present#19036
hqqw2h-lgtm wants to merge 1 commit intospring-projects:mainfrom
hqqw2h-lgtm:gh-18583

Conversation

@hqqw2h-lgtm
Copy link
Copy Markdown

@hqqw2h-lgtm hqqw2h-lgtm commented Apr 4, 2026

Summary

Clarify in both servlet and reactive CORS documentation that Spring Security fails with an ambiguous bean definition error when multiple CorsConfigurationSource beans are defined, and direct users to use the per-chain .cors() DSL to specify which source to use.

Closes gh-18583

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Apr 4, 2026
Clarify that Spring Security fails with an ambiguous bean definition
error when multiple CorsConfigurationSource beans are present, and
refer users to the per-chain configuration section for the solution.

Closes spring-projectsgh-18583

Signed-off-by: hanweiwei <duzielww@163.com>
Signed-off-by: hanweiwei <duzielww@163.com>
@hqqw2h-lgtm hqqw2h-lgtm force-pushed the gh-18583 branch 2 times, most recently from 60627c5 to 85c9d8f Compare April 5, 2026 03:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: waiting-for-triage An issue we've not yet triaged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document behavior when multiple CorsConfigurationSource beans are present

3 participants