/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 vote283 views2 answers
MongodbClint express
Javascript Express
63 votes373 views4 answers
Sample express app
Javascript Express
0 vote288 views1 answer
Express proxy
Javascript Express
55 votes361 views2 answers
Express url redirect
Javascript Express
0 vote319 views1 answer
Npm paypal express checkout
Javascript Express
1 vote336 views1 answer
Express ejs layout use different layout
Javascript Express
2 votes280 views1 answer
How express serve public folder
Javascript Express
0 vote287 views1 answer
Node express mongo boilerplate with jwt
Javascript Express
1 vote299 views1 answer
Express body-parser is depreciated
Javascript Express
2 votes314 views1 answer
Relaod the page in express
Javascript Express