I don't know how common WebDAV servers handle this, but I think it's a bad idea.
Just the risk of damaging binary files that are thought to be text, as you mentioned, makes it not worth doing. Here are some more disadvantages:
- Breaks the model of the WebDAV server as a simple storage and retrieval device. As a user:
- I'd view this as mangling my files.
- I'd have to spend time figuring out how and why my files had changed.
- Then I'd wonder what other things the server might be doing to my files on my behalf.
- Changes line endings based on the server's OS, not the client's (customer's).
If I'm a Windows-only or Unix-only user, then all my line endings are right for me, and I don't want the server changing them. If I use both, then I already have tools that are either insensitive to the line endings or can convert between them.
My experience with text-processing client programs in recent years is that they're all insensitive to line endings. XML parsers and script interpreters, for example, can work with either style of line ending. So I don't see much benefit to offset the risk.