My instance is running behind a proxy with root end point as - say /mysplunkapp
The configurations are done in web.conf file correctly to reflect the root context path to /mysplunkapp
The problem is while login into splunk. From the firebug, we see that there is 303 - "See Other" firing up.
With this, the context path is lost and the proxy web server is not able to understand where to redirect the request to.
Hence, users getting lost ( redirected to some other page on the proxy) . This happens, on and off. Specifically, for sure for the first time login into Splunk.
I looked into the Splunk python code. But, could not locate where the login is handled. Though I see login.html where FORM based auth is taken care.. I could not see the real issue in the code. I suspect its around redirect and return_to variable.
In simple terms, whats expected is, after login into Splunk, the response should have the path as "/mysplunkapp"
but, what is redirected is just root "/".
Hence proxy is not able to understand where to redirect to?
#FIX (1) line below
return_to = '/mysplunkapp/en-US/' <<===
# Force a refresh of startup info so that we know to
# redirect if license stuff has expired.
updateCheckerBaseURL = self.getUpdateCheckerBaseURL()
ps: Replace hardcoded value with cherrypy.config.get('root.endpoint') , if you didn't like hardcoding.