/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

1 vote219 views2 answers
Express trust proxy
Javascript Express
1 vote187 views1 answer
What is express static
Javascript Express
10 votes221 views6 answers
Express cookieparser
Javascript Express
2 votes232 views1 answer
Refresh after delete in express
Javascript Express
0 vote177 views1 answer
Express db
Javascript Express
6 votes199 views3 answers
Express urlencoded
Javascript Express
1 vote224 views4 answers
Cors error in node js express
Javascript Express
0 vote234 views1 answer
React download file from express res.download
Javascript Express
1 vote226 views1 answer
Http to https redirect express js
Javascript Express
0 vote219 views1 answer
Express pourquoi mettre bodyparser avant router
Javascript Express