Set-Cookie is being set on redirection in ASP.NET MVC on .NET 4.7.2 . Why?
I am setting SameSite
in Startup.Auth.cs
like this:
Set-Cookie is being set on redirection in ASP.NET MVC on .NET 4.7.2 . Why?
I am setting SameSite
in Startup.Auth.cs
like this:
Set-Cookie is being set on redirection in ASP.NET MVC on .NET 4.7.2 . Why?
I am setting SameSite
in Startup.Auth.cs
like this:
Set-Cookie is being set on redirection in ASP.NET MVC on .NET 4.7.2 . Why?
I am setting SameSite
in Startup.Auth.cs
like this:
Set-Cookie is being set on redirection in ASP.NET MVC on .NET 4.7.2 . Why?
I am setting SameSite
in Startup.Auth.cs
like this:
Set-Cookie is being set on redirection in ASP.NET MVC on .NET 4.7.2 . Why?
I am setting SameSite
in Startup.Auth.cs
like this:
Set-Cookie is being set on redirection in ASP.NET MVC on .NET 4.7.2 . Why?
I am setting SameSite
in Startup.Auth.cs
like this:
Set-Cookie is being set on redirection in ASP.NET MVC on .NET 4.7.2 . Why?
I am setting SameSite
in Startup.Auth.cs
like this:
Set-Cookie is being set on redirection in ASP.NET MVC 4.7.2 . Why?
I am setting SameSite in Startup.Auth.cs like:
CookiePath = “/; SameSite=Lax”,
But for Login action, on redirection; the Set-Cookie value is being automatically set by the Framework and not by code. The issue is that the Set-Cookie that is a Response Header is having .AspNet.ApplicationCookie as its value. This is a very big vulnerability as the Cookie is being exposed as part of response.