phantomtypist

FYI Memcached worked completed in new repo over at [https://github.com/apereo/dotnet-cas-client-memcached/](https://github.com/apereo/dotnet-cas-client-memcached/) [DotNetCasClient.Memcached](https://www.nuget.org/packages/DotNetCasClient.Memcached/) NuGet package now available GitHubapereo/dotnet-cas-client-memcachedContribute to apereo/dotnet-cas-client-memcached development by creating an account on GitHub.

FYI Redis work completed in new repo over at https://github.com/apereo/dotnet-cas-client-redis/ DotNetCasClient.Redis NuGet package now available GitHubapereo/dotnet-cas-client-redisContribute to apereo/dotnet-cas-client-redis development by creating an account on GitHub.

@TheHokieCoder the only thing left on this issue to work on is the SQL Server provider. I think you said last time we spoke it was almost done? I'm fine...

Which versions of IE does this effect?

Did you also try the most recent version of the nuget package to see if the problem actually still existed? The problem they described in the four year old blog...

@jffcovey you didn't have to close the issue, just answer the questions I asked. I mean, you put in all that effort writing that blog post back in 2017 and...

What version of TLS is both the web application server running and the CAS server running? What version of. Net is your application compiled against (be specific)

Uh, @nightBaker why do you keep closing and re-opening pull requests? You can just keep continuing your changes on a single pull request and push the changes to it as...

@nightBaker You'll also need to tell us when you are done making changes to the PR... otherwise I have no clue when you are done making changes... which is why...

@nightBaker You say you fixed the problem for the .NET 4.x code path. Question: does the problem exist in the .NET 2/3.x code path? If _yes_, then have you fixed...