/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 vote206 views1 answer
Express remove x-powered-by
Javascript Express
13 votes212 views3 answers
Express request body undefined
Javascript Express
18 votes230 views3 answers
Fetch is not defined express
Javascript Express
1 vote240 views1 answer
Nodejs check if express started
Javascript Express
0 vote209 views1 answer
== operation is not working on ids in express
Javascript Express
1 vote212 views2 answers
Express trust proxy
Javascript Express
55 votes246 views6 answers
Express js params
Javascript Express
0 vote218 views1 answer
Express rate limit redis
Javascript Express
23 votes211 views6 answers
Node.js express
Javascript Express
0 vote219 views1 answer
How to use custom stylesheets express node
Javascript Express