因此,我有一個節點服務器啓動並運行一個api端點,當通過郵遞員輸入重複的電子郵件時,端點不斷崩潰。如果發生非重複註冊,服務器將繼續運行而不會打嗝。但是,如果一個重複的電子郵件提交,我看到郵遞員重複的電子郵件錯誤:當重複註冊發生時,節點快遞服務器崩潰
{
"code": 11000,
"index": 0,
"errmsg": "E11000 duplicate key error collection: register.users index: email_1 dup key: { : \"[email protected]\" }",
"op": {
"userRole": "isUser",
"password": "yudfjadjslkafdaljj343",
"zip": "94596",
"state": "CA",
"city": "Walnut Creek",
"address2": "",
"streetAddress": "1 fake address ",
"phoneNumber": "(925) 555-0644",
"email": "[email protected]",
"lastName": "Last",
"firstName": "Person",
"_id": "57e2b2e49f0de63201914616",
"__v": 0
}
}
這裏的API路線:
var express = require('express');
var app = express();
var router = express.Router();
var User = require('../models/user');
module.exports = function (app) {
router.route('/users')
.get(function (req, res) {
res.json({ message: 'welcome!!' });
})
.post(function (req, res) {
var rb = req.body;
var user = new User();
user.firstName = rb.firstName;
user.lastName = rb.lastName;
user.email = rb.email;
user.phoneNumber = rb.phoneNumber;
user.streetAddress = rb.streetAddress;
user.address2 = rb.address2;
user.city = rb.city;
user.state = rb.state;
user.zip = rb.zip
user.password = rb.password;
user.userRole = rb.userRole;
user.save(function(err) {
if (err) {
res.send(err);
next();
};
res.json({ message: 'UserCreated!' });
});
});
app.use('/api', router);
}
和貓鼬模式:
var mongoose = require('mongoose');
var Schema = mongoose.Schema;
var UserSchema = new Schema({
firstName: {
type: String,
required: true
},
lastName: {
type: String,
required: true
},
email: {
type: String,
required: true,
index: true,
unique: true
},
phoneNumber: {
type: String,
required: true
},
streetAddress: {
type: String,
required: true
},
address2: String,
city: {
type: String,
required: true
},
state: {
type: String,
required: true
},
zip: {
type: String,
required: true
},
password: {
type: String,
required: true
},
userRole: {
type: String,
required: true
}
});
module.exports = mongoose.model('User', UserSchema);
最後終端上的錯誤:
[nodemon] restarting due to changes...
[nodemon] starting `node server/server.js`
Up and running on port 3000
events.js:160
throw er; // Unhandled 'error' event
^
Error: Can't set headers after they are sent.
at ServerResponse.OutgoingMessage.setHeader (_http_outgoing.js:346:11)
at ServerResponse.header (/Users/atlanteavila/Documents/myapps/register/node_modules/express/lib/response.js:719:10)
at ServerResponse.send (/Users/atlanteavila/Documents/myapps/register/node_modules/express/lib/response.js:164:12)
at ServerResponse.json (/Users/atlanteavila/Documents/myapps/register/node_modules/express/lib/response.js:250:15)
at /Users/atlanteavila/Documents/myapps/register/server/routes/signUp.js:34:11
at /Users/atlanteavila/Documents/myapps/register/node_modules/mongoose/lib/model.js:3336:16
at /Users/atlanteavila/Documents/myapps/register/node_modules/mongoose/lib/document.js:1932:15
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
[nodemon] app crashed - waiting for file changes before starting...
提前感謝您幫助解決這一問題。謝謝!
這絕對解決了這個問題。我選擇這個作爲最佳答案b/c在兩個地方似乎都需要return語句。謝謝! –