/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 vote155 views1 answer
Express unique validator for the owner
Javascript Express
37 votes294 views6 answers
Express body-parser deprecated
Javascript Express
6 votes149 views3 answers
Express urlencoded
Javascript Express
0 vote220 views1 answer
Programação web com Node e Express Beneficiando-se da stack JavaScript
Javascript Express
2 votes174 views1 answer
Expressjs path optional parameters
Javascript Express
1 vote152 views2 answers
Urlencoded json express
Javascript Express
1 vote186 views1 answer
Express static auth
Javascript Express
5 votes150 views1 answer
Node express server static files
Javascript Express
8 votes126 views1 answer
Express delete cookie
Javascript Express
7 votes168 views1 answer
Express js list all routes
Javascript Express