快線404

Question

我的node.js快速路由遇到問題。 我真的很新，看不到我的錯誤。 請求localhost：2700 / api / subs時總是出現404錯誤，但是我認為我的路線是正確的，不是嗎？ 有人看到錯誤了嗎？

錯誤消息的開頭：

 Error: Not Found at ****/app.js:45:13 at Layer.handle [as handle_request] (****/node_modules/express/lib/router/layer.js:95:5) 

這是app.js

var express = require('express');
var path = require('path');
var favicon = require('serve-favicon');
var logger = require('morgan');
var cookieParser = require('cookie-parser');
var bodyParser = require('body-parser');

const mongoose = require('mongoose');

// establish connection to the Database
mongoose.connect('mongodb://localhost/test', {
  useMongoClient: true
});

mongoose.connection.once('open', function() {
  console.log('Connection to Database has been established..');
}).on('error', function(error){
  console.log(error);
});


var index = require('./routes/index');
var users = require('./routes/users');
Subscriber = require('./routes/subscriber.js');

var app = express();

// view engine setup
app.set('views', path.join(__dirname, 'views'));
app.set('view engine', 'jade');

// uncomment after placing your favicon in /public
//app.use(favicon(path.join(__dirname, 'public', 'favicon.ico')));
app.use(logger('dev'));
app.use(bodyParser.json());
app.use(bodyParser.urlencoded({ extended: false }));
app.use(cookieParser());
app.use(express.static(path.join(__dirname, 'public')));

app.use('/', index);
app.use('/users', users);

// catch 404 and forward to error handler
app.use(function(req, res, next) {
var err = new Error('Not Found');
err.status = 404;
next(err);
});

// error handler
app.use(function(err, req, res, next) {
  // set locals, only providing error in development
  res.locals.message = err.message;
  res.locals.error = req.app.get('env') === 'development' ? err : {};

  // render the error page
  res.status(err.status || 500);
  res.render('error');
});

app.get('/api/subs', function(req, res){
    Subscriber.getSubscribers(function(err, subscribers){
        if(err){
            throw err;
        }
        res.json(subscribers);
    });
});

// ... here is a function which creates the database objects and saves         
//       them. took it out for better overview....

app.listen(2700, function(){
  console.log("Listening on Port 2700")
});

module.exports = app;

和subscriber.js這是在子目錄./routes：

const mongoose = require('mongoose');

var subscriberSchema = mongoose.Schema({
    //seqnr shall go here. dunno how to declare integer x)
    nr: Number,
    name: String,
    email: String,
    uLink: String,
    anwalt: String
});

var Subscriber = module.exports = mongoose.model('Subscriber', subscriberSchema);

//get Subscriber
module.exports.getSubscribers = function(callback, limit){
    Subscriber.find(callback).limit(limit);
};

index.js

var express = require('express');
var router = express.Router();

/* GET home page. */ 
router.get('/', function(req, res, next) {
  res.render('index', { title: 'Express' });
});

module.exports = router;

Answer 1

您需要將404 app.use放在所有其他用途之后，否則它將忽略其后的api/subs 。

而且，此位將永遠不會運行，因為它也位於api.use ，它將始終引發錯誤：

// error handler
app.use(function(err, req, res, next) {
  // set locals, only providing error in development
  res.locals.message = err.message;
  res.locals.error = req.app.get('env') === 'development' ? err : {};

  // render the error page
  res.status(err.status || 500);
  res.render('error');
});

另外，您實際上不應該為404拋出錯誤。 它應該告訴最終用戶該頁面不存在，但它不應使您的腳本崩潰。

我也同意另一個答案，即應該將這些代碼塊移至單獨的路由器文件中，但這更多的是針對良好的實踐和結構設計，而不是針對此特定的錯誤。

Answer 2

嘗試將其放在單獨的文件中，並在404處理程序之前將其包含在其他路由中

app.use('/', index);
app.use('/users', users);

所以...建立一個subs.js路由

var express = require('express');
var router = express.Router();
Subscriber = require('./routes/subscriber.js');

router.get('/', function(req, res){
    Subscriber.getSubscribers(function(err, subscribers){
        if(err){
            throw err;
        }
        res.json(subscribers);
    });
});

module.exports = router;

然后將其包含在您的app.js

var subs= require('./routes/subs');
...
api.use('/api/subs', subs);
...
app.use(function(req, res, next) {
var err = new Error('Not Found');
err.status = 404;
next(err);
});