Browser version: Chrome Version 121.0.6167.139 (Official Build) (arm64)
Browser OS version: Mac OS Sonoma 14.3.1
Original install method (e.g. download page, yum, from source, etc.): Kibana docker image
Description of the problem including expected versus actual behavior:
When Kibana is behind a proxy, the Dev Tools Console is not maintaining the prefix_path like all of the other apps in Kibana do.
Steps to reproduce:
I'm seeing in Kibana 8.12.2 that the prefix_path is being dropped by Dev Tools Console commands.
i.e. the "/kibana" in the example below.
v7.17.15 (correct)GET _cluster/health produces GET /kibana/_cluster/health?pretty=true
v8.12.2 (incorrect)GET _cluster/health produces GET /_cluster/health?pretty=true
I am obviously running kibana behind a proxy. All other apps in Kibana appear to be working fine, only Dev Tools Console seems to have an issue so far.
I've tried every combination in the kibana.yml file of:
Kibana version: 8.12.2
Elasticsearch version: 8.12.2
Server OS version: CentOS 7 (I know... I know...)
Browser version: Chrome Version 121.0.6167.139 (Official Build) (arm64)
Browser OS version: Mac OS Sonoma 14.3.1
Original install method (e.g. download page, yum, from source, etc.): Kibana docker image
Description of the problem including expected versus actual behavior: When Kibana is behind a proxy, the Dev Tools Console is not maintaining the
prefix_path
like all of the other apps in Kibana do.Steps to reproduce: I'm seeing in Kibana 8.12.2 that the prefix_path is being dropped by Dev Tools Console commands. i.e. the "/kibana" in the example below.
kibana.yml
elasticsearch.hosts: "server.mydomain.com:443/kibana
In Dev Tools Console:
v7.17.15 (correct)
GET _cluster/health
producesGET /kibana/_cluster/health?pretty=true
v8.12.2 (incorrect)
GET _cluster/health
producesGET /_cluster/health?pretty=true
I am obviously running kibana behind a proxy. All other apps in Kibana appear to be working fine, only Dev Tools Console seems to have an issue so far.
I've tried every combination in the kibana.yml file of:
Workaround: Workaround: For my use case, I am able to update the root route in my proxy and direct the traffic to the /kibana endpoint.
Describe the feature: Dev Tools should maintain the
prefix_path
like all other kibana apps.