LCB_ERR_INVALID_CHAR when interrogating a view with a key containing something that looks like a URI-encoded char

It seems that when a view is interrogated with a key containing a string that looks like an URI-encoded character, the library says LCB_ERR_INVALID_CHAR.

For instance, when the key contains %20, the error is produced.

I guess that the library URI-encodes everything, but %20 is a valid key and can be URI-encoded as %2520.

Thanks!