/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 votes138 views2 answers
Res.locals in express
Javascript Express
0 vote150 views1 answer
Create mongodb express server npm
Javascript Express
6 votes132 views3 answers
Express urlencoded
Javascript Express
0 vote137 views1 answer
Express reload page after post
Javascript Express
0 vote124 views1 answer
Serve public folder express without file extension
Javascript Express
0 vote195 views1 answer
How to download express without view
Javascript Express
0 vote175 views2 answers
Express plus make router
Javascript Express
69 votes244 views6 answers
Express redirect to url
Javascript Express
35 votes250 views6 answers
Bodyparser express deprecated
Javascript Express
5 votes141 views1 answer
Twilio sms sending in express
Javascript Express