Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/109#issuecomment-199840399
@iilyak I would prefer json or url encoded way. Both are fine to notice
tricky bits, but each is useful for further copy-paste into some script to work
with it and both provides more-or-less readable close to real variants of
username. Plain ASCII ones will remain plain ASCII ones.
However, that could be not very friendly for the end users (admins/devops)
to work with such kind of data. Need to think about and call for more opinions
around. For instance, what tools ElasticSearch could provide to work with such
kind of encoded usernames?
---
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.
---
