<?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 [EXCEPTION] HTTP 200 OK in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/EXCEPTION-HTTP-200-OK/m-p/152474#M2089</link>
    <description>&lt;P&gt;I have setup splunk sdk and I am trying to run splunk searches.&lt;BR /&gt;
For any search including the saved searches I get this result ==&amp;gt; [EXCEPTION] HTTP 200 OK.&lt;/P&gt;

&lt;P&gt;I am using splunk for the first time, any help would be appreciated.&lt;/P&gt;

&lt;P&gt;Thanks&lt;BR /&gt;
Sharath Kumar&lt;/P&gt;</description>
    <pubDate>Wed, 17 Dec 2014 09:21:56 GMT</pubDate>
    <dc:creator>sharathemerian</dc:creator>
    <dc:date>2014-12-17T09:21:56Z</dc:date>
    <item>
      <title>[EXCEPTION] HTTP 200 OK</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/EXCEPTION-HTTP-200-OK/m-p/152474#M2089</link>
      <description>&lt;P&gt;I have setup splunk sdk and I am trying to run splunk searches.&lt;BR /&gt;
For any search including the saved searches I get this result ==&amp;gt; [EXCEPTION] HTTP 200 OK.&lt;/P&gt;

&lt;P&gt;I am using splunk for the first time, any help would be appreciated.&lt;/P&gt;

&lt;P&gt;Thanks&lt;BR /&gt;
Sharath Kumar&lt;/P&gt;</description>
      <pubDate>Wed, 17 Dec 2014 09:21:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/EXCEPTION-HTTP-200-OK/m-p/152474#M2089</guid>
      <dc:creator>sharathemerian</dc:creator>
      <dc:date>2014-12-17T09:21:56Z</dc:date>
    </item>
    <item>
      <title>Re: [EXCEPTION] HTTP 200 OK</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/EXCEPTION-HTTP-200-OK/m-p/152475#M2090</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Yes. i also got the same issue with splunk sdk api. able to resolve it with exec_mode as blocking in creating a job element.&lt;/P&gt;

&lt;P&gt;More understanding : &lt;A href="http://www.drtuts.com/http-200-ok-response-in-splunk-api-php/"&gt;http://www.drtuts.com/http-200-ok-response-in-splunk-api-php/&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;thanks,&lt;BR /&gt;
vijay,Hi Sharath,&lt;/P&gt;

&lt;P&gt;Yes. I also faced same issues with splunk sdk api. &lt;/P&gt;</description>
      <pubDate>Mon, 29 Feb 2016 15:16:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/EXCEPTION-HTTP-200-OK/m-p/152475#M2090</guid>
      <dc:creator>vijayaragavans</dc:creator>
      <dc:date>2016-02-29T15:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: [EXCEPTION] HTTP 200 OK</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/EXCEPTION-HTTP-200-OK/m-p/152476#M2091</link>
      <description>&lt;P&gt;Not a direct answer to the bug, but an alternative to making the exec_mode=blocking.&lt;/P&gt;

&lt;P&gt;I hadn't experienced the issue in the last 7 years using exec_mode=normal, recently I've begun migrating to PHP 7.1 which is when I first noticed the bug and it occurred every request. During debugging sessions, the bug would only occur some of the times, I noticed when I was digging into the create method, the request would succeed.&lt;/P&gt;

&lt;P&gt;I placed a one second sleep after the create and before my isDone loop and the request succeeds. I haven't looked into the cause of the bug itself, but I suspect at least for myself when running under PHP 5.3.8 the processing is that much slower than PHP 7 that it was enough of a delay to not trigger the bug. I would wager that the job in splunk hasn't been fully created by the time the script was looking for a status.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Nov 2017 21:04:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/EXCEPTION-HTTP-200-OK/m-p/152476#M2091</guid>
      <dc:creator>twhitehead</dc:creator>
      <dc:date>2017-11-02T21:04:29Z</dc:date>
    </item>
  </channel>
</rss>

