All Apps and Add-ons

reverse proxy issue with custom REST endpoint

Loves-to-Learn Everything

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?


Labels (1)
0 Karma
Get Updates on the Splunk Community!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

(view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...