{"action":"created","issue":{"url":"https://api.github.com/repos/wallabag/ios-app/issues/68","repository_url":"https://api.github.com/repos/wallabag/ios-app","labels_url":"https://api.github.com/repos/wallabag/ios-app/issues/68/labels{/name}","comments_url":"https://api.github.com/repos/wallabag/ios-app/issues/68/comments","events_url":"https://api.github.com/repos/wallabag/ios-app/issues/68/events","html_url":"https://github.com/wallabag/ios-app/issues/68","id":203428575,"number":68,"title":"Form-Encoded Body Parameter","user":{"login":"LordEidi","id":2028898,"avatar_url":"https://avatars.githubusercontent.com/u/2028898?v=3","gravatar_id":"","url":"https://api.github.com/users/LordEidi","html_url":"https://github.com/LordEidi","followers_url":"https://api.github.com/users/LordEidi/followers","following_url":"https://api.github.com/users/LordEidi/following{/other_user}","gists_url":"https://api.github.com/users/LordEidi/gists{/gist_id}","starred_url":"https://api.github.com/users/LordEidi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/LordEidi/subscriptions","organizations_url":"https://api.github.com/users/LordEidi/orgs","repos_url":"https://api.github.com/users/LordEidi/repos","events_url":"https://api.github.com/users/LordEidi/events{/privacy}","received_events_url":"https://api.github.com/users/LordEidi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-01-26T17:05:50Z","updated_at":"2017-01-27T10:59:32Z","closed_at":null,"body":"Hi\r\n\r\nWhile reading the source to your app I noticed, that your OAuth 2 authorisation with the bearer token makes use of form-encoded body parameters. Looking at the [RFC 6750 section 2](https://tools.ietf.org/html/rfc6750#section-2.2) it states that a clients should make authenticated requests with a bearer token using the \"Authorization\" request header field with the \"Bearer\" HTTP authorization scheme. And that when instead using form-encoded body parameters the content to be encoded in the entity-body must consist entirely of ASCII characters. Your app mostly uses form-encoded body parameters. Unfortunately the Alamofire framework uses UTF-8 in form-encoded bodies, see [line 66ff ParameterEncoding](https://github.com/Alamofire/Alamofire/blob/master/Source/ParameterEncoding.swift). \r\n\r\nTo make this short. Is there a special reason why you are using form-encoded body parameters vs. request header field? And if not, would you accept a pull request changing from body parameter to request header field?\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/wallabag/ios-app/issues/comments/275640547","html_url":"https://github.com/wallabag/ios-app/issues/68#issuecomment-275640547","issue_url":"https://api.github.com/repos/wallabag/ios-app/issues/68","id":275640547,"user":{"login":"bourvill","id":295272,"avatar_url":"https://avatars.githubusercontent.com/u/295272?v=3","gravatar_id":"","url":"https://api.github.com/users/bourvill","html_url":"https://github.com/bourvill","followers_url":"https://api.github.com/users/bourvill/followers","following_url":"https://api.github.com/users/bourvill/following{/other_user}","gists_url":"https://api.github.com/users/bourvill/gists{/gist_id}","starred_url":"https://api.github.com/users/bourvill/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bourvill/subscriptions","organizations_url":"https://api.github.com/users/bourvill/orgs","repos_url":"https://api.github.com/users/bourvill/repos","events_url":"https://api.github.com/users/bourvill/events{/privacy}","received_events_url":"https://api.github.com/users/bourvill/received_events","type":"User","site_admin":false},"created_at":"2017-01-27T10:59:32Z","updated_at":"2017-01-27T10:59:32Z","body":"Thank for feedback, leave me time to watch"}}
{"actor":{"display_login":"bourvill"}}