<?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: No HTTP response from Splunk when sending data in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/No-HTTP-response-from-Splunk-when-sending-data/m-p/127678#M26248</link>
    <description>&lt;P&gt;A TCP input, is simply that. It is a lower level than HTTP. A tool like &lt;A href="http://nc110.sourceforge.net/"&gt;netcat&lt;/A&gt; is more appropriate for testing sending data over TCP.&lt;/P&gt;

&lt;P&gt;However it looks like you're attempting to use the &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/RESTREF/RESTinput#receivers.2Fsimple"&gt;Splunk REST API&lt;/A&gt; to send data. This goes over the Splunk management port (By default your URL should be: &lt;CODE&gt;&lt;A href="https://yourSplunkIndexer:8089/services/receivers/simple" target="test_blank"&gt;https://yourSplunkIndexer:8089/services/receivers/simple&lt;/A&gt;&lt;/CODE&gt; ) It's been a while since I've played with the REST API to send data, but you may or may not need to authenticate for this endpoint as well.&lt;/P&gt;</description>
    <pubDate>Tue, 26 May 2015 18:09:51 GMT</pubDate>
    <dc:creator>acharlieh</dc:creator>
    <dc:date>2015-05-26T18:09:51Z</dc:date>
    <item>
      <title>No HTTP response from Splunk when sending data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/No-HTTP-response-from-Splunk-when-sending-data/m-p/127677#M26247</link>
      <description>&lt;P&gt;All,&lt;/P&gt;

&lt;P&gt;I'm trying to curl data to my Splunk indexer. The data is getting there, but I'm never receiving a response from Splunk that the data was received. This is causing issues, since I can't tell if the data was forwarded correctly. I receive a response from Splunk when I issue POSTs for searches, so this is NOT a connection issue.&lt;/P&gt;

&lt;P&gt;Here is the curl command I'm issuing to a TCP enabled port. Like I say, the data is getting to Splunk, but I don't receive any response. Why might this be?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;curl -k "http://MySplunkIndexer:515/services/receivers/simple" -d "Testkey=TestValue"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 26 May 2015 17:22:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/No-HTTP-response-from-Splunk-when-sending-data/m-p/127677#M26247</guid>
      <dc:creator>bruceclarke</dc:creator>
      <dc:date>2015-05-26T17:22:08Z</dc:date>
    </item>
    <item>
      <title>Re: No HTTP response from Splunk when sending data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/No-HTTP-response-from-Splunk-when-sending-data/m-p/127678#M26248</link>
      <description>&lt;P&gt;A TCP input, is simply that. It is a lower level than HTTP. A tool like &lt;A href="http://nc110.sourceforge.net/"&gt;netcat&lt;/A&gt; is more appropriate for testing sending data over TCP.&lt;/P&gt;

&lt;P&gt;However it looks like you're attempting to use the &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/RESTREF/RESTinput#receivers.2Fsimple"&gt;Splunk REST API&lt;/A&gt; to send data. This goes over the Splunk management port (By default your URL should be: &lt;CODE&gt;&lt;A href="https://yourSplunkIndexer:8089/services/receivers/simple" target="test_blank"&gt;https://yourSplunkIndexer:8089/services/receivers/simple&lt;/A&gt;&lt;/CODE&gt; ) It's been a while since I've played with the REST API to send data, but you may or may not need to authenticate for this endpoint as well.&lt;/P&gt;</description>
      <pubDate>Tue, 26 May 2015 18:09:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/No-HTTP-response-from-Splunk-when-sending-data/m-p/127678#M26248</guid>
      <dc:creator>acharlieh</dc:creator>
      <dc:date>2015-05-26T18:09:51Z</dc:date>
    </item>
  </channel>
</rss>

