我正在尝试将使用ASP.NET Core的cookie的SameCookie属性显式设置为无。
我尝试执行此操作的方法是这样设置CookieOptions的属性值：
var options = new CookieOptions
{
SameSite = SameSiteMode.None
};
（为简洁起见，省略了其他属性）
但是，当我检查服务器响应头（服务器应该使用SameSite = None设置cookie）时，我可以看到SameSite被省略了。相反，我可以清楚地看到“价值”，“到期”，“甚至安全”的说法。
如果我将C＃代码中的SameSite设置为Lax或Strict，则可以看到它明确包含在Set-Cookie标头中。如果将其设置为“无”，则无法。
我确实检查了两个浏览器-Firefox和Chrome 77（我知道此版本对SameSite所做的更改）。
有一个黑客可以包含SameSite = None。您只需要向CookieOptions的Path属性添加以下行：
options.Path += "; samesite=None";
然后可以在响应的Set-Cookie标头中找到它。
是否可以将Kestrel（没有用于托管的IIS，裸Kestrel）配置为在头文件中包含SameSite = None，而不会像这样被黑客入侵？
答案 0 :(得分：3)
问题似乎在于，虽然SameSite枚举具有一个None值，但该值被解释为仅不提供SameSite属性的默认值。您可以在code for SetCookieHeaderValue中看到这一点，其中仅包含Strict和Lax的令牌值。
要设置SameSite=None; Secure cookie，您应该自己发送Set-Cookie标头。
（附带说明：我将尝试整理对核心的拉取请求，以添加适当的None支持）
答案 1 :(得分：2)
对于可能需要侧加载选项的任何人，我已经编写，测试并发布了一个简单的解决方案，该解决方案以IHttpModule的形式插入IIS HTTP请求管道。该解决方案基本上将cookie添加两次：一次使用SameSite，一次不使用。由于了解SameSite = None的浏览器，因此可以提供100％的浏览器兼容性。安全地使用它，而不了解它的浏览器将使用正常的cookie。这是Google最初提出的解决方案，由Auth0为其产品（采用其他形式）实施。
代码要点如下：
using System;
using System.Linq;
using System.Web;
namespace SameSiteHttpModule
{
public class SameSiteDoomsdayModule : IHttpModule
{
/// <summary>
/// Set up the event handlers.
/// </summary>
public void Init(HttpApplication context)
{
// This one is the OUTBOUND side; we add the extra cookie
context.PreSendRequestHeaders += OnEndRequest;
// This one is the INBOUND side; we coalesce the cookies.
context.BeginRequest += OnBeginRequest;
}
/// <summary>
/// The OUTBOUND LEG; we add the extra cookie.
/// </summary>
private void OnEndRequest(object sender, EventArgs e)
{
HttpApplication application = (HttpApplication)sender;
HttpContext context = application.Context;
// IF NEEDED: Add URL filter here
for (int i = 0; i < context.Response.Cookies.Count; i++)
{
HttpCookie responseCookie = context.Response.Cookies[i];
context.Response.Headers.Add("Set-Cookie", $"{responseCookie.Name}-same-site={responseCookie.Value};SameSite=None; Secure");
}
}
/// <summary>
/// The INBOUND LEG; we coalesce the cookies.
/// </summary>
private void OnBeginRequest(object sender, EventArgs e)
{
HttpApplication application = (HttpApplication)sender;
HttpContext context = application.Context;
// IF NEEDED: Add URL filter here
string[] keys = context.Request.Cookies.AllKeys;
for (int i = 0; i < context.Request.Cookies.Count; i++)
{
HttpCookie inboundCookie = context.Request.Cookies[i];
if (!inboundCookie.Name.Contains("-same-site"))
{
continue; // Not interested in this cookie.
}
// Check to see if we have a root cookie without the -same-site
string actualName = inboundCookie.Name.Replace("-same-site", string.Empty);
if (keys.Contains(actualName))
{
continue; // We have the actual key, so we are OK; just continue.
}
// We don't have the actual name, so we need to inject it as if it were the original
// https://support.microsoft.com/en-us/help/2666571/cookies-added-by-a-managed-httpmodule-are-not-available-to-native-ihtt
// HttpCookie expectedCookie = new HttpCookie(actualName, inboundCookie.Value);
context.Request.Headers.Add("Cookie", $"{actualName}={inboundCookie.Value}");
}
}
public void Dispose()
{
}
}
}
它像其他任何HTTP模块一样被安装：
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.webServer>
<modules>
<add type="SameSiteHttpModule.SameSiteDoomsdayModule, SameSiteHttpModule" name="SameSiteDoomsdayModule"/>
</modules>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath=".\IC.He.IdentityServices.exe" arguments="" forwardWindowsAuthToken="false" requestTimeout="00:10:00" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />
</system.webServer>
</configuration>
您可以在此处找到更多信息：https://charliedigital.com/2020/01/22/adventures-in-single-sign-on-samesite-doomsday/
它将为任何.NET版本，任何.NET Core版本和任何情况提供修补程序，无论您是否拥有原始源代码。
答案 2 :(得分：2)
approach outlined by Charles Chen（使用处理程序为设置了SameSite=None和Secure的每个cookie制作副本）的优点是实现起来不麻烦，并具有简单的兼容性方法使用不正确支持SameSite=None的浏览器。对于我的情况-支持较旧的.NET版本-这种方法是一种救命稻草，但是当尝试使用Charles的代码时，我遇到了一些问题，阻止了它按原样为我工作。
这是更新的代码，可以解决我遇到的问题：
using System;
using System.Collections.Generic;
using System.Text.RegularExpressions;
using System.Web;
namespace SameSiteHttpModule
{
public class SameSiteModule : IHttpModule
{
// Suffix includes a randomly generated code to minimize possibility of cookie copies colliding with original names
private const string SuffixForCookieCopy = "-same-site-j4J6bSt0";
private Regex _cookieNameRegex;
private Regex _cookieSameSiteAttributeRegex;
private Regex _cookieSecureAttributeRegex;
/// <inheritdoc />
/// <summary>
/// Set up the event handlers.
/// </summary>
public void Init(HttpApplication context)
{
// Initialize regular expressions used for making a cookie copy
InitializeMatchExpressions();
// This one is the OUTBOUND side; we add the extra cookies
context.PreSendRequestHeaders += OnPreSendRequestHeaders;
// This one is the INBOUND side; we coalesce the cookies
context.BeginRequest += OnBeginRequest;
}
/// <summary>
/// The OUTBOUND LEG; we add the extra cookie
/// </summary>
private void OnPreSendRequestHeaders(object sender, EventArgs e)
{
var application = (HttpApplication) sender;
var response = application.Context.Response;
var cookieCopies = CreateCookieCopiesToSave(response);
SaveCookieCopies(response, cookieCopies);
}
/// <summary>
/// The INBOUND LEG; we coalesce the cookies
/// </summary>
private void OnBeginRequest(object sender, EventArgs e)
{
var application = (HttpApplication) sender;
var request = application.Context.Request;
var cookiesToRestore = CreateCookiesToRestore(request);
RestoreCookies(request, cookiesToRestore);
}
#region Supporting code for saving cookies
private IEnumerable<string> CreateCookieCopiesToSave(HttpResponse response)
{
var cookieStrings = response.Headers.GetValues("set-cookie") ?? new string[0];
var cookieCopies = new List<string>();
foreach (var cookieString in cookieStrings)
{
bool createdCopy;
var cookieStringCopy = TryMakeSameSiteCookieCopy(cookieString, out createdCopy);
if (!createdCopy) continue;
cookieCopies.Add(cookieStringCopy);
}
return cookieCopies;
}
private static void SaveCookieCopies(HttpResponse response, IEnumerable<string> cookieCopies)
{
foreach (var cookieCopy in cookieCopies)
{
response.Headers.Add("set-cookie", cookieCopy);
}
}
private void InitializeMatchExpressions()
{
_cookieNameRegex = new Regex(@"
(?'prefix' # Group 1: Everything prior to cookie name
^\s* # Start of value followed by optional whitespace
)
(?'cookie_name' # Group 2: Cookie name
[^\s=]+ # One or more characters that are not whitespace or equals
)
(?'suffix' # Group 3: Everything after the cookie name
.*$ # Arbitrary characters followed by end of value
)",
RegexOptions.IgnoreCase | RegexOptions.Compiled | RegexOptions.IgnorePatternWhitespace);
_cookieSameSiteAttributeRegex = new Regex(@"
(?'prefix' # Group 1: Everything prior to SameSite attribute value
^.* # Start of value followed by 0 or more arbitrary characters
;\s* # Semicolon followed by optional whitespace
SameSite # SameSite attribute name
\s*=\s* # Equals sign (with optional whitespace around it)
)
(?'attribute_value' # Group 2: SameSite attribute value
[^\s;]+ # One or more characters that are not whitespace or semicolon
)
(?'suffix' # Group 3: Everything after the SameSite attribute value
.*$ # Arbitrary characters followed by end of value
)",
RegexOptions.IgnoreCase | RegexOptions.Compiled | RegexOptions.IgnorePatternWhitespace);
_cookieSecureAttributeRegex = new Regex(@"
;\s* # Semicolon followed by optional whitespace
Secure # Secure attribute value
\s* # Optional whitespace
(?:;|$) # Semicolon or end of value",
RegexOptions.IgnoreCase | RegexOptions.Compiled | RegexOptions.IgnorePatternWhitespace);
}
private string TryMakeSameSiteCookieCopy(string cookie, out bool success)
{
if (!AddNameSuffix(ref cookie))
{
// could not add the name suffix so unable to copy cookie (generally should not happen)
success = false;
return null;
}
var addedSameSiteNone = AddSameSiteNone(ref cookie);
var addedSecure = AddSecure(ref cookie);
if (!addedSameSiteNone && !addedSecure)
{
// cookie already has SameSite and Secure attributes so don't make copy
success = false;
return null;
}
success = true;
return cookie;
}
private bool AddNameSuffix(ref string cookie)
{
var match = _cookieNameRegex.Match(cookie);
if (!match.Success)
{
// Could not find the cookie name in order to modify it
return false;
}
var groups = match.Groups;
var nameForCopy = groups["cookie_name"] + SuffixForCookieCopy;
cookie = string.Concat(groups["prefix"].Value, nameForCopy, groups["suffix"].Value);
return true;
}
private bool AddSameSiteNone(ref string cookie)
{
var match = _cookieSameSiteAttributeRegex.Match(cookie);
if (!match.Success)
{
cookie += "; SameSite=None";
return true;
}
var groups = match.Groups;
if (groups["attribute_value"].Value.Equals("None", StringComparison.OrdinalIgnoreCase))
{
// SameSite=None is already present, so we will not add it
return false;
}
// Replace existing SameSite value with "None"
cookie = string.Concat(groups["prefix"].Value, "None", groups["suffix"].Value);
return true;
}
private bool AddSecure(ref string cookie)
{
if (_cookieSecureAttributeRegex.IsMatch(cookie))
{
// Secure is already present so we will not add it
return false;
}
cookie += "; Secure";
return true;
}
#endregion
#region Supporting code for restoring cookies
private static IEnumerable<HttpCookie> CreateCookiesToRestore(HttpRequest request)
{
var cookiesToRestore = new List<HttpCookie>();
for (var i = 0; i < request.Cookies.Count; i++)
{
var inboundCookie = request.Cookies[i];
if (inboundCookie == null) continue;
var cookieName = inboundCookie.Name;
if (!cookieName.EndsWith(SuffixForCookieCopy, StringComparison.OrdinalIgnoreCase))
{
continue; // Not interested in this cookie since it is not a copied cookie.
}
var originalName = cookieName.Substring(0, cookieName.Length - SuffixForCookieCopy.Length);
if (request.Cookies[originalName] != null)
{
continue; // We have the original cookie, so we are OK; just continue.
}
cookiesToRestore.Add(new HttpCookie(originalName, inboundCookie.Value));
}
return cookiesToRestore;
}
private static void RestoreCookies(HttpRequest request, IEnumerable<HttpCookie> cookiesToRestore)
{
// We need to inject cookies as if they were the original.
foreach (var cookie in cookiesToRestore)
{
// Add to the cookie header for non-managed modules
// https://support.microsoft.com/en-us/help/2666571/cookies-added-by-a-managed-httpmodule-are-not-available-to-native-ihtt
if (request.Headers["cookie"] == null)
{
request.Headers.Add("cookie", $"{cookie.Name}={cookie.Value}");
}
else
{
request.Headers["cookie"] += $"; {cookie.Name}={cookie.Value}";
}
// Also add to the request cookies collection for managed modules.
request.Cookies.Add(cookie);
}
}
#endregion
public void Dispose()
{
}
}
}
此代码处理的一些问题：
Path和Expires之类的属性，这些属性对于网站的正常运行是必不可少的。Cookie标头之外，还将它们添加到.NET HttpRequest.Cookies集合中，这对于避免丢失ASP.NET会话是必需的。 / li>
Cookie标头，这与RFC 6265相反，并且可能导致应用程序出现问题。一些部署选项：
配置（例如，用于web.config）：
<system.webServer>
...
<modules>
<add name="SameSiteModule" type="SameSiteHttpModule.SameSiteModule, CustomSameSiteModule" />
p.s。查尔斯，我是var的粉丝，对不起：）
答案 3 :(得分：1)
最新版本的.NET Framework和.NET Core现在已解决该问题。
正如我在另一篇文章http://code4projects.altervista.org/getting-started-with-docker/中所发布的那样，cookie选项SameSiteMode.None现在可以正常使用。
答案 4 :(得分：1)
使用Microsoft.Net.Http.Headers 2.2.8为我解决了该问题。当前使用的目标框架：.Net Core 2.2用于项目。