Author Topic: UTF-8 encoding for outgoing HTTP headers  (Read 1263 times)

0 Members and 1 Guest are viewing this topic.


  • Guest
UTF-8 encoding for outgoing HTTP headers
« on: December 04, 2009, 08:56:54 AM »

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.

Offline rejetto

  • Administrator
  • Tireless poster
  • *
  • Posts: 12953
    • View Profile
Re: UTF-8 encoding for outgoing HTTP headers
« Reply #1 on: December 08, 2009, 11:57:13 AM »
next beta release will address this problem.
please give feedback when you can test it.