/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

11 votes129 views5 answers
Express validator
Javascript Express
-1 vote172 views1 answer
Express cors policy no 'access-control-allow-origin'
Javascript Express
0 vote180 views1 answer
Express req get json
Javascript Express
0 vote160 views1 answer
Express set views directory
Javascript Express
0 vote150 views1 answer
Express get raw path
Javascript Express
0 vote196 views1 answer
Set 404 handling via express in node
Javascript Express
0 vote229 views1 answer
Express js jump to above directory
Javascript Express
0 vote164 views1 answer
Express json body
Javascript Express
0 vote166 views1 answer
EXPRESS APP REGISTER HANDLEBARS VIEW ENGINE
Javascript Express
0 vote160 views2 answers
Parse json express
Javascript Express