madelson

Another upvote for this; this feels really important. I imagine that this could be quite simple (since the code should be the same between SDS and MDS). **Would the team...

This would be cool. I could see using this to expose certain "unsafe" methods from a library to transient scripts that you wouldn't want to expose to normal consumers.

We just got burned by this as well. When is the fix for this expected?

This feels like a pretty big limitation. Is there a plan to fix this? Would you accept a PR?

@mafurman thanks for looking into this. Any findings so far? Do you need anything from me?

Hi @mafurman apologies for bumping this again but I was wondering if you could give me a sense of when someone would be able to look into this issue? This...

We were able to work around this issue for now by using `SignedXml`. That has the same (and possibly worse) bugs but I found a workaround in the context of...

@zlangner https://www.nuget.org/packages/DistributedLock.Redis/ supports semaphores FWIW.

@Doraku yes the solution you linked there should work and fixes the nesting problem. However, doesn't `?` have special meaning in URLs (starts the query string?). I could see this...

Another option would be to use a custom alphabet for the encoding, for example all upper-case letters and digits (36 chars): ``` Encode(md5, "0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ"); static string Encode(byte[] hash, ReadOnlySpan alphabet)...