{"action":"closed","issue":{"url":"https://api.github.com/repos/nodejs/http-parser/issues/448","repository_url":"https://api.github.com/repos/nodejs/http-parser","labels_url":"https://api.github.com/repos/nodejs/http-parser/issues/448/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/http-parser/issues/448/comments","events_url":"https://api.github.com/repos/nodejs/http-parser/issues/448/events","html_url":"https://github.com/nodejs/http-parser/issues/448","id":374652057,"node_id":"MDU6SXNzdWUzNzQ2NTIwNTc=","number":448,"title":"Cannot parse non-alphanumeric characters when not encoded","user":{"login":"exiaohao","id":8476007,"node_id":"MDQ6VXNlcjg0NzYwMDc=","avatar_url":"https://avatars2.githubusercontent.com/u/8476007?v=4","gravatar_id":"","url":"https://api.github.com/users/exiaohao","html_url":"https://github.com/exiaohao","followers_url":"https://api.github.com/users/exiaohao/followers","following_url":"https://api.github.com/users/exiaohao/following{/other_user}","gists_url":"https://api.github.com/users/exiaohao/gists{/gist_id}","starred_url":"https://api.github.com/users/exiaohao/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/exiaohao/subscriptions","organizations_url":"https://api.github.com/users/exiaohao/orgs","repos_url":"https://api.github.com/users/exiaohao/repos","events_url":"https://api.github.com/users/exiaohao/events{/privacy}","received_events_url":"https://api.github.com/users/exiaohao/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-10-27T14:39:26Z","updated_at":"2018-10-28T02:03:51Z","closed_at":"2018-10-28T02:03:51Z","author_association":"NONE","body":"[envoy](https://github.com/envoyproxy/envoy) (which use ***http-parser*** as parser) cannot parse  unurlencoded non-alphanumeric characters (e.g. Chinese characters) correctly when process HTTP requests with it.\r\nI know http standard does not allow double-byte characters in requests, it must be urlencoded. But we cannot control clients' behaviors and mandatory require them follow this standard. Even some unreasonable says that nginx have strong compatibility why envoy and http-parser can't?\r\nIs there any way to compatible it?\r\n\r\nrelated issue in envoy: https://github.com/envoyproxy/envoy/issues/4854"}}
{"actor":{"display_login":"indutny"}}