[BUG] Reporting behind Reverse Proxy doesn't work

[zhongnansu]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Plugins
Please list all plugins currently enabled.

Screenshots
If applicable, add screenshots to help explain your problem.

Host/Environment (please complete the following information):

• OS: [e.g. iOS]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

---

I can't generate any reports and I believe it has to do with the reverse Proxy setting. The headless chrome that launches isn't communicating back through the proxy port and or path. There doesn't seem to be a setting specific to the kibana report like there is for the main kibana setting from elasticsearch.

Is there a method to get this to work right now on a reverse proxy?

Thanks!

This issue was submitted by @ky-ma
opendistro-for-elasticsearch/kibana-reports#332

[ky-ma]

Update:

Go do Discover
Create A filter, save the filter
click reporting
generate CSV

Expected Behavior
a dialog box that allows you to save the CSV file

Plugins
The standard plugs

It's the reverse proxy of exposing the Kibana UI through a "path" that's the problem when launching the headless chrome to create the CSV file.

[zhongnansu]

#222
This PR introduces some reporting specific settings that can be used to address this issue. It's availabe in 1.2 onwards.