'ascii' codec can't decode byte 0xe5 in position 0: ordinal not in range(128)

[patria@…]

Oops… Trac detected an internal error:

If you think this really should work and you can reproduce it, you should consider reporting this problem to the Trac team.

Go to ​http://trac.edgewall.org/ and create a new ticket where you describe the problem, how to reproduce it. Don't forget to include the Python traceback found below.

TracGuide — The Trac User and Administration Guide Python Traceback

Traceback (most recent call last):
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 406, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 237, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/local/lib/python2.4/site-packages/TracAccountManager-0.1.2.egg/acct_mgr/web_ui.py", line 117, in process_request
  File "/usr/local/lib/python2.4/site-packages/TracAccountManager-0.1.2.egg/acct_mgr/web_ui.py", line 124, in _do_create
  File "/usr/local/lib/python2.4/site-packages/TracAccountManager-0.1.2.egg/acct_mgr/api.py", line 85, in has_user
  File "/usr/local/lib/python2.4/site-packages/TracAccountManager-0.1.2.egg/acct_mgr/htfile.py", line 41, in has_user
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe5 in position 0: ordinal not in range(128)

[patria@…]

'ascii' codec can't decode byte 0xe5 in position 0: ordinal not in range(128)

[Noah Kantrowitz]

Are you trying to register a username that is not plain ASCII?

[osimons]

In a way this looks like an 'invalid' ticket as it seems to be directly related to ​th:AccountManagerPlugin, and the ticket should be registered there.

However, depending on the actual circumstances, it may also be a 'duplicate' of #6318 as there seems to be some issues with non-ascii logins.

To repeat Noah's question: Did the login contain non-ascii characters?

[Christian Boos]

Eventually related to #6318 or #7325, but without the requested feedback it's hard to tell.

[zeljko_t@…]

I can confirm that this happens if UTF-8 is used in htdigest file.

Additional problem: is UTF-8 in htdigest supported by Apache in the first place? I could not find any information about that.

[Christian Boos]

Yes, so that's definitely a duplicate of #6318, i.e. non-ascii login names are simply not supported yet.