Open ghost opened 14 years ago
Does that work? I think there's more work to be done to support non-ascii paths than just redefining the regex character classes. For example, it is my understanding that browsers may send non-ascii paths as percent-encoded utf-8, and tornado does not currently make any attempt to decode them.
I'm not sure it works well.
I'm deprecated normal name/Unicode String as key/argument
/obj_type/name
I'm use uuid instead,
/obj_type/uuid
From recent discussion on the mailing list: The rules for decoding these urls correctly are complicated and are given in RFC 3987: http://tools.ietf.org/html/rfc3987#section-3.2. We need an implementation of this algorithm and a way for applications to opt in to it (since it would be slow and it is common practice even for non-english sites to restrict the routing-critical part of their url paths to ascii).
Please add unicode URLSpec support.
Patch: