<?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: Sticky Sessions with Splunk Search Heads behind Apache Reverse-Proxy in Security</title>
    <link>https://community.splunk.com/t5/Security/Sticky-Sessions-with-Splunk-Search-Heads-behind-Apache-Reverse/m-p/52725#M1746</link>
    <description>&lt;P&gt;Hmmm. I tried adding that session cookie to the apache config, but can't seem to make that work- I am continually redirected back to the Splunk login screen when more than one backend proxies are configured. I'm assuming this is a session issue, because proxying a single backend server works fine, its when I add two or more that the behavior starts... I suppose this is more an Apache issue than Splunk, but I thought someone must have tried this.&lt;/P&gt;

&lt;P&gt;Here is my Apache config snippet (more or less straight out of the Apache docs):&lt;/P&gt;</description>
    <pubDate>Tue, 08 Mar 2011 00:54:32 GMT</pubDate>
    <dc:creator>damonmiller</dc:creator>
    <dc:date>2011-03-08T00:54:32Z</dc:date>
    <item>
      <title>Sticky Sessions with Splunk Search Heads behind Apache Reverse-Proxy</title>
      <link>https://community.splunk.com/t5/Security/Sticky-Sessions-with-Splunk-Search-Heads-behind-Apache-Reverse/m-p/52722#M1743</link>
      <description>&lt;P&gt;Hello. I have a set of 3 or so search-heads that have matching configurations. I am trying to configure an Apache Reverse-Proxy to load-balance between these servers to maximize search capacity and to handle HTTPS encoding, etc. &lt;/P&gt;

&lt;P&gt;I have sucessfully setup the proxy to point to a single search head, but when I configure more than one, I find the sessions continuing to round-robin between servers, intead of "sticking" to on search head after a session is established. I have followed a few recommendations as documented on the Apache mod_proxy and mod_proxy_balancer docs, but so far can't make this work. &lt;/P&gt;

&lt;P&gt;Does splunk have any standardized session variables, like "JSESSIONID" or the like I could leverage? Any other suggestions? Has anyone gotten this to work?&lt;/P&gt;

&lt;P&gt;Thanks!
Damon&lt;/P&gt;</description>
      <pubDate>Thu, 03 Mar 2011 01:27:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Sticky-Sessions-with-Splunk-Search-Heads-behind-Apache-Reverse/m-p/52722#M1743</guid>
      <dc:creator>damonmiller</dc:creator>
      <dc:date>2011-03-03T01:27:01Z</dc:date>
    </item>
    <item>
      <title>Re: Sticky Sessions with Splunk Search Heads behind Apache Reverse-Proxy</title>
      <link>https://community.splunk.com/t5/Security/Sticky-Sessions-with-Splunk-Search-Heads-behind-Apache-Reverse/m-p/52723#M1744</link>
      <description>&lt;P&gt;Haven't tried it myself, but looking at my splunk instance, it looks like there is a &lt;CODE&gt;session_id_HTTPPORTNUMBER&lt;/CODE&gt; (e.g., &lt;CODE&gt;session_id_8000&lt;/CODE&gt;) cookie. Will that do the trick?&lt;/P&gt;</description>
      <pubDate>Thu, 03 Mar 2011 01:46:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Sticky-Sessions-with-Splunk-Search-Heads-behind-Apache-Reverse/m-p/52723#M1744</guid>
      <dc:creator>David</dc:creator>
      <dc:date>2011-03-03T01:46:45Z</dc:date>
    </item>
    <item>
      <title>Re: Sticky Sessions with Splunk Search Heads behind Apache Reverse-Proxy</title>
      <link>https://community.splunk.com/t5/Security/Sticky-Sessions-with-Splunk-Search-Heads-behind-Apache-Reverse/m-p/52724#M1745</link>
      <description>&lt;P&gt;That's correct. The port number is the listen port of the Splunk Web process, 8000 by default.&lt;/P&gt;</description>
      <pubDate>Sat, 05 Mar 2011 11:54:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Sticky-Sessions-with-Splunk-Search-Heads-behind-Apache-Reverse/m-p/52724#M1745</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-03-05T11:54:09Z</dc:date>
    </item>
    <item>
      <title>Re: Sticky Sessions with Splunk Search Heads behind Apache Reverse-Proxy</title>
      <link>https://community.splunk.com/t5/Security/Sticky-Sessions-with-Splunk-Search-Heads-behind-Apache-Reverse/m-p/52725#M1746</link>
      <description>&lt;P&gt;Hmmm. I tried adding that session cookie to the apache config, but can't seem to make that work- I am continually redirected back to the Splunk login screen when more than one backend proxies are configured. I'm assuming this is a session issue, because proxying a single backend server works fine, its when I add two or more that the behavior starts... I suppose this is more an Apache issue than Splunk, but I thought someone must have tried this.&lt;/P&gt;

&lt;P&gt;Here is my Apache config snippet (more or less straight out of the Apache docs):&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2011 00:54:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Sticky-Sessions-with-Splunk-Search-Heads-behind-Apache-Reverse/m-p/52725#M1746</guid>
      <dc:creator>damonmiller</dc:creator>
      <dc:date>2011-03-08T00:54:32Z</dc:date>
    </item>
    <item>
      <title>Re: Sticky Sessions with Splunk Search Heads behind Apache Reverse-Proxy</title>
      <link>https://community.splunk.com/t5/Security/Sticky-Sessions-with-Splunk-Search-Heads-behind-Apache-Reverse/m-p/52726#M1747</link>
      <description>&lt;P&gt;&lt;IFMODULE mod_proxy.c=""&gt;&lt;BR /&gt;
ProxyPass / balancer://mycluster/ stickysession=session_id_8000 nofailover=On timeout=15&lt;/IFMODULE&gt;&lt;/P&gt;

&lt;P&gt;ProxyPassReverse / balancer://mycluster/ stickysession=session_id_8000&lt;/P&gt;

&lt;P&gt;&lt;PROXY&gt;&lt;BR /&gt;
BalancerMember &lt;A href="http://10.x.x.10:8000" target="_blank"&gt;http://10.x.x.10:8000&lt;/A&gt;&lt;BR /&gt;
BalancerMember &lt;A href="http://10.x.x.11:8000" target="_blank"&gt;http://10.x.x.11:8000&lt;/A&gt;&lt;BR /&gt;
&lt;/PROXY&gt;&lt;BR /&gt;
&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 09:25:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Sticky-Sessions-with-Splunk-Search-Heads-behind-Apache-Reverse/m-p/52726#M1747</guid>
      <dc:creator>damonmiller</dc:creator>
      <dc:date>2020-09-28T09:25:57Z</dc:date>
    </item>
    <item>
      <title>Re: Sticky Sessions with Splunk Search Heads behind Apache Reverse-Proxy</title>
      <link>https://community.splunk.com/t5/Security/Sticky-Sessions-with-Splunk-Search-Heads-behind-Apache-Reverse/m-p/52727#M1748</link>
      <description>&lt;P&gt;Finally got this working using Apache's internal balancer cookies (ROUTEID) as described in &lt;A href="http://httpd.apache.org/docs/2.2/mod/mod_proxy_balancer.html#example"&gt;http://httpd.apache.org/docs/2.2/mod/mod_proxy_balancer.html#example&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2011 02:28:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Sticky-Sessions-with-Splunk-Search-Heads-behind-Apache-Reverse/m-p/52727#M1748</guid>
      <dc:creator>damonmiller</dc:creator>
      <dc:date>2011-03-08T02:28:47Z</dc:date>
    </item>
  </channel>
</rss>

