<?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: Can Splunk Accept Cookies With Colon Embedded? in Security</title>
    <link>https://community.splunk.com/t5/Security/Can-Splunk-Accept-Cookies-With-Colon-Embedded/m-p/15377#M401</link>
    <description>&lt;P&gt;We had a similar issue. Not sure if the spec changed from when our cookie was made? But we apparently never noticed the issue because we were not fully qualifying the address when going to splunk login page. Meaning that our site-wide single sign on cookies where not being applied. The long term solution is to fix any cookies you might be submitting to the interface.&lt;/P&gt;</description>
    <pubDate>Mon, 26 Sep 2011 15:31:44 GMT</pubDate>
    <dc:creator>zachvida</dc:creator>
    <dc:date>2011-09-26T15:31:44Z</dc:date>
    <item>
      <title>Can Splunk Accept Cookies With Colon Embedded?</title>
      <link>https://community.splunk.com/t5/Security/Can-Splunk-Accept-Cookies-With-Colon-Embedded/m-p/15375#M399</link>
      <description>&lt;P&gt;If I have cookies set in my domain and when I try to connect via FQDN, I get:
&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;
"400 Bad Request" &lt;/P&gt;&lt;P&gt;   Illegal cookie name DACS:DGINET::DGI:manon
&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;
&lt;/P&gt;&lt;P&gt;
After investigating on the web, I've found the following &lt;/P&gt;

&lt;P&gt;&lt;A href="http://www.cherrypy.org/ticket/868" rel="nofollow"&gt;www.cherrypy.org/868&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;where it is explained that Cookies with colon are considered not compatible with RFC 2965. 
&lt;/P&gt;&lt;P&gt; 
Firefox and IE and other applications can accept this format, is there a way to make it working in Splunk as well? 
&lt;/P&gt;&lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Mon, 14 Jun 2010 18:05:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Can-Splunk-Accept-Cookies-With-Colon-Embedded/m-p/15375#M399</guid>
      <dc:creator>mzorzi</dc:creator>
      <dc:date>2010-06-14T18:05:39Z</dc:date>
    </item>
    <item>
      <title>Re: Can Splunk Accept Cookies With Colon Embedded?</title>
      <link>https://community.splunk.com/t5/Security/Can-Splunk-Accept-Cookies-With-Colon-Embedded/m-p/15376#M400</link>
      <description>&lt;P&gt;This matter has been evaluated by our UI dev team and I will take the liberty to post their response here :&lt;/P&gt;

&lt;P&gt;"Fixing cherrypy to accept bad cookies would require that we stop using the standard python cookie library and write our own. The only fix is to replace cherrypy's cookie handler and write (or use) another handler. Unfortunately there isn't a quick patch to be had."&lt;/P&gt;</description>
      <pubDate>Sat, 11 Dec 2010 02:52:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Can-Splunk-Accept-Cookies-With-Colon-Embedded/m-p/15376#M400</guid>
      <dc:creator>hexx</dc:creator>
      <dc:date>2010-12-11T02:52:44Z</dc:date>
    </item>
    <item>
      <title>Re: Can Splunk Accept Cookies With Colon Embedded?</title>
      <link>https://community.splunk.com/t5/Security/Can-Splunk-Accept-Cookies-With-Colon-Embedded/m-p/15377#M401</link>
      <description>&lt;P&gt;We had a similar issue. Not sure if the spec changed from when our cookie was made? But we apparently never noticed the issue because we were not fully qualifying the address when going to splunk login page. Meaning that our site-wide single sign on cookies where not being applied. The long term solution is to fix any cookies you might be submitting to the interface.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Sep 2011 15:31:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Can-Splunk-Accept-Cookies-With-Colon-Embedded/m-p/15377#M401</guid>
      <dc:creator>zachvida</dc:creator>
      <dc:date>2011-09-26T15:31:44Z</dc:date>
    </item>
  </channel>
</rss>

