CODEWITHSUNDEEP
javams-wordwebdav
scoulou
scoulou

Reputation: 47

Issue with microsoft word url encoding during webdav protocol

We have :

The urls to open our files end with the files' names, and are encoded in UTF-8 before to be sent to the UI :

server.com/path/my_file_name.doc

It works perfectly with file names without special characters but with an ugly url like

server.com/path/En-tête de lettre + capital 1 050 000 €.doc

, our server does not manage to access to the file. In the stack trace, we can see that the url received by the server is

server.com/path/En-tête de lettre + capital 1 050 000 �.doc

, but the error message that ms-word is displaying contains the right url, so I think that the original url is right.

And last but not least : it works when the server is running on a windows platform.

I suppose that ms-word re-encodes the url before transmitting it to the server, but I can't guess how to decode it.

All suggestions are welcome ^^

Upvotes: 0

Views: 1940

Answers (1)

Brad at Kademi
Brad at Kademi

Reputation: 1320

I'm the author of http://milton.io (java webdav server lib) and I've seen an issue where MS clients do incorrect encoding of some url's, and milton has some workarounds for that. What webdav framework/server are you using?

However, the example given looks more like mangling, as suggested by Marc B. Your server is probably outputting the propfind response in UTF-8, but windows is interpreting it as win-1252.

So you should look at the response headers and check to see what character encoding is given for the response and check that it matches the actual encoding used in the PROPFIND response.

Note that earlier versions of milton had a problem where they would use the server default encoding but always report UTF-8, so this problem would occur on any server not using UTF-8 as the default character encoding.

Upvotes: 1

Related Questions