Actually, with the content server it may be possible to use RFC 6266 (which is not yet a standard but widely supported) to have non-ascii filenames in the content-disposition header. It would need testing on a wide variety of browsers/devices to ensure it does not break things.
|