Kibana: Help users who include the basePath in the request

[spalger]

It seems all too common that new users reach for the server.basePath setting and don't realize that they need to rewrite the requests coming to Kibana. While it would be awesome if we could just change the way server.basePath works without breaking every existing install using the setting, I think we could do more to help the person realize what's wrong by rendering a help message when the server responds with a 404 and the url starts with the server.basePath.

[RobinAllen]

It seems the concern here is:

• Everybody who tries to use 'basePath' gets confused, because it doesn't do what every new user expects it to do. (I've just wasted an hour down that path too!)
• You don't want to change 'basePath' because it would break existing installs.

So why not introduce a second parameter, and put it immediately under basePath in the yml, with a note saying "If you want to change the 'basePath', you might want to change this 'incomingRewriteRule' parameter too"

That way people wouldn't get so confused, it would 'just work', and it wouldn't break anyone's pre-existing install.

[gquintana]

Used in conjunction with Kibana Shield (aka XPack Security) plugin, you don't get a 401 error but an infinite 302 redirect loop because Shield redirects to /kibana/login

[thenom]

Without implementing a URL rewrite process for kibana then there seems no way of using an AWS ALB with path based routing. AWS ALB does not modify the path that is passed to the backend.