dotnet/aspnetcore

Allow customization of cookie consent value for more flexibility

Open

#39,597 opened on Jan 18, 2022

View on GitHub
 (6 comments) (0 reactions) (0 assignees)C# (10,653 forks)batch import
area-networkinghelp wanted

Repository metrics

Stars
 (37,933 stars)
PR merge metrics
 (Avg merge 16d 9h) (258 merged PRs in 30d)

Description

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

We are setting the consent cookie for the eTLD+1 with the value 1 if the user agreed with an expiration of 1 year and with the value -1 with an expiration for the session when the user disagreed. This kind of flexibility is currently not possible with the build-in cookie consent feature of asp net core.

Describe the solution you'd like

A way to customize the validation of the HasConsent in the ResponseCookiesWrapper

Additional context

No response

Contributor guide

Research direction
Examine the ResponseCookiesWrapper class and the HasConsent logic to understand how to introduce a customizable validation delegate.
Tech stack
csharp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#ASP.NET Core
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65