Mixing
TypeError [ERR_UNESCAPED_CHARACTERS] Request path contains unescaped characters
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am working Ubuntu with incoming HTTP request with this URL: http://myIp:3000/v1/projects/list
And I get this error in terminal:
TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
at new ClientRequest (_http_client.js:127:13)
at Object.request (https.js:300:10)
at Request.start (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:751:32)
at Request.end (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:1512:10)
at end (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:564:14)
at Immediate._onImmediate (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:578:7)
at processImmediate(timers.js:632:19)
After this error node process dissapears from terminal (but still working and API response is sent properly), though I can't see its work (image attached). So the only way to interact with node process is to do something like ps aux | grep node or ps Tand manually kill process.
Assuming the error meaning I've found an appropriate code fragment where the error appears (request.js:751:32). Here it is:
try {
self.req = self.httpModule.request(reqOptions)
} catch (err) {
self.emit('error', err)
return
}
The only solution I've come to is to comment self.emit('error', err) code line, which is obviously far from best practice.
The fact is the same code works on other computers (Ubuntu, Windows) with same components versions and no error occurs. Also API endpoints like http://myIp:3000/v1/community/list work fine on all devices.
Here's my component versions:
npm — 6.5.0,
node — 11.4.0,
request — 2.88.0,
Ubuntu — 16.04 (Windows — 10)
some code fragments if needed (Express Server creation and specific route in ProjectsController):
const app = express();
app.use('/v1/projects/', ProjectsController);
const router = express.Router();
router.post('/list', function(req,res){
//logic
});
node.js express npm ubuntu-16.04
asked Jan 3 at 15:55
Hlib DerbenovHlib Derbenov
614
add a comment |
I am working Ubuntu with incoming HTTP request with this URL: http://myIp:3000/v1/projects/list
And I get this error in terminal:
TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
at new ClientRequest (_http_client.js:127:13)
at Object.request (https.js:300:10)
at Request.start (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:751:32)
at Request.end (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:1512:10)
at end (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:564:14)
at Immediate._onImmediate (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:578:7)
at processImmediate(timers.js:632:19)
After this error node process dissapears from terminal (but still working and API response is sent properly), though I can't see its work (image attached). So the only way to interact with node process is to do something like ps aux | grep node or ps Tand manually kill process.
Assuming the error meaning I've found an appropriate code fragment where the error appears (request.js:751:32). Here it is:
try {
self.req = self.httpModule.request(reqOptions)
} catch (err) {
self.emit('error', err)
return
}
The only solution I've come to is to comment self.emit('error', err) code line, which is obviously far from best practice.
The fact is the same code works on other computers (Ubuntu, Windows) with same components versions and no error occurs. Also API endpoints like http://myIp:3000/v1/community/list work fine on all devices.
Here's my component versions:
npm — 6.5.0,
node — 11.4.0,
request — 2.88.0,
Ubuntu — 16.04 (Windows — 10)
some code fragments if needed (Express Server creation and specific route in ProjectsController):
const app = express();
app.use('/v1/projects/', ProjectsController);
const router = express.Router();
router.post('/list', function(req,res){
//logic
});
node.js express npm ubuntu-16.04
asked Jan 3 at 15:55
Hlib DerbenovHlib Derbenov
614
add a comment |
I am working Ubuntu with incoming HTTP request with this URL: http://myIp:3000/v1/projects/list
And I get this error in terminal:
TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
at new ClientRequest (_http_client.js:127:13)
at Object.request (https.js:300:10)
at Request.start (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:751:32)
at Request.end (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:1512:10)
at end (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:564:14)
at Immediate._onImmediate (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:578:7)
at processImmediate(timers.js:632:19)
After this error node process dissapears from terminal (but still working and API response is sent properly), though I can't see its work (image attached). So the only way to interact with node process is to do something like ps aux | grep node or ps Tand manually kill process.
Assuming the error meaning I've found an appropriate code fragment where the error appears (request.js:751:32). Here it is:
try {
self.req = self.httpModule.request(reqOptions)
} catch (err) {
self.emit('error', err)
return
}
The only solution I've come to is to comment self.emit('error', err) code line, which is obviously far from best practice.
The fact is the same code works on other computers (Ubuntu, Windows) with same components versions and no error occurs. Also API endpoints like http://myIp:3000/v1/community/list work fine on all devices.
Here's my component versions:
npm — 6.5.0,
node — 11.4.0,
request — 2.88.0,
Ubuntu — 16.04 (Windows — 10)
some code fragments if needed (Express Server creation and specific route in ProjectsController):
const app = express();
app.use('/v1/projects/', ProjectsController);
const router = express.Router();
router.post('/list', function(req,res){
//logic
});
node.js express npm ubuntu-16.04
asked Jan 3 at 15:55
Hlib DerbenovHlib Derbenov
614
I am working Ubuntu with incoming HTTP request with this URL: http://myIp:3000/v1/projects/list
And I get this error in terminal:
TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
at new ClientRequest (_http_client.js:127:13)
at Object.request (https.js:300:10)
at Request.start (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:751:32)
at Request.end (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:1512:10)
at end (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:564:14)
at Immediate._onImmediate (/home/dev/grem-api-dev/apiv3/node_modules/request/request.js:578:7)
at processImmediate(timers.js:632:19)
After this error node process dissapears from terminal (but still working and API response is sent properly), though I can't see its work (image attached). So the only way to interact with node process is to do something like ps aux | grep node or ps Tand manually kill process.
Assuming the error meaning I've found an appropriate code fragment where the error appears (request.js:751:32). Here it is:
try {
self.req = self.httpModule.request(reqOptions)
} catch (err) {
self.emit('error', err)
return
}
The only solution I've come to is to comment self.emit('error', err) code line, which is obviously far from best practice.
The fact is the same code works on other computers (Ubuntu, Windows) with same components versions and no error occurs. Also API endpoints like http://myIp:3000/v1/community/list work fine on all devices.
Here's my component versions:
npm — 6.5.0,
node — 11.4.0,
request — 2.88.0,
Ubuntu — 16.04 (Windows — 10)
some code fragments if needed (Express Server creation and specific route in ProjectsController):
const app = express();
app.use('/v1/projects/', ProjectsController);
const router = express.Router();
router.post('/list', function(req,res){
//logic
});
node.js express npm ubuntu-16.04
node.js express npm ubuntu-16.04
asked Jan 3 at 15:55
Hlib DerbenovHlib Derbenov
614
asked Jan 3 at 15:55
Hlib DerbenovHlib Derbenov
614
asked Jan 3 at 15:55
Hlib DerbenovHlib Derbenov
614
asked Jan 3 at 15:55
Hlib DerbenovHlib Derbenov
614
asked Jan 3 at 15:55
Hlib DerbenovHlib Derbenov
614
614
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Solution for this issue was finding code fragment that was sending request to other web resource with URL that contained unescaped characters, and then replacing them according to this article https://www.w3schools.com/tags/ref_urlencode.asp. This fragment was executed by condition, that's why only 1 server with specific OS passed through if/else statement.
const request = require('request');
if (...) {}
else {
request.get(...) //source of error
.on('response', function(response) {
//logic
});
}
answered Jan 5 at 0:40
Hlib DerbenovHlib Derbenov
614
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025710%2ftypeerror-err-unescaped-characters-request-path-contains-unescaped-characters%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Solution for this issue was finding code fragment that was sending request to other web resource with URL that contained unescaped characters, and then replacing them according to this article https://www.w3schools.com/tags/ref_urlencode.asp. This fragment was executed by condition, that's why only 1 server with specific OS passed through if/else statement.
const request = require('request');
if (...) {}
else {
request.get(...) //source of error
.on('response', function(response) {
//logic
});
}
answered Jan 5 at 0:40
Hlib DerbenovHlib Derbenov
614
add a comment |
Solution for this issue was finding code fragment that was sending request to other web resource with URL that contained unescaped characters, and then replacing them according to this article https://www.w3schools.com/tags/ref_urlencode.asp. This fragment was executed by condition, that's why only 1 server with specific OS passed through if/else statement.
const request = require('request');
if (...) {}
else {
request.get(...) //source of error
.on('response', function(response) {
//logic
});
}
answered Jan 5 at 0:40
Hlib DerbenovHlib Derbenov
614
add a comment |
Solution for this issue was finding code fragment that was sending request to other web resource with URL that contained unescaped characters, and then replacing them according to this article https://www.w3schools.com/tags/ref_urlencode.asp. This fragment was executed by condition, that's why only 1 server with specific OS passed through if/else statement.
const request = require('request');
if (...) {}
else {
request.get(...) //source of error
.on('response', function(response) {
//logic
});
}
answered Jan 5 at 0:40
Hlib DerbenovHlib Derbenov
614
Solution for this issue was finding code fragment that was sending request to other web resource with URL that contained unescaped characters, and then replacing them according to this article https://www.w3schools.com/tags/ref_urlencode.asp. This fragment was executed by condition, that's why only 1 server with specific OS passed through if/else statement.
const request = require('request');
if (...) {}
else {
request.get(...) //source of error
.on('response', function(response) {
//logic
});
}
answered Jan 5 at 0:40
Hlib DerbenovHlib Derbenov
614
answered Jan 5 at 0:40
Hlib DerbenovHlib Derbenov
614
answered Jan 5 at 0:40
Hlib DerbenovHlib Derbenov
614
answered Jan 5 at 0:40
Hlib DerbenovHlib Derbenov
614
614
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025710%2ftypeerror-err-unescaped-characters-request-path-contains-unescaped-characters%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
