thanks for reporting klausr.
actually, the encoding by apache was not due, and it is better it now doesn't.
while such encoding is not advisable, it is allowed by the protocol (i think), and so i considered it an HFS bug, to handle it incorrectly.
the result is that HFS 2.3 handles such problematic request successfully.
sadly, i forgot to include this fix in last 2.2 release. And i guess i won't, since i hope 2.3 will go stable soon.