Github user iilyak commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/109#issuecomment-199779143
@kxepal Supporting utf-8 is a very valid concern. Do we actually support
it? It doesn't seem possible to transmit utf-8 in a http header. We use basic
auth which is based on headers. There is a new
[RFC7617](https://datatracker.ietf.org/doc/rfc7617/) which is going to support
utf-8. But currently it is not supported. Therefore I do believe that we
shouldn't have any utf-8 users in the wild. As utf-8 support is slowly coming
maybe we should consider userid validation on couch side to sanitize user's
input before it became a problem. The proposed
[RFC7613](https://datatracker.ietf.org/doc/rfc7613/?include_text=1) defines
what can be in a userid and what shouldn't be there.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
