2021年更新: 我试了url。format和querystring这两个都被弃用了，取而代之的是我们可以使用URLSearchParams

const {URLSearchParams} = require('url')
               
app.get('/category', (req, res) =>{
    const pathname = '/?'
    const components ={
     a:"a",
     b:"b"
    }

    const urlParameters = new URLSearchParams(components)
    res.redirect(pathname + urlParameters)
})

我发现的最简单的方法是在routeHandlers之间传递数据来使用next()，不需要干扰重定向或会话。 可选地，您可以只调用您的homeCtrl(req,res)而不是next()，只传递req和res

var express  = require('express');
var jade     = require('jade');
var http     = require("http");


var app    = express();
var server = http.createServer(app);

/////////////
// Routing //
/////////////

// Move route middleware into named
// functions
function homeCtrl(req, res) {

    // Prepare the context
    var context = req.dataProcessed;
    res.render('home.jade', context);
}

function categoryCtrl(req, res, next) {

    // Process the data received in req.body
    // instead of res.redirect('/');
    req.dataProcessed = somethingYouDid;
    return next();
    // optionally - Same effect
    // accept no need to define homeCtrl
    // as the last piece of middleware
    // return homeCtrl(req, res, next);
}

app.get('/', homeCtrl);

app.post('/category', categoryCtrl, homeCtrl);

我用了一个非常简单但有效的技巧 在我的app.js(我的入口点) 我定义了一个变量

let authUser = {};

然后我分配给它从我的路由页面(像成功登录后)

authUser = matchedUser

这可能不是最好的方法，但它符合我的需求。

我不得不寻找另一个解决方案，因为所提供的解决方案实际上没有一个满足我的要求，原因如下:

Query strings: You may not want to use query strings because the URLs could be shared by your users, and sometimes the query parameters do not make sense for a different user. For example, an error such as ?error=sessionExpired should never be displayed to another user by accident. req.session: You may not want to use req.session because you need the express-session dependency for this, which includes setting up a session store (such as MongoDB), which you may not need at all, or maybe you are already using a custom session store solution. next(): You may not want to use next() or next("router") because this essentially just renders your new page under the original URL, it's not really a redirect to the new URL, more like a forward/rewrite, which may not be acceptable.

所以这是我的第四个解决方案，没有任何前面的问题。基本上，它涉及到使用一个临时cookie，为此你必须首先安装cookie-parser。显然，这意味着它只能在启用cookie的情况下工作，并且数据量有限。

实现的例子:

var cookieParser = require("cookie-parser");

app.use(cookieParser());

app.get("/", function(req, res) {
    var context = req.cookies["context"];
    res.clearCookie("context", { httpOnly: true });
    res.render("home.jade", context); // Here context is just a string, you will have to provide a valid context for your template engine
});

app.post("/category", function(req, res) {
    res.cookie("context", "myContext", { httpOnly: true });
    res.redirect("/");
}

你可以通过查询字符串传递少量的键/值对数据:

res.redirect('/?error=denied');

主页上的javascript可以访问它并相应地调整它的行为。

注意，如果你不介意/category作为浏览器地址栏中的URL，你可以直接渲染而不是重定向。恕我直言，很多时候人们使用重定向，因为旧的web框架使直接响应变得困难，但表达起来很容易:

app.post('/category', function(req, res) {

  // Process the data received in req.body

  res.render('home.jade', {error: 'denied'});
});

@Dropped.on。Caprica评论说，使用AJAX消除了URL更改问题。

我们可以使用express-session发送所需的数据

当你初始化应用程序

const express = require('express');
const app = express();
const session = require('express-session');
app.use(session({secret: 'mySecret', resave: false, saveUninitialized: false}));

所以在重定向之前，只需要为会话保存上下文

app.post('/category', function(req, res) {
    // add your context here 
req.session.context ='your context here' ;
    res.redirect('/');
});

现在您可以在会话的任何地方获取上下文。它可以通过request。session。context获得

app.get('/', function(req, res) {

    // So prepare the context
var context=req.session.context;
    res.render('home.jade', context);
});