节点/快速路由不等待Redis服务器回调

Question

在任何对Redis res.json(...) client.somecommand(..) 的打开调用返回之前，需要对下面的代码进行哪些特定的更改才能发送命令？

下面的代码抛出了一个与client.hmset(uname, { ... }相关的错误，试图在调用res.json(...)之后设置响应头。当我将return res.json()命令移至client.exists(uname, function(err, reply) { ... }条件块结束后，而不是它们在块中的当前位置时，anonymous token值将发送到客户端应用程序，而不是生成的token值。这表示对Redis服务器的回调没有返回。

如何更改下面的代码，以便在返回Redis服务器回调之前无法运行res.json( ... )命令？理想情况下，如果Redis服务器回调时间太长，则在发送错误消息之前有一些条件要等待一定的时间。

通过在文件顶部添加以下两行代码，Redis将添加到包含以下所有代码的routes.js文件中：

var redis = require('redis');
var client = redis.createClient();

下面的代码中有对Redis服务器的各种调用：

client.exists(uname, function(err, reply) { ... }
client.hgetall(uname, function(err, object) { ... }
client.hmset(uname, { ... }
client.expire(uname, 10);

Node.js/Express.jsAPI路由的完整代码是：

app.get('/user**', function(req, res) {
    console.log("You Hit The User Route TOP");
    request({
        method: 'GET',
        url: authServer + '/uaa/user', 
        json: true, 
        auth: {
            user: null,
            password: null,
            sendImmediately: true,
            bearer: bearerToken 
        }
    }, function (error, response, body) {
        if(error){
          console.log('ERROR with user request.');
          return res.sendStatus(500);  
        }
        else {
            var uname = '';var jwtUser = 'empty';var jwtJSON = { "token" : "anonymous" }
            console.log(response.statusCode);
            if(body['name']){ 
                uname = body['name'];console.log('uname is: ');console.log(uname);
                if(uname.length > 0) {
                    scopesLocal = body['oauth2Request'].scope.toString();
                    client.exists(uname, function(err, reply) {//Check to see if a Redis key for the user already exists
                        if (reply === 1) {//a redis key DOES exist
                            console.log('\"'+uname+'\" exists');
                            client.hgetall(uname, function(err, object) {//retrieve all the values in the hash/object that we just set
                            if(object) {
                                if(object["jwt"]) { 
                                    console.log('object[\"jwt\"] is: ');console.log(object["jwt"]); 
                                    jwtJSON = { "token" : object["jwt"] };
                                    console.log('jwtJSON is: ');console.log(jwtJSON);
                                    return res.json(jwtJSON);
                                }
                            }
                        });
                        } else {//a redis key DOES NOT exist
                            console.log('\"'+uname+'\" doesn\'t exist');
                            jwtUser = generateJwt(uname, authoritiesLocal);
                            client.hmset(uname, {//store a hash/object
                                'AccessToken': body['details'].tokenValue,
                                'TokenType': body['details'].tokenType,
                                'Authenticated': body['authenticated'],
                                'Principal': body['principal'],
                                'Scopes': scopesLocal.toString(), 
                                'Authorities' : authoritiesLocal,
                                'jwt' : jwtUser
                            });
                            jwtJSON = { "token" : jwtUser };console.log('jwtJSON is: ');console.log(jwtJSON);
                            return res.json(jwtJSON);
                        }
                        client.expire(uname, 10);//set the key to expire in 10 seconds.  use this to manage session length
                    });//end of Redis conditional block
                    console.log('jwtJSON is: ');console.log(jwtJSON);
                } else { console.log('uname is empty!'); }
                return res.json(jwtJSON);
            }
        };
    });
    console.log("You Hit The User Route BOTTOM");
});

nodemon终端中的错误消息是：

_http_outgoing.js:346
    throw new Error('Can\'t set headers after they are sent.');
    ^

Error: Can't set headers after they are sent.
    at ServerResponse.OutgoingMessage.setHeader (_http_outgoing.js:346:11)
    at ServerResponse.header (/home/user/nodejs_apps/oauth_seed_app/node_modules/express/lib/response.js:719:10)
    at ServerResponse.json (/home/user/nodejs_apps/oauth_seed_app/node_modules/express/lib/response.js:247:10)
    at Command.callback (/home/user/nodejs_apps/oauth_seed_app/app/routes.js:112:44)
    at normal_reply (/home/user/nodejs_apps/oauth_seed_app/node_modules/redis/index.js:714:21)
    at RedisClient.return_reply (/home/user/nodejs_apps/oauth_seed_app/node_modules/redis/index.js:816:9)
    at JavascriptRedisParser.Parser.returnReply (/home/user/nodejs_apps/oauth_seed_app/node_modules/redis/index.js:188:18)
    at JavascriptRedisParser.execute (/home/user/nodejs_apps/oauth_seed_app/node_modules/redis-parser/lib/parser.js:413:12)
    at Socket.<anonymous> (/home/user/nodejs_apps/oauth_seed_app/node_modules/redis/index.js:267:27)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at readableAddChunk (_stream_readable.js:153:18)
    at Socket.Readable.push (_stream_readable.js:111:10)
    at TCP.onread (net.js:534:20)

我读过关于特定错误消息的this posting。我还读过this other posting关于如何等待回调的文章。我还读过this posting关于Redis回调Node的文章。但我看不出如何将答案应用于上述代码中的Redis回调问题。

Answer 1

问题是OP中的return res.json(jwtJSON);命令没有被隔离到离散的if...else块中。

解决办法是：

if(something) {
    //populate jwtJSON with a real JWT
    return res.json(jwtJSON);
} else {
    return res.json(jwtJSON);//this leaves the anonymous value
}  

对上述代码中的每一个嵌套条件执行这种隔离处理解决了这个问题。