/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 vote179 views1 answer
Express send 200
Javascript Express
0 vote135 views1 answer
Put route error express
Javascript Express
1 vote128 views1 answer
Get express variable
Javascript Express
0 vote137 views1 answer
Express server how to get request ip
Javascript Express
17 votes144 views6 answers
Express js
Javascript Express
0 vote122 views1 answer
EXPRESS APP REGISTER HANDLEBARS VIEW ENGINE
Javascript Express
8 votes101 views1 answer
Express delete cookie
Javascript Express
1 vote149 views1 answer
Express get request origin
Javascript Express
0 vote135 views1 answer
Favicon express js
Javascript Express
5 votes137 views2 answers
Serve static files from express
Javascript Express