#2438: Authentication of non-ascii user names does not work in TG 2.x
---------------------------------+------------------------------------------
Reporter: chrisz | Owner: Gustavo
Type: defect | Status: reopened
Priority: high | Milestone: 2.1
Component: TurboGears | Version: trunk
Severity: major | Resolution:
Keywords: repoze.who identity |
---------------------------------+------------------------------------------
Comment (by chrisz):
Ok, I've added accept-charset="UTF-8" to the login form now.
In fact the HTML specs say: "The default value for this attribute is the
reserved string "UNKNOWN". User agents may interpret this value as the
character encoding that was used to transmit the document containing this
FORM element."
So that behavior is not against the specs and in practice, all browsers
seem to do this, but it cannot harm to explictly set the accept-charset
attribute.
The problem is now how friendlyforms gets the information that the data is
encoded as utf-8. As Ian writes, the browser could send the encoding as
`Content-Type: application/x-www-form-urlencoded; charset=utf8`, but
browsers seldom set this. In fact, all browsers I tested sent only
`Content-Type: application/x-www-form-urlencoded`. So we must somehow
explicitely tell friendlyforms to use utf-8 as default encoding instead of
iso-8859-1 since it does not get this information from the browser.
--
Ticket URL: <http://trac.turbogears.org/ticket/2438#comment:11>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
