ucp WebDAV provider returns Content-Type header value, but...

Giuseppe Castagno giuseppe.castagno at acca-esse.eu
Mon Feb 1 11:31:11 CET 2016

Hi all,

These commits:


fixed a problem preventing MediaType from getting the value of 
Content-Type header form a Web resource.

Following two Gerrit patch set propose the same for 5.1 branch.


I'd like to preserve the sequence so I cherry-picked (-x) them 
externally, not sure I did the right thing.

Checked them, fix tdf#95217 in 5.1 as well.

With both patch applied the value contained in MediaType prop is now not 
empty, but being a value under a web server control, it may not be right.

This excerpt from <http://tools.ietf.org/html/rfc7231#section-> 
tells you that:
In practice, resource owners do not always properly configure their
origin server to provide the correct Content-Type for a given

Furthermore, in some WebDAV read/only server, I found that 
'Content-type' header and 'DAV:getcontenttype' values are different, 
instead of being the same as stated in section 15.5 of RFC4918

As an example accessing the hybrid web site resource:

LO gets, using GET:

Content-Type: text/plain

while PROFIND:

DAV:getcontenttype:text/xml; charset="utf-8"

In this case (a WebDAV site) MediaType prop returns DAV:getcontenttype 

Kind Regards,
Giuseppe Castagno aka beppec56
Acca Esse http://www.acca-esse.eu
giuseppe.castagno at acca-esse.eu

More information about the LibreOffice mailing list