/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 vote208 views1 answer
Serve public folder express without file extension
Javascript Express
0 vote238 views2 answers
Parse json express
Javascript Express
23 votes280 views6 answers
Node.js express
Javascript Express
0 vote232 views1 answer
Express middleware status code always 200
Javascript Express
0 vote270 views1 answer
How to use custom stylesheets express node
Javascript Express
2 votes279 views2 answers
Express how to refresh
Javascript Express
0 vote255 views1 answer
How to get data send from a form express
Javascript Express
1 vote247 views1 answer
Javascript express app listen
Javascript Express
0 vote276 views1 answer
Expressjs cors blocked mixed-content
Javascript Express
7 votes257 views1 answer
Express js list all routes
Javascript Express