/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 vote163 views1 answer
How To Upload File To Alicloud OSS with node.js and Express
Javascript Express
0 vote156 views1 answer
EXPRESS APP REGISTER HANDLEBARS VIEW ENGINE
Javascript Express
24 votes160 views4 answers
Npm express
Javascript Express
0 vote150 views1 answer
Express js boilerplate
Javascript Express
1 vote161 views1 answer
Express middleware pass parameter
Javascript Express
0 vote164 views1 answer
Set up background process in express app
Javascript Express
0 vote143 views1 answer
Express get remote ip
Javascript Express
1 vote160 views1 answer
Express prisma
Javascript Express
0 vote156 views1 answer
Express remove x-powered-by
Javascript Express
4 votes219 views1 answer
Express get full url
Javascript Express