Refine your search:

I think this is similar to http://answers.splunk.com/questions/3602/can-splunk-accept-cookies-with-colon-embedded but not exactly.

It seems that when I have a domain wide cookie set, I can never get to splunk (if I use a fully qualified domain name to access splunk).

Even if the cookie names appear valid, I still get an error from splunk. Here is one example.


400 Bad Request

Illegal cookie name AtworkEnv

Traceback (most recent call last): File "/opt/splunk/splunk/lib/python2.6/site-packages/cherrypy/_cprequest.py", line 581, in respond self.process_headers() File "/opt/splunk/splunk/lib/python2.6/site-packages/cherrypy/_cprequest.py", line 653, in process_headers raise cherrypy.HTTPError(400, msg) HTTPError: (400, 'Illegal cookie name AtworkEnv')


The domain wide cookies are set by an ap that we have no control over (and must goto daily). Also, I must use a fully qualified domain name to access splunk (we have different domain at my work).

Has anyone found a workaround for this?

Thanks

Kevin

asked 21 Oct '10, 14:01

kkalmbach's gravatar image

kkalmbach
895
accept rate: 0%

edited 21 Dec '10, 17:28

piebob's gravatar image

piebob ♦♦
2.4k1517


3 Answers:

Bump. This just bit me again, this time with glassfish admin cookies.

This is a problem somewhere in Cookie.py.

Anyone have a little fix? Maybe something borrowed from a newer Python? I see on the tubes that this is a problem for Google Analytics, as well, as they use cookies with colons in the name.

link

answered 01 Dec '11, 08:47

vbumgarn's gravatar image

vbumgarn
6011214
accept rate: 9%

Looking at it closer, it appears there are 2 issues:

  • The first is that splunk fails with cookie names with colons in them (like the referenced issue)

  • The second is that splunk is reporting the wrong cookie name when complaining about a cookie

Not sure what we are going to do, but it would be best if splunk could handle the illegal cookie names.

link

answered 21 Oct '10, 14:11

kkalmbach's gravatar image

kkalmbach
895
accept rate: 0%

It looks like commenting out line 653 will stop the error from killing the request. I will make sure this is filed as a bug with CherryPy.

link

answered 28 Mar '11, 15:55

vbumgarner's gravatar image

vbumgarner
1.8k210
accept rate: 23%

This does not seem to work reliably. The Cookie.py stops processing (and raises the error) when it hits the first error. So if the "Cookie" header contains: good=value; b:ad=value Things are fine with that line commented out. If the value of "Cookie" is: b:ad=value; good=value Then Cookie.py stops processing and the good=value is never read in. I think we need to comment out the raise in Cookie.py

(04 Apr '11, 19:47) kkalmbach
Post your answer
toggle preview

Follow this question

Log In to enable email subscriptions

RSS:

Answers

Answers + Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×221
×104
×2

Asked: 21 Oct '10, 14:01

Seen: 1,326 times

Last updated: 01 Dec '11, 08:47

Copyright © 2005-2012 Splunk, Inc. All rights reserved.