From aa25bfb0e0f1b8cbdec29fb3b245bdea59d1a234 Mon Sep 17 00:00:00 2001 From: Madhura Bhave Date: Thu, 23 Mar 2017 16:11:22 -0700 Subject: [PATCH] Clarify the effect that management.context-path has on endpoint paths Fixes gh-8586 --- .../src/main/asciidoc/production-ready-features.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc b/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc index cda90353a8..876891a64f 100644 --- a/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc +++ b/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc @@ -602,6 +602,8 @@ those values (so you can use anything that is legal in a URL path). For example, the location of the `/health` endpoint to `/ping/me` you can set `endpoints.health.path=/ping/me`. +NOTE: Even if an endpoint path is configured separately, it is still relative to the `management.context-path`. + TIP: If you provide a custom `MvcEndpoint` remember to include a settable `path` property, and default it to `/{id}` if you want your code to behave like the standard MVC endpoints. (Take a look at the `HealthMvcEndpoint` to see how you might do that.) If your custom