search

salesforce / global-tunnel

Deprecated, please see:
https://github.com/np-maintain/global-tunnel
BSD 3-Clause "New" or "Revised" License
48 stars 48 forks source link

throw new TypeError('Request path contains unescaped characters.'); #13

Open IBMRob opened 8 years ago

IBMRob commented 8 years ago

Without the global-tunnel my code connects directly to the endpoint fine but when I enable global-tunnel via a MockServer proxy then I am getting the following error:

_http_client.js:54 throw new TypeError('Request path contains unescaped characters.'); ^

TypeError: Request path contains unescaped characters. at new ClientRequest (_http_client.js:54:11) at TunnelingAgent.exports.request (http.js:31:10) at TunnelingAgent.createSocket (/home/test/NodeApps/node_modules/global-tunnel/node_modules/tunnel/lib/tunnel.js:116:25) at TunnelingAgent.createSecureSocket as createSocket at TunnelingAgent.addRequest (/home/test/NodeApps/node_modules/global-tunnel/node_modules/tunnel/lib/tunnel.js:80:8) at new ClientRequest (_http_client.js:139:16) at Object.exports.request (http.js:31:10) at Object.globalTunnel._defaultedAgentRequest (/home/test/NodeApps/node_modules/global-tunnel/index.js:211:38) at Object.exports.request (https.js:173:15) at Object.globalTunnel._defaultedAgentRequest (/home/test/NodeApps/node_modules/global-tunnel/index.js:211:38)

bbence84 commented 8 years ago

Same here. Any suggestions?

simonbernard commented 8 years ago

I had the same problem and raised an issue to node-tunnel. https://github.com/koichik/node-tunnel/issues/12

It seems that dependency to node-tunnel should be updated to '0.0.4`.

chriskea commented 8 years ago

Same issue, the fix mentioned above resolved it.