<?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 Splunk HEC closes connection instead of re-using it in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-HEC-closes-connection-instead-of-re-using-it/m-p/703955#M116416</link>
    <description>&lt;P&gt;Our apps send data to the Splunk HEC via HTTP POSTS. The apps are configured to use a connection pool, but after sending data to Splunk (via HTTP POSTS), the Splunk server responds with a Status 200 and the "Connection: Close" header. This instructs our apps to close their connection instead of reusing the connection.&lt;/P&gt;&lt;P&gt;How can I stop this behavior? Right now it's constantly re-creating a connection thousands of times instead of just re-using the same connection.&lt;/P&gt;</description>
    <pubDate>Fri, 08 Nov 2024 19:19:00 GMT</pubDate>
    <dc:creator>onlineops</dc:creator>
    <dc:date>2024-11-08T19:19:00Z</dc:date>
    <item>
      <title>Splunk HEC closes connection instead of re-using it</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-HEC-closes-connection-instead-of-re-using-it/m-p/703955#M116416</link>
      <description>&lt;P&gt;Our apps send data to the Splunk HEC via HTTP POSTS. The apps are configured to use a connection pool, but after sending data to Splunk (via HTTP POSTS), the Splunk server responds with a Status 200 and the "Connection: Close" header. This instructs our apps to close their connection instead of reusing the connection.&lt;/P&gt;&lt;P&gt;How can I stop this behavior? Right now it's constantly re-creating a connection thousands of times instead of just re-using the same connection.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Nov 2024 19:19:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-HEC-closes-connection-instead-of-re-using-it/m-p/703955#M116416</guid>
      <dc:creator>onlineops</dc:creator>
      <dc:date>2024-11-08T19:19:00Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk HEC closes connection instead of re-using it</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-HEC-closes-connection-instead-of-re-using-it/m-p/703956#M116417</link>
      <description>&lt;P&gt;Are your clients sending proper HTTP/1.1. Splunk should support keep-alive out of the box.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Nov 2024 19:48:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-HEC-closes-connection-instead-of-re-using-it/m-p/703956#M116417</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-11-08T19:48:31Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk HEC closes connection instead of re-using it</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-HEC-closes-connection-instead-of-re-using-it/m-p/703958#M116418</link>
      <description>&lt;P&gt;Thank you for replying. Yes, the client is using HTTP 1.1 when sending the HTTP POSTS. This was verified within the packet capture.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Nov 2024 20:10:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-HEC-closes-connection-instead-of-re-using-it/m-p/703958#M116418</guid>
      <dc:creator>onlineops</dc:creator>
      <dc:date>2024-11-08T20:10:44Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk HEC closes connection instead of re-using it</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-HEC-closes-connection-instead-of-re-using-it/m-p/703960#M116420</link>
      <description>&lt;P&gt;Well, this says that Splunk should normally behave properly with HTTP/1.1&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Data/TroubleshootHTTPEventCollector#Detect_scaling_problems" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Data/TroubleshootHTTPEventCollector#Detect_scaling_problems&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Another thing to consider.&lt;/P&gt;&lt;PRE&gt;forceHttp10 = [auto|never|always]
* Whether or not the REST HTTP server forces clients that connect
  to it to use the HTTP 1.0 specification for web communications.
* When set to "always", the REST HTTP server does not use some
  HTTP 1.1 features such as persistent connections or chunked
  transfer encoding.
* When set to "auto", it does this only if the client did not send
  a User-Agent header, or if the user agent is known to have bugs
  in its support of HTTP/1.1.
* When set to "never" it always allows HTTP 1.1, even to
  clients it suspects might be buggy.
* Default: auto&lt;/PRE&gt;</description>
      <pubDate>Fri, 08 Nov 2024 21:02:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-HEC-closes-connection-instead-of-re-using-it/m-p/703960#M116420</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-11-08T21:02:49Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk HEC closes connection instead of re-using it</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-HEC-closes-connection-instead-of-re-using-it/m-p/703963#M116421</link>
      <description>&lt;P&gt;To fix this issue, we had our client insert the "Connection: Keep-Alive" header into the HTTP POST requests. This instructed the Splunk server to keep the connection alive.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Nov 2024 22:37:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-HEC-closes-connection-instead-of-re-using-it/m-p/703963#M116421</guid>
      <dc:creator>onlineops</dc:creator>
      <dc:date>2024-11-08T22:37:12Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk HEC closes connection instead of re-using it</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-HEC-closes-connection-instead-of-re-using-it/m-p/703992#M116425</link>
      <description>&lt;P&gt;Interesting find. It's inconsistent with the docs so it calls for a support case or at least a docs feedback.&lt;/P&gt;</description>
      <pubDate>Sat, 09 Nov 2024 07:19:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-HEC-closes-connection-instead-of-re-using-it/m-p/703992#M116425</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-11-09T07:19:45Z</dc:date>
    </item>
  </channel>
</rss>

