Hello,
HFS seems to be all Unicode - both in the HTML directory listings it generates and HTTP headers it accepts. However, when it generates headers like Location, they are in a single-byte encoding, whatever is the server default. This can be demonstrated with requests like
GET
http://server/UnicodeFolderName HTTP/1.1
HFS sends a 301 response
HTTP/1.1 301 Moved Permanently
Location:
http://server/UnicodeFolderName/where both the Location header and the response body are in single-byte encoding.
This might be ok for the browser, but not for the proxy, especially if it has some complex URL-processing logic. The UnicodeFolderName is garbled and produces errors.
Please consider fixing it. Thanks.
