/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 vote268 views1 answer
Express fingerprint
Javascript Express
0 vote363 views1 answer
Expressjs cheat sheet
Javascript Express
0 vote278 views1 answer
Express server how to get request ip
Javascript Express
0 vote286 views1 answer
No special characters express validator
Javascript Express
63 votes334 views5 answers
Express js redirect to url
Javascript Express
0 vote241 views1 answer
Express get locals from request
Javascript Express
0 vote280 views1 answer
EXPRESS APP REGISTER HANDLEBARS VIEW ENGINE
Javascript Express
0 vote334 views1 answer
Error: cannot find module 'html' express
Javascript Express
0 vote290 views1 answer
Entendendo Package Json e instalando o Express
Javascript Express
1 vote279 views1 answer
Mongoose and express get requests
Javascript Express