/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 vote285 views1 answer
MIME type Error CSS in nodejs Express
Javascript Express
0 vote258 views1 answer
Express get jwt token from header
Javascript Express
62 votes318 views3 answers
Express hello world
Javascript Express
0 vote238 views1 answer
Express render
Javascript Express
39 votes364 views5 answers
Node express params
Javascript Express
0 vote339 views1 answer
Set 404 handling via express in node
Javascript Express
83 votes342 views6 answers
Express nodejs
Javascript Express
9 votes272 views2 answers
Express session destroy
Javascript Express
3 votes259 views1 answer
Express get cookie
Javascript Express
0 vote271 views1 answer
Express get raw query
Javascript Express