/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 vote287 views1 answer
A full express function
Javascript Express
2 votes293 views1 answer
What will you write to add the .env file to your express application?
Javascript Express
0 vote264 views1 answer
Manage favicon with express app
Javascript Express
0 vote313 views1 answer
How to set css in hbs in express
Javascript Express
0 vote258 views1 answer
Basic express graphql
Javascript Express
0 vote293 views1 answer
Node js express mongodb find all documents
Javascript Express
0 vote280 views1 answer
Express fingerprint
Javascript Express
0 vote282 views1 answer
Express octet stream
Javascript Express
0 vote347 views1 answer
Error: cannot find module 'html' express
Javascript Express
0 vote258 views1 answer
Express redirect with post data
Javascript Express