/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 vote267 views1 answer
Expressjs with mongodb
Javascript Express
0 vote281 views1 answer
Render raw html in response with Express
Javascript Express
1 vote260 views1 answer
Express body-parser is depreciated
Javascript Express
57 votes328 views3 answers
Require express
Javascript Express
0 vote289 views1 answer
Express send 200
Javascript Express
1 vote339 views1 answer
Expressjs create encrypted password
Javascript Express
0 vote275 views1 answer
Express access static files in post request
Javascript Express
0 vote259 views1 answer
Serve a file in express
Javascript Express
1 vote245 views1 answer
Get express variable
Javascript Express
0 vote265 views2 answers
Req.query express
Javascript Express