/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 vote192 views1 answer
How to use vue.js in expressjs with pug
Javascript Express
0 vote170 views1 answer
Express set views directory
Javascript Express
14 votes158 views2 answers
Check express version
Javascript Express
2 votes185 views1 answer
Expressjs path optional parameters
Javascript Express
2 votes140 views1 answer
Expressjs download
Javascript Express
0 vote193 views1 answer
TypeError:Cannot read property 'reviews' of null express
Javascript Express
0 vote164 views1 answer
Err handling express
Javascript Express
1 vote230 views1 answer
Expressjs create encrypted password
Javascript Express
37 votes236 views6 answers
Express body-parser deprecated
Javascript Express
1 vote181 views2 answers
Express trust proxy
Javascript Express