/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 vote316 views1 answer
Serve a file in express
Javascript Express
1 vote337 views1 answer
Express static auth
Javascript Express
0 vote338 views1 answer
TypeError:Cannot read property 'reviews' of null express
Javascript Express
8 votes304 views3 answers
Request entity too large express
Javascript Express
2 votes346 views2 answers
Initialize express app
Javascript Express
9 votes333 views6 answers
Express bodyparser
Javascript Express
2 votes329 views1 answer
Refresh after delete in express
Javascript Express
0 vote342 views1 answer
Expressjs allow cors for all hosts and ports
Javascript Express
1 vote314 views1 answer
Express middleware pass parameter
Javascript Express
1 vote331 views1 answer
Express timeout between requests
Javascript Express