A customer has been using our Splunk add-on with a reverse proxy and they reported that the add-on stopped working with our latest release that uses a custom REST endpoint for setup of the add-on.
In the screenshot below, I can see that the reverse proxy root_endpoint (/esa01) is used in the first 2 calls to GET when setting up that dashboard (these errors are usually there). However in the subsequent GET and POST calls with use of the custom endpoint the root_endpoint is not used. The add-on does not specify the base URL when using a custom REST endpoint, so I am wondering if there is an issue with the Splunk JavaScript SDK? Or is our add-on missing something to support reverse proxy?
