From 5b1a4a0430ebb930da4cfbb57128c0d1113b8b3e Mon Sep 17 00:00:00 2001 From: Andy Wilkinson Date: Mon, 11 Sep 2017 12:10:42 +0100 Subject: [PATCH] Note that management.context-path is relative to server.context-path Closes gh-10200 --- .../src/main/asciidoc/production-ready-features.adoc | 4 ++++ 1 file changed, 4 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 166ef737f1c..b42617a7c35 100644 --- a/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc +++ b/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc @@ -636,6 +636,10 @@ your application might already use `/info` for another purpose. You can use the The `application.properties` example above will change the endpoint from `/{id}` to `/manage/{id}` (e.g. `/manage/info`). +NOTE: Unless the management port has been configured to +<>, `management.context-path` is relative to `server.context-path`. + You can also change the "`id`" of an endpoint (using `endpoints.{name}.id`) which then changes the default resource path for the MVC endpoint. Legal endpoint ids are composed only of alphanumeric characters (because they can be exposed in a number of places,