Why do we need a trailing slash after setting path_prefix for management plugin ? #7309
Unanswered
claireleray-poclain
asked this question in
Questions
Replies: 1 comment
-
The plugin does not allow you to set up a redirect but you can put in a reverse proxy such as Nginx in front of the API (a good idea for many reasons for production anyway) and set up any URI rewrites you please. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
The documentation specifies that I can set
management.path_prefix
to use a prefix such as /my-prefix for HTTP requests to the management plugin. However, it also says that the URL to access the plugin will behost:port/my-prefix/
, with the trailing slash.This behavior works great, but I find it pretty confusing. What is the reason ? Is there a workaround to redirect
host:port/my-prefix
tohost:port/my-prefix/
?Beta Was this translation helpful? Give feedback.
All reactions