/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

10 votes304 views6 answers
Express cookieparser
Javascript Express
1 vote310 views1 answer
Run project in visual studio with iis express
Javascript Express
0 vote259 views1 answer
Express set views directory
Javascript Express
0 vote263 views1 answer
Manage favicon with express app
Javascript Express
0 vote255 views1 answer
Express add delay
Javascript Express
24 votes290 views4 answers
Express js npm
Javascript Express
62 votes379 views6 answers
Simple express server
Javascript Express
2 votes322 views2 answers
Res.locals in express
Javascript Express
0 vote264 views1 answer
Express Error: Cannot find module '.database/connection'
Javascript Express
0 vote272 views1 answer
Express remove x-powered-by
Javascript Express