/Javascript/Express/Req.params.id express

Req.params.id express

Req.query vs req.params express

Passing params ===> GET request to "/cars/honda" 
returns a list of Honda car models


Passing query =====> GET request to "/car/honda?color=blue"


returns a list of Honda car models, but filtered so only models with an stock
color of blue are returned.

It doesn't make sense to add those filters into the URL 
parameters (/car/honda/color/blue) because according to REST, that would 
imply that we want to get a bunch of information about the color "blue".
Since what we really want is a filtered list of Honda models, we use query
strings to filter down the results that get returned.

Notice that the query strings are really just { key: value } pairs in a 
slightly different format: ?key1=value1&key2=value2&key3=value3.

Source: grepper.com

Similar codes

62 votes260 views3 answers
Expressjs hello world
Javascript Express
0 vote137 views1 answer
Express get raw query
Javascript Express
0 vote143 views1 answer
Express middleware status code always 200
Javascript Express
0 vote154 views1 answer
Remove .html from url express js
Javascript Express
18 votes140 views3 answers
Fetch is not defined express
Javascript Express
0 vote138 views3 answers
How to serve React JS static files with express JS?
Javascript Express
1 vote144 views1 answer
Express timeout between requests
Javascript Express
83 votes255 views6 answers
Express nodejs
Javascript Express
0 vote153 views1 answer
Express js project github
Javascript Express
0 vote135 views1 answer
Try and catch express
Javascript Express