<?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: How to resolve Server Abort error - Nginx Reverse Proxy (load balancing) in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-resolve-Server-Abort-error-Nginx-Reverse-Proxy-load/m-p/214244#M8007</link>
    <description>&lt;P&gt;Nginx reconfigured.&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jan 2017 18:12:36 GMT</pubDate>
    <dc:creator>BP9906</dc:creator>
    <dc:date>2017-01-04T18:12:36Z</dc:date>
    <item>
      <title>How to resolve Server Abort error - Nginx Reverse Proxy (load balancing)</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-resolve-Server-Abort-error-Nginx-Reverse-Proxy-load/m-p/214243#M8006</link>
      <description>&lt;P&gt;I thought I'd mention that I came across an error and worked with Splunk Support to determine the cause.&lt;BR /&gt;&lt;BR /&gt;
I had recently upgraded from Spunk 6.3.x to Splunk 6.4.x and I've been using Nginx as reverse proxy for a long time so that I can load balance traffic between peers of my SHC (search head cluster). &lt;/P&gt;

&lt;P&gt;The error was happening when I tried to save a search in the Saved Searches menu via Settings &amp;gt; Saved Searches (old style). &lt;/P&gt;

&lt;P&gt;The issue was apparent in Chrome console that I was getting conflicting X-Frame-Options headers.  Previously I put in this config and changed it to match Splunk:&lt;/P&gt;

&lt;P&gt;OLD:&lt;BR /&gt;
add_header X-Frame-Options DENY;&lt;/P&gt;

&lt;P&gt;NOW:&lt;BR /&gt;
add_header X-Frame-Options "SAMEORIGIN";&lt;/P&gt;

&lt;P&gt;This resolved my issue, in case someone else comes across it.  Apparently Splunk implemented X-Frame-Options in 6.4 so thats why this issue was happening.  I suppose I could remove the header altogether from Nginx but I thought I'd share what the cause and change was that helped me. &lt;/P&gt;</description>
      <pubDate>Wed, 04 Jan 2017 18:11:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-resolve-Server-Abort-error-Nginx-Reverse-Proxy-load/m-p/214243#M8006</guid>
      <dc:creator>BP9906</dc:creator>
      <dc:date>2017-01-04T18:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: How to resolve Server Abort error - Nginx Reverse Proxy (load balancing)</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-resolve-Server-Abort-error-Nginx-Reverse-Proxy-load/m-p/214244#M8007</link>
      <description>&lt;P&gt;Nginx reconfigured.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jan 2017 18:12:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-resolve-Server-Abort-error-Nginx-Reverse-Proxy-load/m-p/214244#M8007</guid>
      <dc:creator>BP9906</dc:creator>
      <dc:date>2017-01-04T18:12:36Z</dc:date>
    </item>
  </channel>
</rss>

