Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial![](https://ecs-static.teamtreehouse.com/assets/views/marketing/shared/community-banner-white-47072046c51352fe6a69f5e691ff5700b28bb11d45197d7bdf066d9ea3f72d0c.webp)
![Tyler McDonald](https://secure.gravatar.com/avatar/89e6d4f3e9e00868956029cca3c9f6ba?s=96&d=https%3A%2F%2Fecs-static.teamtreehouse.com%2Fassets%2Fcontent%2Fdefault_avatar-445fbbabfc8dc9188fb5967fe43322ee0c3e0dd1e10f378bf8343784af5a13eb.webp&r=pg)
Tyler McDonald
Full Stack JavaScript Techdegree Graduate 16,700 PointsNode not showing error with incorrect URL
Hello, I am following along with Reggie, but whenever I mistype the URL to force node to throw the error, it doesn't work. After about 30 seconds it throws an error connect ETIMEDOUT.
Is there a reason I am unable to get the same error as Reggie?
Here's my code:
const https = require("https");
function getProfile(username) {
// Connect to the API URL
const request = https.get(
`https://teamtreehousea.com/profiles/${username}.json`,
(response) => {
let body = "";
// Read the data
response.on("data", (data) => (body += data.toString()));
// Parse the data
response.on("end", () => {
const profile = JSON.parse(body);
printMessage(profile);
});
}
);
request.on("error", (error) => console.error(error));
}
// Print the data
function printMessage(profile) {
const message = `${profile.name} (${profile.profile_name}) has ${profile.badges.length} total badge(s) and ${profile.points.total} points.`;
console.log(message);
}
const users = process.argv.slice(2);
users.forEach(getProfile);
1 Answer
![Steven Parker](https://uploads.teamtreehouse.com/production/profile-photos/969492/micro_tool_chess_set_2.jpg)
Steven Parker
230,688 PointsThe type of error you get depends on which part of the URL is incorrect:
If the URL points to a server that doesn't exist, a timeout is the type of error you should get (eventually).
On the other hand, if the URL points to a legitimate server, but to a resource that the server doesn't have, you'll get a "not found" error right away.