/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

1 vote196 views2 answers
Express error middleware
Javascript Express
62 votes271 views6 answers
Simple express server
Javascript Express
24 votes214 views3 answers
Express param in url
Javascript Express
0 vote193 views1 answer
Express get remote ip
Javascript Express
0 vote197 views1 answer
Express generator error handling
Javascript Express
0 vote221 views1 answer
Entendendo Package Json e instalando o Express
Javascript Express
24 votes193 views4 answers
Express js npm
Javascript Express
0 vote199 views2 answers
Express plus
Javascript Express
6 votes257 views3 answers
Set headers in express
Javascript Express
0 vote193 views1 answer
Express pearl ship
Javascript Express