<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: splunk behind an apache proxy login issue in Security</title>
    <link>https://community.splunk.com/t5/Security/splunk-behind-an-apache-proxy-login-issue/m-p/106739#M3412</link>
    <description>&lt;P&gt;Ok, figured out &lt;EM&gt;a&lt;/EM&gt; solution.  This does appear to be a splunk weirdness, but one can get around it by adding  AllowEncodedSlashes On to your vhost for :80.  Will allow you to parse the doubly quoted path.  I already have http redirecting to https and the rest just worked.  &lt;/P&gt;</description>
    <pubDate>Wed, 01 May 2013 02:34:34 GMT</pubDate>
    <dc:creator>mdubbyap</dc:creator>
    <dc:date>2013-05-01T02:34:34Z</dc:date>
    <item>
      <title>splunk behind an apache proxy login issue</title>
      <link>https://community.splunk.com/t5/Security/splunk-behind-an-apache-proxy-login-issue/m-p/106738#M3411</link>
      <description>&lt;P&gt;My splunk instance is is behind an apache proxy.  Everything works correctly except for login.  When i log into splunk, the return_to param is being url quoted twice, but only url unquoted once it seems.&lt;BR /&gt;&lt;BR /&gt;
e.g. I go to my host &lt;A href="https://host/splunk" target="_blank"&gt;https://host/splunk&lt;/A&gt; and get redirected to the login screen with this url &lt;A href="https://host/splunk/en-US/account/login?return_to=%252Fsplunk%252Fen-US%252F" target="_blank"&gt;https://host/splunk/en-US/account/login?return_to=%252Fsplunk%252Fen-US%252F&lt;/A&gt;&lt;BR /&gt;
(note the return_to being quoted twice). After i authenticate i get a 404 at &lt;A href="http://app241.auto.mobileiron.com/%2Fsplunk%2Fen-US%2F" target="_blank"&gt;http://app241.auto.mobileiron.com/%2Fsplunk%2Fen-US%2F&lt;/A&gt; (notice not https, and the quoted path).&lt;/P&gt;

&lt;P&gt;Thoughts?&lt;/P&gt;

&lt;P&gt;My splunk and apache configs looks like this:&lt;BR /&gt;
in apache ssl.conf:&lt;BR /&gt;
    &lt;LOCATION&gt;&lt;BR /&gt;
        ProxyPass  &lt;A href="http://127.0.0.1:8000/splunk" target="_blank"&gt;http://127.0.0.1:8000/splunk&lt;/A&gt;&lt;BR /&gt;
        ProxyPassReverse &lt;A href="http://127.0.0.1:8000/splunk" target="_blank"&gt;http://127.0.0.1:8000/splunk&lt;/A&gt;&lt;BR /&gt;
    &lt;/LOCATION&gt;&lt;/P&gt;

&lt;P&gt;in web.conf&lt;BR /&gt;
root_endpoint = /splunk&lt;BR /&gt;
tools.proxy.on = True&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 13:47:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/splunk-behind-an-apache-proxy-login-issue/m-p/106738#M3411</guid>
      <dc:creator>mdubbyap</dc:creator>
      <dc:date>2020-09-28T13:47:29Z</dc:date>
    </item>
    <item>
      <title>Re: splunk behind an apache proxy login issue</title>
      <link>https://community.splunk.com/t5/Security/splunk-behind-an-apache-proxy-login-issue/m-p/106739#M3412</link>
      <description>&lt;P&gt;Ok, figured out &lt;EM&gt;a&lt;/EM&gt; solution.  This does appear to be a splunk weirdness, but one can get around it by adding  AllowEncodedSlashes On to your vhost for :80.  Will allow you to parse the doubly quoted path.  I already have http redirecting to https and the rest just worked.  &lt;/P&gt;</description>
      <pubDate>Wed, 01 May 2013 02:34:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/splunk-behind-an-apache-proxy-login-issue/m-p/106739#M3412</guid>
      <dc:creator>mdubbyap</dc:creator>
      <dc:date>2013-05-01T02:34:34Z</dc:date>
    </item>
  </channel>
</rss>

