Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

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

Open
IBMRob opened this issue Jan 27, 2016 · 3 comments
Open

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

IBMRob opened this issue Jan 27, 2016 · 3 comments

Comments

@IBMRob
Copy link

IBMRob commented Jan 27, 2016

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
Copy link

bbence84 commented Feb 2, 2016

Same here. Any suggestions?

@simonbernard
Copy link

I had the same problem and raised an issue to node-tunnel.
koichik/node-tunnel#12

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

@chriskea
Copy link

Same issue, the fix mentioned above resolved it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants