/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 vote249 views1 answer
Express send 200
Javascript Express
1 vote228 views2 answers
Express trust proxy
Javascript Express
0 vote211 views1 answer
Mongoose express js post
Javascript Express
6 votes209 views6 answers
Express return json
Javascript Express
60 votes364 views6 answers
Express Server
Javascript Express
0 vote201 views1 answer
Remove etag express
Javascript Express
15 votes234 views1 answer
Express view engine', 'ejs
Javascript Express
37 votes417 views6 answers
Express body-parser deprecated
Javascript Express
-2 votes257 views1 answer
Express get port from request
Javascript Express
0 vote195 views1 answer
Set up background process in express app
Javascript Express