Apache 将根据重写的 URL 选择要提供服务的文件,但原始 URL 将传递给脚本。
Kestrel 将重写的 URL 传递到管道中(可通过HttpContext.Request.Path
).
是否可以访问原网址来自中间件重写后?
遵循@Tseng 发出的指示。我的测试包装了 RewriteMiddleware,但您可能需要一个单独的中间件。
public class P7RewriteMiddleware
{
private RewriteMiddleware _originalRewriteMiddleware;
public P7RewriteMiddleware(
RequestDelegate next,
IHostingEnvironment hostingEnvironment,
ILoggerFactory loggerFactory,
RewriteOptions options)
{
_originalRewriteMiddleware = new RewriteMiddleware(next, hostingEnvironment, loggerFactory, options);
}
/// <summary>
/// Executes the middleware.
/// </summary>
/// <param name="context">The <see cref="HttpContext"/> for the current request.</param>
/// <returns>A task that represents the execution of this middleware.</returns>
public new Task Invoke(HttpContext context)
{
var currentUrl = context.Request.Path + context.Request.QueryString;
context.Items.Add("original-path", currentUrl);
return _originalRewriteMiddleware.Invoke(context);
}
}
后来,我的身份验证过滤器使用它。
if (spa.RequireAuth)
{
context.Result = new RedirectToActionResult(Action, Controller,
new { area = Area, returnUrl = context.HttpContext.Items["original-path"] });
}
本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系:hwhale#tublm.com(使用前将#替换为@)