Consider normalizing path used for Discriminator
Closed this issue · 3 comments
From @BrennanConroy on Tuesday, September 19, 2017 9:13:00 AM
One specific instance where I hit this was running an app from the command line produced a cookie in my browser. And then running the exact same app without any changes from VS Code would fail to unprotect the cookie because VS Code environment returned e:/...
and command line environment returned E:/...
Copied from original issue: aspnet/DataProtection#276
From @blowdart on Friday, October 13, 2017 12:03:13 PM
This would probably end up being platform specific - because it shouldn't be case sensitive on windows, but should on linux.
Is there a path normalization function? (You'd be doing the work yourself anyway)
Looks like the decision in the referenced issues was Won't fix
. @blowdart should this be closed then?