<?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: [Fatal Error] :1:1: Content is not allowed in prolog. in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/Fatal-Error-1-1-Content-is-not-allowed-in-prolog/m-p/18270#M114</link>
    <description>&lt;P&gt;Thank you SO MUCH for the question and the answer. Just made my day.&lt;/P&gt;

&lt;P&gt;So I suggest you accept the answer as it give the solution (was having the same problem, switching to port 8089 solved it)&lt;/P&gt;</description>
    <pubDate>Mon, 15 Apr 2013 14:40:19 GMT</pubDate>
    <dc:creator>guilhem</dc:creator>
    <dc:date>2013-04-15T14:40:19Z</dc:date>
    <item>
      <title>[Fatal Error] :1:1: Content is not allowed in prolog.</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Fatal-Error-1-1-Content-is-not-allowed-in-prolog/m-p/18268#M112</link>
      <description>&lt;P&gt;Hi, using splunk-sdk-java is being developed.&lt;BR /&gt;
 Login method call in development of the following error has occurred.&lt;/P&gt;

&lt;P&gt;POST &lt;A href="https://192.168.225.128:8000/services/auth/login"&gt;https://192.168.225.128:8000/services/auth/login&lt;/A&gt; =&amp;gt; [Fatal Error]: 1:1: Content is not allowed in prolog.&lt;BR /&gt;
 com.splunk.HttpException: HTTP 400&lt;BR /&gt;
 at com.splunk.HttpException.create (HttpException.java: 59)&lt;BR /&gt;
 at com.splunk.HttpService.send (HttpService.java: 366)&lt;BR /&gt;
 at com.splunk.Service.send (Service.java: 644)&lt;BR /&gt;
 at com.splunk.HttpService.post (HttpService.java: 226)&lt;BR /&gt;
 at com.splunk.Service.login (Service.java: 556)&lt;BR /&gt;
 at com.splunk.ServiceTest.main (ServiceTest.java: 321)&lt;/P&gt;

&lt;P&gt;What would I have to solve please answer.&lt;/P&gt;

&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Apr 2012 14:24:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Fatal-Error-1-1-Content-is-not-allowed-in-prolog/m-p/18268#M112</guid>
      <dc:creator>surren</dc:creator>
      <dc:date>2012-04-04T14:24:31Z</dc:date>
    </item>
    <item>
      <title>Re: [Fatal Error] :1:1: Content is not allowed in prolog.</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Fatal-Error-1-1-Content-is-not-allowed-in-prolog/m-p/18269#M113</link>
      <description>&lt;P&gt;wrong URL. you can't sent REST calls to SplunkWeb. try port 8089.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Apr 2012 15:13:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Fatal-Error-1-1-Content-is-not-allowed-in-prolog/m-p/18269#M113</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2012-04-04T15:13:58Z</dc:date>
    </item>
    <item>
      <title>Re: [Fatal Error] :1:1: Content is not allowed in prolog.</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Fatal-Error-1-1-Content-is-not-allowed-in-prolog/m-p/18270#M114</link>
      <description>&lt;P&gt;Thank you SO MUCH for the question and the answer. Just made my day.&lt;/P&gt;

&lt;P&gt;So I suggest you accept the answer as it give the solution (was having the same problem, switching to port 8089 solved it)&lt;/P&gt;</description>
      <pubDate>Mon, 15 Apr 2013 14:40:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Fatal-Error-1-1-Content-is-not-allowed-in-prolog/m-p/18270#M114</guid>
      <dc:creator>guilhem</dc:creator>
      <dc:date>2013-04-15T14:40:19Z</dc:date>
    </item>
  </channel>
</rss>

