{"action":"closed","issue":{"url":"https://api.github.com/repos/Microsoft/cordova-simulate/issues/215","repository_url":"https://api.github.com/repos/Microsoft/cordova-simulate","labels_url":"https://api.github.com/repos/Microsoft/cordova-simulate/issues/215/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/cordova-simulate/issues/215/comments","events_url":"https://api.github.com/repos/Microsoft/cordova-simulate/issues/215/events","html_url":"https://github.com/Microsoft/cordova-simulate/issues/215","id":194113824,"number":215,"title":"VS2017 RC: remote proxy not working: 'socket hang up'","user":{"login":"nodefish","id":16632464,"avatar_url":"https://avatars.githubusercontent.com/u/16632464?v=3","gravatar_id":"","url":"https://api.github.com/users/nodefish","html_url":"https://github.com/nodefish","followers_url":"https://api.github.com/users/nodefish/followers","following_url":"https://api.github.com/users/nodefish/following{/other_user}","gists_url":"https://api.github.com/users/nodefish/gists{/gist_id}","starred_url":"https://api.github.com/users/nodefish/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nodefish/subscriptions","organizations_url":"https://api.github.com/users/nodefish/orgs","repos_url":"https://api.github.com/users/nodefish/repos","events_url":"https://api.github.com/users/nodefish/events{/privacy}","received_events_url":"https://api.github.com/users/nodefish/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2016-12-07T17:28:39Z","updated_at":"2016-12-15T12:10:32Z","closed_at":"2016-12-15T12:10:32Z","body":"Hello,\r\n\r\nI just migrated a VS Community 2015 TACO app to VS Community 2017 RC. According to [this link](https://taco.visualstudio.com/en-us/docs/vs-taco-2017-cordova-simulate/#supported-plugins), the same kind of proxy as the one from the 'Ripple emulator' is provided in cordova-simulate.\r\n\r\nHowever, I can't get my app to send/receive requests to my remote development server. They time out and result in `502 - Bad Gateway`. If I look at the response in Chrome's network pane, the failed requests have this message under the response preview: `Error: socket hang up`.\r\n\r\nI can't seem to find any proxy configuration so I'm stumped. Please advise, thanks."}}
{"actor":{"display_login":"nodefish"}}