/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 vote305 views1 answer
Express orm
Javascript Express
0 vote328 views1 answer
Expressjs cors blocked mixed-content
Javascript Express
0 vote321 views1 answer
Express formidable
Javascript Express
0 vote279 views1 answer
Express rewrite url
Javascript Express
4 votes389 views1 answer
Express get full url
Javascript Express
5 votes295 views2 answers
Serve static files from express
Javascript Express
-1 vote336 views1 answer
Express cors policy no 'access-control-allow-origin'
Javascript Express
24 votes334 views3 answers
Express param in url
Javascript Express
1 vote331 views2 answers
Connecting mongoose with express js
Javascript Express
0 vote289 views1 answer
Express js boilerplate
Javascript Express