{"action":"closed","issue":{"url":"https://api.github.com/repos/kennethreitz/requests/issues/2725","labels_url":"https://api.github.com/repos/kennethreitz/requests/issues/2725/labels{/name}","comments_url":"https://api.github.com/repos/kennethreitz/requests/issues/2725/comments","events_url":"https://api.github.com/repos/kennethreitz/requests/issues/2725/events","html_url":"https://github.com/kennethreitz/requests/issues/2725","id":101046018,"number":2725,"title":"Requests.put blocking on Windows (Tika-Python)","user":{"login":"chrismattmann","id":395887,"avatar_url":"https://avatars.githubusercontent.com/u/395887?v=3","gravatar_id":"","url":"https://api.github.com/users/chrismattmann","html_url":"https://github.com/chrismattmann","followers_url":"https://api.github.com/users/chrismattmann/followers","following_url":"https://api.github.com/users/chrismattmann/following{/other_user}","gists_url":"https://api.github.com/users/chrismattmann/gists{/gist_id}","starred_url":"https://api.github.com/users/chrismattmann/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chrismattmann/subscriptions","organizations_url":"https://api.github.com/users/chrismattmann/orgs","repos_url":"https://api.github.com/users/chrismattmann/repos","events_url":"https://api.github.com/users/chrismattmann/events{/privacy}","received_events_url":"https://api.github.com/users/chrismattmann/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":52,"created_at":"2015-08-14T16:22:14Z","updated_at":"2015-10-24T14:37:16Z","closed_at":"2015-10-24T14:37:16Z","body":"Over in the [Apache Tika Python Port](http://github.com/chrismattmann/tika-python/) I'm noticing in [tika-python#44](http://github.com/chrismattmann/tika-python/issues/44) and in [tika-python#58](http://github.com/chrismattmann/tika-python/issues/58) some odd behavior with requests on Python 2.7.9. For whatever reason, when using a file handle and putting it with requests.put it blocks and blocks until finally it gets (correctly) a BadStatusLine back after a timeout. Anyone else seen this?"}}