/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 vote323 views1 answer
Express http to https
Javascript Express
64 votes435 views6 answers
Express routing
Javascript Express
0 vote263 views1 answer
Basic express graphql
Javascript Express
0 vote294 views1 answer
Express basic routing syntax
Javascript Express
1 vote286 views1 answer
Express prisma
Javascript Express
4 votes270 views1 answer
Express case sensitive routing
Javascript Express
1 vote312 views1 answer
Redirect all request http to https express js
Javascript Express
2 votes323 views2 answers
Express check if object is empty
Javascript Express
2 votes277 views3 answers
Req body express
Javascript Express
3 votes275 views1 answer
Nodejs express return image
Javascript Express