Skip to content

Documentation Clarity in the "CookieSecurePolicy" in the AntiForgeryOptions #3670

@akshita31

Description

@akshita31

The AntiForgeryOptions say that the default CookieSecurePolicy in "None". However, the "CookieSecurePolicy" enum says that the default value is "SameAsRequest". While working with the project I navigated to the "CookieSecurePolicy" and assumed that the default must be "SameAsRequest".

I am not sure whether this is really an issue or it is a common scenario where we create default objects with the enum types that don't use the default enum value, but I thought it might be worth to bring to your notice if it somehow got ignored.

Metadata

Metadata

Assignees

No one assigned

    Labels

    DoneThis issue has been fixedarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsfeature-http-abstractionshelp wantedUp for grabs. We would accept a PR to help resolve this issue

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions