You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is similar to #9081. When setting the spring.webflux.base-path, the Cloudfoundry specific actuators are also set under the configured base-path.
Looking for a workaround that allows the property to be set while relocating or redirecting the expected Cloudfoundry requests to the appropriate Actuators.
The text was updated successfully, but these errors were encountered:
We documented this as a known limitation for the servlet case and we should do the same for the webflux case.
mbhave
changed the title
Cloudfoundry specific actuators should not be affected if spring.webflux.base-path is changed
Document how to use cloudfoundry specific actuators with a custom base path for webflux applications
Jan 25, 2021
This issue is similar to #9081. When setting the
spring.webflux.base-path
, the Cloudfoundry specific actuators are also set under the configured base-path.Looking for a workaround that allows the property to be set while relocating or redirecting the expected Cloudfoundry requests to the appropriate Actuators.
The text was updated successfully, but these errors were encountered: