CookieError: Illegal key value: EBox::Auth_EBox

[anarquist]

I don't know if this is a bug with sabnzbd or eBox (http://ebox-platform.com/).

Platform:
Client: Firefox 3.5.1 (and previous), Windows XP Pro SP3 32bit
Server: sabnzbdplus 0.4.9-0ubuntu1 on Ubuntu 9.04 32bit

Recreate:
Visit eBox (i.e. https://ubuntu:15000/) and log in.  Then try to open sabnzbd+ (i.e. http://ubuntu/sabnzbd/) and get error:

500 Internal error

The server encountered an unexpected condition which prevented it from fulfilling the request.

Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/cherrypy/_cphttptools.py", line 104, in _run
    self.processHeaders()
  File "/var/lib/python-support/python2.5/cherrypy/_cphttptools.py", line 203, in processHeaders
    self.simple_cookie.load(value)
  File "/usr/lib/python2.5/Cookie.py", line 619, in load
    self.__ParseString(rawdata)
  File "/usr/lib/python2.5/Cookie.py", line 650, in __ParseString
    self.__set(K, rval, cval)
  File "/usr/lib/python2.5/Cookie.py", line 572, in __set
    M.set(key, real_value, coded_value)
  File "/usr/lib/python2.5/Cookie.py", line 451, in set
    raise CookieError("Illegal key value: %s" % key)
CookieError: Illegal key value: EBox::Auth_EBox

Powered by CherryPy 2.3.0


Workaround: Clear Private Data (including cookies) in Firefox, then it works fine.

[amerrykan]

I just installed eBox Platform 1.2 (using their modified Ubuntu ISO), I installed sabnzbd+ from the official/unofficial Ubuntu PPA, and after my usual two hour wrestle with sabnzbd+'s webserver to get it to actually answer any incoming requests, I reproduced this issue.  This is logged in cherrypy.log:

Code: Select all

26/Jul/2009:23:26:01 HTTP INFO Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/cherrypy/_cphttptools.py", line 94, in _run
    self.processHeaders()
  File "/var/lib/python-support/python2.5/cherrypy/_cphttptools.py", line 187, in processHeaders
    self.simple_cookie.load(value)
  File "/usr/lib/python2.5/Cookie.py", line 619, in load
    self.__ParseString(rawdata)
  File "/usr/lib/python2.5/Cookie.py", line 650, in __ParseString
    self.__set(K, rval, cval)
  File "/usr/lib/python2.5/Cookie.py", line 572, in __set
    M.set(key, real_value, coded_value)
  File "/usr/lib/python2.5/Cookie.py", line 451, in set
    raise CookieError("Illegal key value: %s" % key)
CookieError: Illegal key value: EBox::Auth_EBox

[stalks]

I am also suffering from this same bug with sabnzbd.

sabznbd needs to play nicely with *all* available cookies. I beleive sab expects to be the lone use of cookies, but if the domain is shared with other sites and sab comes accross cookies it doesn't expect, or are in a different format, then the web page dumps.

Code: Select all

500 Internal Server Error

The server encountered an unexpected condition which prevented it from fulfilling the request.

Traceback (most recent call last):
  File "/usr/share/sabnzbdplus/cherrypy/_cprequest.py", line 593, in respond
    self.process_headers()
  File "/usr/share/sabnzbdplus/cherrypy/_cprequest.py", line 661, in process_headers
    self.cookie.load(value)
  File "/usr/lib/python2.6/Cookie.py", line 627, in load
    self.__ParseString(rawdata)
  File "/usr/lib/python2.6/Cookie.py", line 660, in __ParseString
    self.__set(K, rval, cval)
  File "/usr/lib/python2.6/Cookie.py", line 580, in __set
    M.set(key, real_value, coded_value)
  File "/usr/lib/python2.6/Cookie.py", line 455, in set
    raise CookieError("Illegal key value: %s" % key)
CookieError: Illegal key value: cb_/zabbix/graphs.php_parts

This happens when Zabbix cookies are present. I have also had the same issue with MythWeb in the past when it hosted on the same domain. The only work around at present for me is to manually remove the offending cookie, however I then lose settings in Zabbix which is annoying.

Request higher priority for this bug?

[shypike]

It's a problem that hits few people, so priority is lower than for other problems.
I agree that it's not properly handled.

There is a work-around.
If you let one service run on localhost and the other on 127.0.0.1 and maybe even one on [::1],
the cookies will no longer collide.
In fact, you can even define a bunch of extra aliasses for localhost.

Yes, it needs to be fixed. But it won't be in the short term.
I've experimented with a specific domain setting in the cookies,
but it doesn't work as expected. So it might be a lot of work.