Lets track it for both: it might not really be an issue that cms has
converted from str to utf-8 for most things, just that mod_wsgi is
enforcing what comes across in the header. I have a patch submitted
alrady that mitigates the Keystone problem:
https://review.openstack.org/#/c/90476/ I'll make sure it gets linked
here.
** Summary changed:
- mod_wsgi exception processing UTF-F Header
+ mod_wsgi exception processing UTF-8 Header
** Also affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1312971
Title:
mod_wsgi exception processing UTF-8 Header
Status in OpenStack Identity (Keystone):
New
Status in Python client library for Keystone:
Triaged
Bug description:
Using master version of python-keystoneclient (not yet released)
gives the following error when running with Keystone in Apache HTTPD
and requesting a V3 Token
[Fri Apr 25 18:28:14.775659 2014] [:error] [pid 5075] [remote
10.10.63.250:2982] mod_wsgi (pid=5075): Exception occurred processing WSGI
script '/var/www/cgi-bin/keystone/main'.
[Fri Apr 25 18:28:14.775801 2014] [:error] [pid 5075] [remote
10.10.63.250:2982] TypeError: expected byte string object for header value,
value of type unicode found
Its due to the utf-8 encoding in keystoneclient/common/cms.py which
is making the PKI token Unicode instead of str.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1312971/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
