Skip to content

Support multi-segment additional health endpoint paths - #51470

Open
Wanbinyu wants to merge 1 commit into
spring-projects:mainfrom
Wanbinyu:gh-48374-multisegment-health-path
Open

Support multi-segment additional health endpoint paths#51470
Wanbinyu wants to merge 1 commit into
spring-projects:mainfrom
Wanbinyu:gh-48374-multisegment-health-path

Conversation

@Wanbinyu

Copy link
Copy Markdown

This allows a health group's additional-path to contain multiple path segments on either the main or management server.

AdditionalHealthEndpointPath now accepts multi-segment values, and health endpoint routing resolves the group using the longest matching additional-path prefix. Spring MVC's exact-path handling now forwards the complete path consistently with WebFlux and Jersey. The shared integration test fixture verifies the behavior across all three web stacks, and the reference documentation has been updated.

Closes #48374

Tests:

  • ./gradlew :module:spring-boot-health:test
  • MVC, WebFlux, and Jersey HealthEndpointAdditionalPathIntegrationTests
  • Checkstyle for each changed Java source set

Signed-off-by: Wan bin yu <3431359639@qq.com>
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Aug 27, 2026
@Wanbinyu
Wanbinyu marked this pull request as ready for review August 27, 2026 06:40
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.

Support multi-segment paths when mapping a health group to an additional path

2 participants