相当于node.js http模块的“ req.url”的express.js是什么？

Question

When using vanilla node.js' http.createServer, you can get the url that the client requested with req.url.

When using express.js, the code for responding to a HTTP GET request is something like:

app.get('/', function (req, res) {
  res.send('Hello World!')
})

My problem with this is that it requires you to have an individual app.get for every single page or item on the server. How do I use express.js like the vanilla node.js server to deal with each get request within the callback generated by the http.createServer?

Answer 1

Register you followup handler like an express module...

app.use(function(req, res, next){ ... YOUR CODE HERE ... })

Do this after your routes...

Answer 2

Hi

To answer the specific question (as outlined in your title) , ExpressJS provides

• req.originalURL which is equivalent to Node's req.url
• req.baseUrl which is actually the path that was mounted by Express

So, essentially, Express' req.baseUrl + req.url is equivalent to Node's req.url

Also, Express' routing DOES NOT require you to explicitly set the path to each page; it also accepts regex strings with which you can process specific requests.

Take a look at Express' routing ; it should be of immense benefit to you.

Answer 3

You shouldn't ever have a need to use req.url . Express allows you to have variables in your routes.

app.get('/article/:id', function(req, res) {
    // req.params.id will be whatever came after /article/
});

You can also get fancy and use a regular expression.

app.get(/\/article(\d+)/, function(req, res) {
    // req.params[0] will have the digits of /article123
});

If you really want the URL, req.url still exists. However, you should use routes to handle all your routing logic. I've never really had the need to use req.url .