Hi all,
These commits:
<https://gerrit.libreoffice.org/gitweb?p=core.git;a=commitdiff;h=e973b342826e54f147251b132c3325d30749e312>
<https://gerrit.libreoffice.org/gitweb?p=core.git;a=commitdiff;h=d61352f58a7f750d3b0b0a9c2d6498fbb7a6e10d>
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.
<https://gerrit.libreoffice.org/#/c/21987/1>
<https://gerrit.libreoffice.org/#/c/21988/1>
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-3.1.1.5>
tells you that:
"
...
In practice, resource owners do not always properly configure their
origin server to provide the correct Content-Type for a given
representation,....
"
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
<http://tools.ietf.org/html/rfc4918#section-15>
As an example accessing the hybrid web site resource:
<http://unladen-swallow.googlecode.com/svn/trunk/LICENSE>
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
value.
--
Kind Regards,
Giuseppe Castagno aka beppec56
Acca Esse http://www.acca-esse.eu
giuseppe.castagno at acca-esse.eu
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
