When using ThrowOnUnknownSessionKey = false; with the options, it allows you to ignore keys that aren't yet mapped. However, those session values are nulled out rather than ignored. I'm not sure if this is intentional, but when converting large sites a page at a time, it would make sense if there was a way to completely ignore these keys that you don't need yet.
To Reproduce
.NET Framework Side:
Configure to not throw on unknown keys and only register one key but then set 2 different keys in session:
.NET 8 Side:
Configure to not throw on unknown keys and only register one key, view both keys and note that only 1 is set:
Load the .NET Framework side again and note test2 is now null:
Describe the bug
When using ThrowOnUnknownSessionKey = false; with the options, it allows you to ignore keys that aren't yet mapped. However, those session values are nulled out rather than ignored. I'm not sure if this is intentional, but when converting large sites a page at a time, it would make sense if there was a way to completely ignore these keys that you don't need yet.
To Reproduce
.NET Framework Side:
Configure to not throw on unknown keys and only register one key but then set 2 different keys in session:
.NET 8 Side:
Configure to not throw on unknown keys and only register one key, view both keys and note that only 1 is set:
Load the .NET Framework side again and note test2 is now null:
Further technical details
Please include the following if applicable:
ASP.NET Framework Application:
ASP.NET Core Application: