Opened 16 years ago
Closed 15 years ago
#7287 closed defect (duplicate)
'ascii' codec can't decode byte 0xe5 in position 0: ordinal not in range(128)
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | i18n | Version: | 0.11.2.1 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
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)
Attachments (1)
Change History (6)
by , 16 years ago
comment:1 by , 16 years ago
Description: | modified (diff) |
---|
Are you trying to register a username that is not plain ASCII?
comment:2 by , 16 years ago
Keywords: | needinfo added |
---|
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?
comment:3 by , 16 years ago
Description: | modified (diff) |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
comment:4 by , 15 years ago
Component: | general → i18n |
---|---|
Keywords: | needinfo removed |
Resolution: | duplicate |
Severity: | critical → normal |
Status: | closed → reopened |
Version: | 0.10.4 → 0.11.2.1 |
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.
comment:5 by , 15 years ago
Resolution: | → duplicate |
---|---|
Status: | reopened → closed |
Yes, so that's definitely a duplicate of #6318, i.e. non-ascii login names are simply not supported yet.
'ascii' codec can't decode byte 0xe5 in position 0: ordinal not in range(128)