{"action":"opened","issue":{"url":"https://api.github.com/repos/mikedilger/formdata/issues/3","labels_url":"https://api.github.com/repos/mikedilger/formdata/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/mikedilger/formdata/issues/3/comments","events_url":"https://api.github.com/repos/mikedilger/formdata/issues/3/events","html_url":"https://github.com/mikedilger/formdata/issues/3","id":87192397,"number":3,"title":"rfc2231 encoding of header attribute values","user":{"login":"mikedilger","id":1669069,"avatar_url":"https://avatars.githubusercontent.com/u/1669069?v=3","gravatar_id":"","url":"https://api.github.com/users/mikedilger","html_url":"https://github.com/mikedilger","followers_url":"https://api.github.com/users/mikedilger/followers","following_url":"https://api.github.com/users/mikedilger/following{/other_user}","gists_url":"https://api.github.com/users/mikedilger/gists{/gist_id}","starred_url":"https://api.github.com/users/mikedilger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikedilger/subscriptions","organizations_url":"https://api.github.com/users/mikedilger/orgs","repos_url":"https://api.github.com/users/mikedilger/repos","events_url":"https://api.github.com/users/mikedilger/events{/privacy}","received_events_url":"https://api.github.com/users/mikedilger/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-06-11T03:11:24Z","updated_at":"2015-06-11T03:11:24Z","closed_at":null,"body":"Strictly speaking, Content-Disposition headers could have their attribute values encoded according to RFC 2231.   Most of this was intended for E-Mail headers, not HTTP multipart/form-data headers.  However, it's possible.\r\n\r\nI've run tests with long filenames with unicode characters, and even ie6 doesn't do any encoding, and the characters come through to UTF-8 just fine.\r\n\r\nSo I'm opening and then closing this issue.\r\n"}}