/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 vote204 views1 answer
Entendendo Package Json e instalando o Express
Javascript Express
0 vote196 views1 answer
Insert a data into mongo using express
Javascript Express
0 vote205 views1 answer
Uuid use in express
Javascript Express
0 vote190 views1 answer
Err handling express
Javascript Express
0 vote208 views1 answer
Error sending empty object express
Javascript Express
1 vote207 views1 answer
Express timeout between requests
Javascript Express
8 votes210 views1 answer
Express router file
Javascript Express
0 vote209 views1 answer
Express Router()
Javascript Express
1 vote206 views1 answer
Http to https redirect express js
Javascript Express
1 vote215 views1 answer
Nuxt looks for npm_modules on express
Javascript Express