Is there an existing issue for this?
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
Is there an existing issue for this?
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