/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

0 vote240 views1 answer
Node.js express export routes
Javascript Express
62 votes260 views3 answers
Express hello world
Javascript Express
0 vote221 views3 answers
How to serve React JS static files with express JS?
Javascript Express
1 vote235 views2 answers
Express trust proxy
Javascript Express
2 votes236 views1 answer
What will you write to add the .env file to your express application?
Javascript Express
0 vote248 views1 answer
Node express app.listen at specific port & host
Javascript Express
1 vote270 views1 answer
Express ejs layout use different layout
Javascript Express
24 votes225 views4 answers
Express js npm
Javascript Express
0 vote223 views1 answer
Passing variable in table row delete button node js express
Javascript Express
1 vote250 views1 answer
Redirect all request http to https express js
Javascript Express