/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

2 votes273 views1 answer
Express response sended
Javascript Express
0 vote358 views1 answer
Expressjs cors blocked mixed-content
Javascript Express
0 vote306 views1 answer
Node express table view
Javascript Express
60 votes399 views6 answers
Express Server
Javascript Express
10 votes361 views6 answers
Express cookieparser
Javascript Express
69 votes392 views6 answers
Express redirect to url
Javascript Express
31 votes376 views4 answers
Express cors policy
Javascript Express
6 votes366 views2 answers
Http header express
Javascript Express
63 votes456 views5 answers
Express js redirect to url
Javascript Express
2 votes393 views2 answers
How to send form data from react to express
Javascript Express