Closed undu closed 11 years ago
Hello undu, thank you for your detailed report and investigations!
But it seems that this is a duplicate of #273, which really was a problem with the way cherrypy handles unicode characters, just like you diagnosed.
A workaround was applied to the devel branch af8ad67709b7befeb6ddf53646dd02d6fe756a31. Please check out the devel branch and see if this resolves your problem. If it doesn't, just reopen this issue and we'll see what's going wrong.
Woops, that's what I get for not cheking throughtly first.
It works great in the devel branch, thanks!
Right now, the transcoding module doesn't deal well with multibyte characters in the fails and generates and error when trying to transcode it.
I'm using the master branch, notice how in the GET command, the string shows utf-8 codes, but in the exception at the end the name of the file is written in plain ASCII.
I've checked the code, the issue seems to be the code in the server that handles the filepath and calls HTTPHandler.trans() at httphandler.py, as the string is already malformed there and the webclient seems to generate correctly the string.
Maybe it's related to how Cherrypy handles the string?