HTTP requests made by the WebDAV UCB content provider do not include an HTTP
User-Agent header.

Many WebDAV clients have quirks that may be worked around on the DAV server, and
the User-Agent header is typically used to identify the client being used and
the server-side adjustments (if any) that need to be made to accommodate that
client.  The lack of a User-Agent header makes client identification and the
related adjustment of server behavior much more difficult.

Here is an example PROPFIND request with no User-Agent, captured while opening a
file using OpenOffice 3.1.1:

PROPFIND /test/test.doc HTTP/1.1

Host: mysite
Keep-Alive: 

Connection: TE, Keep-Alive

TE: trailers

Depth: 0

Content-Length: 207

Content-Type: application/xml

Pragma: no-cache



<?xml version="1.0" encoding="utf-8"?>
<propfind xmlns="DAV:"><prop>
<resourcetype xmlns="DAV:"/>
<IsReadOnly xmlns="http://ucb.openoffice.org/dav/props/"/>
<getcontenttype xmlns="DAV:"/>
</prop></propfind>