Option to add "Translate: F" header for IIS compatibility
Brought to you by:
wdonne
Menu
▾
▴
#12 Option to add "Translate: F" header for IIS compatibility
It would be nice if there was an option to add a "Translate: F" header to each GET request. Microsoft IIS sometimes excepts it, for example when one wants to get files with extensions unknown to the HTTP server. If one tries to download a file with an "unknown" file extension and the "Translate: F" header is missing, IIS will return a 404 error.
See the davfs2's bug report #107510
Can this header be set for files for which the server does know the extension, without harm? This is just to know if it can become a global option on the command-line and in the configuration file.
Yes, it can be always set, at least for Microsoft's server implementations.
--
Last edit: Iiro Laiho 2017-04-29
With this patch applied, the "Translate: F" header is always attached. I am not sure if it is necessary to make it optional or not. After all the built-in clients in Windows and macOS have similar behavior (always send that header) and I am not aware of any ill-effects anywhere. It is however certainly theoretically possible that some WebDAV server somewhere will choke on that header.
Fixed in release 1.1.8.