Skip to content

Update API for SameSitemode #3569

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 11 commits into from
Nov 26, 2019
17 changes: 15 additions & 2 deletions xml/System.Web/SameSiteMode.xml
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,20 @@
</Base>
<Docs>
<summary>Specifies constants that indicate the value for the SameSite attribute of the cookie.</summary>
<remarks>To be added.</remarks>
<remarks>
<format type="text/markdown"><![CDATA[

## Remarks

The <see cref="F:System.Web.SameSiteMode.None" /> value now causes ASP.NET to emit a SameSite cookie header to accommodate upcoming changes to SameSite cookie handling in Chrome. As part of this change, FormsAuth and SessionState cookies will be issued with SameSite = 'Lax' instead of the previous default of 'None', though these values can be overridden in web.config.

Before these updates have been applied, the <see cref="F:System.Web.SameSiteMode.None" /> does not emit the `SameSite` cookie header.

For more information on this behavior see [KB article 4531182](https://support.microsoft.com/help/4531182/kb4531182) or [KB article 4524421](https://support.microsoft.com/help/4524421/kb4524421).

On systems where these updates have been applied, you can specify the previous behavior by setting the `SameSiteMode` to `(SameSiteMode)(-1)`.
]]></format>
</remarks>
</Docs>
<Members>
<Member MemberName="Lax">
Expand Down Expand Up @@ -54,7 +67,7 @@
</ReturnValue>
<MemberValue>0</MemberValue>
<Docs>
<summary>No mode is specified.</summary>
<summary>Emits "SameSite=None" (see remarks).</summary>
</Docs>
</Member>
<Member MemberName="Strict">
Expand Down