| 1 |
<pre>Network Working Group J. Reschke |
| 2 |
Request for Comments: 4709 greenbytes |
| 3 |
Category: Informational October 2006 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Mounting Web Distributed Authoring and Versioning (WebDAV) Servers</span> |
| 7 |
|
| 8 |
Status of This Memo |
| 9 |
|
| 10 |
This memo provides information for the Internet community. It does |
| 11 |
not specify an Internet standard of any kind. Distribution of this |
| 12 |
memo is unlimited. |
| 13 |
|
| 14 |
Copyright Notice |
| 15 |
|
| 16 |
Copyright (C) The Internet Society (2006). |
| 17 |
|
| 18 |
Abstract |
| 19 |
|
| 20 |
In current Web browsers, there is no uniform way to specify that a |
| 21 |
user clicking on a link will be presented with an editable view of a |
| 22 |
Web Distinguished Authoring and Versioning (WebDAV) server. For |
| 23 |
example, it is frequently desirable to be able to click on a link and |
| 24 |
have this link open a window that can handle drag-and-drop |
| 25 |
interaction with the resources of a WebDAV server. |
| 26 |
|
| 27 |
This document specifies a mechanism and a document format that |
| 28 |
enables WebDAV servers to send "mounting" information to a WebDAV |
| 29 |
client. The mechanism is designed to work on any platform and with |
| 30 |
any combination of browser and WebDAV client, relying solely on the |
| 31 |
well-understood dispatch of documents through their MIME type. |
| 32 |
|
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Reschke Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc4709">RFC 4709</a> Mounting WebDAV Servers October 2006</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a> |
| 60 |
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a> |
| 61 |
<a href="#section-3">3</a>. Format ..........................................................<a href="#page-3">3</a> |
| 62 |
<a href="#section-3.1">3.1</a>. dm:mount ...................................................<a href="#page-4">4</a> |
| 63 |
<a href="#section-3.2">3.2</a>. dm:url .....................................................<a href="#page-4">4</a> |
| 64 |
<a href="#section-3.3">3.3</a>. dm:open ....................................................<a href="#page-4">4</a> |
| 65 |
<a href="#section-3.4">3.4</a>. dm:username ................................................<a href="#page-4">4</a> |
| 66 |
<a href="#section-4">4</a>. Example .........................................................<a href="#page-4">4</a> |
| 67 |
<a href="#section-5">5</a>. Internationalization Considerations .............................<a href="#page-5">5</a> |
| 68 |
<a href="#section-6">6</a>. IANA Considerations .............................................<a href="#page-6">6</a> |
| 69 |
<a href="#section-6.1">6.1</a>. MIME Type Registration .....................................<a href="#page-6">6</a> |
| 70 |
<a href="#section-7">7</a>. Security Considerations .........................................<a href="#page-8">8</a> |
| 71 |
<a href="#section-8">8</a>. Acknowledgements ................................................<a href="#page-8">8</a> |
| 72 |
<a href="#section-9">9</a>. References ......................................................<a href="#page-9">9</a> |
| 73 |
<a href="#section-9.1">9.1</a>. Normative References .......................................<a href="#page-9">9</a> |
| 74 |
<a href="#section-9.2">9.2</a>. Informative References .....................................<a href="#page-9">9</a> |
| 75 |
<a href="#appendix-A">Appendix A</a>. Alternative Approaches ...............................<a href="#page-10">10</a> |
| 76 |
<a href="#appendix-A.1">A.1</a>. ...Through HTML/CSS Extensions ............................<a href="#page-10">10</a> |
| 77 |
<a href="#appendix-A.2">A.2</a>. ...Through Custom URI Schemes .............................<a href="#page-10">10</a> |
| 78 |
<a href="#appendix-B">Appendix B</a>. Implementations ......................................<a href="#page-10">10</a> |
| 79 |
<a href="#appendix-B.1">B.1</a>. Example Implementation for Webfolder Client ...............<a href="#page-10">10</a> |
| 80 |
<a href="#appendix-B.2">B.2</a>. Xythos ....................................................<a href="#page-14">14</a> |
| 81 |
|
| 82 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 83 |
|
| 84 |
By definition, a Web Distributed Authoring and Versioning (WebDAV) |
| 85 |
server ([<a href="./rfc2518" title=""HTTP Extensions for Distributed Authoring -- WEBDAV"">RFC2518</a>]) is an HTTP server as well ([<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>]). Most |
| 86 |
WebDAV servers can be (at least partly) operated from an HTML-based |
| 87 |
user interface in a web browser. However, it is frequently desirable |
| 88 |
to be able to switch from an HTML-based view to a presentation |
| 89 |
provided by a native WebDAV client, directly supporting the authoring |
| 90 |
features defined in WebDAV and related specifications. |
| 91 |
|
| 92 |
This document specifies a platform-neutral mechanism based on the |
| 93 |
dispatch of documents through their MIME type. For completeness, |
| 94 |
<a href="#appendix-A">Appendix A</a> lists other approaches that have been implemented in |
| 95 |
existing clients. |
| 96 |
|
| 97 |
For example, many educational institutions use WebDAV servers as a |
| 98 |
mechanism for sharing documents among students. Each student owns a |
| 99 |
separate collection structure on a WebDAV server, often called his/ |
| 100 |
her "locker". Ideally, when users click on a link in an HTML page |
| 101 |
provided by the university (perhaps by their university Web portal), |
| 102 |
an editable view of their locker will appear. |
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Reschke Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc4709">RFC 4709</a> Mounting WebDAV Servers October 2006</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 114 |
|
| 115 |
The terminology used here follows that in the WebDAV Distributed |
| 116 |
Authoring Protocol specification [<a href="./rfc2518" title=""HTTP Extensions for Distributed Authoring -- WEBDAV"">RFC2518</a>]. |
| 117 |
|
| 118 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 119 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 120 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 121 |
|
| 122 |
This document uses XML DTD fragments ([<a href="#ref-XML" title=""Extensible Markup Language (XML) 1.0 (Fourth Edition)"">XML</a>]) as a purely notational |
| 123 |
convention. In particular: |
| 124 |
|
| 125 |
o Element names use the namespace |
| 126 |
"<a href="http://purl.org/NET/webdav/mount">http://purl.org/NET/webdav/mount</a>". When an XML element type in |
| 127 |
this namespace is referenced in this document outside of the |
| 128 |
context of an XML fragment, the string "dm:" will be prefixed to |
| 129 |
the element name. |
| 130 |
|
| 131 |
o Element ordering is irrelevant. |
| 132 |
|
| 133 |
o Extension elements/attributes (elements/attributes not already |
| 134 |
defined as valid child elements) may be added anywhere, except |
| 135 |
when explicitly stated otherwise. |
| 136 |
|
| 137 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Format</span> |
| 138 |
|
| 139 |
A WebDAV mount request is encoded in a specific XML format ([<a href="#ref-XML" title=""Extensible Markup Language (XML) 1.0 (Fourth Edition)"">XML</a>]) |
| 140 |
with a well-defined MIME type (see <a href="#section-6.1">Section 6.1</a>). The MIME type |
| 141 |
allows user agents to dispatch the content to a handler specific to |
| 142 |
the system's WebDAV client. |
| 143 |
|
| 144 |
The elements defined below use the namespace |
| 145 |
"<a href="http://purl.org/NET/webdav/mount">http://purl.org/NET/webdav/mount</a>". |
| 146 |
|
| 147 |
<!ELEMENT mount (url, open?, username?) > |
| 148 |
|
| 149 |
<!ELEMENT url (#PCDATA) > |
| 150 |
<!-- PCDATA value: scheme ":" hier-part, as defined in <a href="./rfc3986#section-3">Section 3 of |
| 151 |
[RFC3986]</a> --> |
| 152 |
|
| 153 |
<!ELEMENT open (#PCDATA) > |
| 154 |
<!-- PCDATA value: path, as defined in <a href="./rfc3986#section-3">Section 3 of |
| 155 |
[RFC3986]</a> --> |
| 156 |
|
| 157 |
<!ELEMENT username (#PCDATA) > |
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Reschke Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc4709">RFC 4709</a> Mounting WebDAV Servers October 2006</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. dm:mount</span> |
| 170 |
|
| 171 |
The <dm:mount> element acts as a container for all the remaining |
| 172 |
elements defined by this protocol. |
| 173 |
|
| 174 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. dm:url</span> |
| 175 |
|
| 176 |
The mandatory <dm:url> element provides the HTTP URL of the WebDAV |
| 177 |
collection that should be mounted by the client. |
| 178 |
|
| 179 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. dm:open</span> |
| 180 |
|
| 181 |
The optional <dm:open> element instructs the client to display the |
| 182 |
specified child collection; its URL is computed by concatenating this |
| 183 |
element's value with the URL obtained from the <dm:url> (<a href="#section-3.2">Section 3.2</a>) |
| 184 |
element (see <a href="#section-7">Section 7</a> for a discussion about why this element only |
| 185 |
supports displaying collections rather than opening arbitrary |
| 186 |
documents). |
| 187 |
|
| 188 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. dm:username</span> |
| 189 |
|
| 190 |
The server can use the optional <dm:username> element to specify the |
| 191 |
name of the currently authenticated principal. A client can use this |
| 192 |
value to select a matching mount point (different users may have |
| 193 |
mounted the URL with different credentials under different local |
| 194 |
mount points) or to provide a meaningful default for authentication |
| 195 |
against the server. It is common that a browser and WebDAV client do |
| 196 |
not share HTTP connections, so including this information in the |
| 197 |
mount document increases usability. |
| 198 |
|
| 199 |
Implementation Note: If a <dm:username> element is present, public |
| 200 |
caching of the document should be disallowed. Thus, appropriate |
| 201 |
'Vary' or 'Cache-Control' headers are needed in the server response. |
| 202 |
|
| 203 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Example</span> |
| 204 |
|
| 205 |
In the example below, the client first retrieves a representation of |
| 206 |
a WebDAV collection using a generic Web browser (1). The returned |
| 207 |
HTML content contains a hyperlink that identifies the "davmount" |
| 208 |
document in the format defined in <a href="#section-3">Section 3</a> (2). The user follows |
| 209 |
this link (3), which causes the server to return the "davmount" |
| 210 |
document to the user's browser (4). The browser in turn passes the |
| 211 |
content to the application that was registered to handle the |
| 212 |
"application/davmount+xml" MIME type, usually the default WebDAV |
| 213 |
client on the client's system. |
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Reschke Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc4709">RFC 4709</a> Mounting WebDAV Servers October 2006</span> |
| 223 |
|
| 224 |
|
| 225 |
(1) Client retrieves representation of WebDAV collection "/user42/ |
| 226 |
inbox/". |
| 227 |
|
| 228 |
GET /user42/inbox/ HTTP/1.1 |
| 229 |
Host: www.example.com |
| 230 |
|
| 231 |
(2) Server returns representation. |
| 232 |
|
| 233 |
HTTP/1.1 200 OK |
| 234 |
Content-Type: text/html |
| 235 |
Content-Length: xxx |
| 236 |
|
| 237 |
.. |
| 238 |
<a href="?action=davmount">View this collection in your |
| 239 |
WebDAV client</a> |
| 240 |
.. |
| 241 |
|
| 242 |
(note that the example shows only that part of the HTML page that |
| 243 |
contains the relevant link) |
| 244 |
|
| 245 |
(3) Client follows link to "davmount" document |
| 246 |
|
| 247 |
GET /user42/inbox/?action=davmount HTTP/1.1 |
| 248 |
Host: www.example.com |
| 249 |
|
| 250 |
(4) Server returns "davmount" document |
| 251 |
|
| 252 |
HTTP/1.1 200 OK |
| 253 |
Content-Type: application/davmount+xml |
| 254 |
Content-Length: xxx |
| 255 |
Cache-Control: private |
| 256 |
|
| 257 |
<dm:mount xmlns:dm="http://purl.org/NET/webdav/mount"> |
| 258 |
<dm:url>http://www.example.com/user42/</dm:url> |
| 259 |
<dm:open>inbox/</dm:open> |
| 260 |
</dm:mount> |
| 261 |
|
| 262 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Internationalization Considerations</span> |
| 263 |
|
| 264 |
This document does not introduce any new internationalization |
| 265 |
considerations beyond those discussed in <a href="./rfc2518#section-16">[RFC2518], Section 16</a>. |
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Reschke Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc4709">RFC 4709</a> Mounting WebDAV Servers October 2006</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span> |
| 282 |
|
| 283 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. MIME Type Registration</span> |
| 284 |
|
| 285 |
Type name: |
| 286 |
|
| 287 |
application |
| 288 |
|
| 289 |
Subtype name: |
| 290 |
|
| 291 |
davmount+xml |
| 292 |
|
| 293 |
Required parameters: |
| 294 |
|
| 295 |
none |
| 296 |
|
| 297 |
Optional parameters: |
| 298 |
|
| 299 |
"charset": This parameter has identical semantics to the charset |
| 300 |
parameter of the "application/xml" media type as specified in |
| 301 |
[<a href="./rfc3023" title=""XML Media Types"">RFC3023</a>]. |
| 302 |
|
| 303 |
Encoding considerations: |
| 304 |
|
| 305 |
Identical to those of "application/xml" as described in <a href="./rfc3023#section-3.2">[RFC3023], |
| 306 |
Section 3.2</a>. |
| 307 |
|
| 308 |
Security considerations: |
| 309 |
|
| 310 |
As defined in this specification. In addition, as this media type |
| 311 |
uses the "+xml" convention, it shares the same security |
| 312 |
considerations as described in <a href="./rfc3023#section-10">[RFC3023], Section 10</a>. |
| 313 |
|
| 314 |
Interoperability considerations: |
| 315 |
|
| 316 |
There are no known interoperability issues. |
| 317 |
|
| 318 |
Published specification: |
| 319 |
|
| 320 |
This specification. |
| 321 |
|
| 322 |
Applications that use this media type: |
| 323 |
|
| 324 |
SAP Netweaver Knowledge Management, Xythos Drive. |
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Reschke Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc4709">RFC 4709</a> Mounting WebDAV Servers October 2006</span> |
| 335 |
|
| 336 |
|
| 337 |
Additional information: |
| 338 |
|
| 339 |
Magic number(s): |
| 340 |
|
| 341 |
As specified for "application/xml" in <a href="./rfc3023#section-3.2">[RFC3023], Section 3.2</a>. |
| 342 |
|
| 343 |
File extension(s): |
| 344 |
|
| 345 |
.davmount |
| 346 |
|
| 347 |
Fragment identifiers: |
| 348 |
|
| 349 |
As specified for "application/xml" in <a href="./rfc3023#section-5">[RFC3023], Section 5</a>. |
| 350 |
|
| 351 |
Base URI: |
| 352 |
|
| 353 |
As specified in <a href="./rfc3023#section-6">[RFC3023], Section 6</a>. |
| 354 |
|
| 355 |
Macintosh file type code(s): |
| 356 |
|
| 357 |
TEXT |
| 358 |
|
| 359 |
Person & email address to contact for further information: |
| 360 |
|
| 361 |
Julian Reschke <[email protected]> |
| 362 |
|
| 363 |
Intended usage: |
| 364 |
|
| 365 |
COMMON |
| 366 |
|
| 367 |
Restrictions on usage: |
| 368 |
|
| 369 |
None. |
| 370 |
|
| 371 |
Author: |
| 372 |
|
| 373 |
Julian Reschke |
| 374 |
|
| 375 |
Change controller: |
| 376 |
|
| 377 |
IESG |
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Reschke Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc4709">RFC 4709</a> Mounting WebDAV Servers October 2006</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span> |
| 394 |
|
| 395 |
All security considerations connected to HTTP/WebDAV and XML apply |
| 396 |
for this specification as well, namely, [<a href="./rfc2518" title=""HTTP Extensions for Distributed Authoring -- WEBDAV"">RFC2518</a>] (<a href="#section-17">Section 17</a>) and |
| 397 |
[<a href="./rfc3470" title=""Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols"">RFC3470</a>] (<a href="#section-7">Section 7</a>). |
| 398 |
|
| 399 |
In addition, client implementers must be careful when implementing |
| 400 |
the <dm:open> element (see <a href="#section-3.3">Section 3.3</a>). It MUST NOT be used to |
| 401 |
initiate any action beyond displaying the contents of a WebDAV |
| 402 |
collection (supporting "opening" documents could be abused to trick a |
| 403 |
user into letting the operating system's shell execute arbitrary |
| 404 |
content, possibly running it as an executable program). |
| 405 |
|
| 406 |
The OPTIONAL <dm:username> element defined in <a href="#section-3.4">Section 3.4</a> allows the |
| 407 |
inclusion of user names into mount documents. However in some cases, |
| 408 |
user name information is considered to be security sensitive. Should |
| 409 |
this be the case, parties generating mount documents are advised to |
| 410 |
either not to include user names, or to use access control to |
| 411 |
restrict access to the information as desired. |
| 412 |
|
| 413 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span> |
| 414 |
|
| 415 |
This document has benefited from thoughtful discussion by Emile |
| 416 |
Baizel, Spencer Dawkins, Lisa Dusseault, Stefan Eissing, Joe |
| 417 |
Gregorio, Michal Gregr, Russ Housley, Jim Luther, Jaroslav Mazanec, |
| 418 |
and Jim Whitehead. |
| 419 |
|
| 420 |
|
| 421 |
|
| 422 |
|
| 423 |
|
| 424 |
|
| 425 |
|
| 426 |
|
| 427 |
|
| 428 |
|
| 429 |
|
| 430 |
|
| 431 |
|
| 432 |
|
| 433 |
|
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Reschke Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc4709">RFC 4709</a> Mounting WebDAV Servers October 2006</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span> |
| 450 |
|
| 451 |
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span> |
| 452 |
|
| 453 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 454 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 455 |
|
| 456 |
[<a id="ref-RFC2518">RFC2518</a>] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D. |
| 457 |
Jensen, "HTTP Extensions for Distributed Authoring -- |
| 458 |
WEBDAV", <a href="./rfc2518">RFC 2518</a>, February 1999. |
| 459 |
|
| 460 |
[<a id="ref-RFC2616">RFC2616</a>] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., |
| 461 |
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext |
| 462 |
Transfer Protocol -- HTTP/1.1", <a href="./rfc2616">RFC 2616</a>, June 1999. |
| 463 |
|
| 464 |
[<a id="ref-RFC3023">RFC3023</a>] Murata, M., St.Laurent, S., and D. Kohn, "XML Media |
| 465 |
Types", <a href="./rfc3023">RFC 3023</a>, January 2001. |
| 466 |
|
| 467 |
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform |
| 468 |
Resource Identifier (URI): Generic Syntax", STD 66, |
| 469 |
<a href="./rfc3986">RFC 3986</a>, January 2005. |
| 470 |
|
| 471 |
[<a id="ref-XML">XML</a>] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and |
| 472 |
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fourth |
| 473 |
Edition)", W3C REC-xml-20060816, August 2006, |
| 474 |
<<a href="http://www.w3.org/TR/2006/REC-xml-20060816">http://www.w3.org/TR/2006/REC-xml-20060816</a>>. |
| 475 |
|
| 476 |
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span> |
| 477 |
|
| 478 |
[<a id="ref-RFC3470">RFC3470</a>] Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines for |
| 479 |
the Use of Extensible Markup Language (XML) within IETF |
| 480 |
Protocols", <a href="./rfc3470">RFC 3470</a>, <a href="https://www.rfc-editor.org/bcp/bcp70">BCP 70</a>, January 2003. |
| 481 |
|
| 482 |
[<a id="ref-WEBARCH">WEBARCH</a>] Walsh, N. and I. Jacobs, "Architecture of the World Wide |
| 483 |
Web, Volume One", W3C REC-webarch-20041215, December 2004, |
| 484 |
<<a href="http://www.w3.org/TR/2004/REC-webarch-20041215/">http://www.w3.org/TR/2004/REC-webarch-20041215/</a>>. |
| 485 |
|
| 486 |
|
| 487 |
|
| 488 |
|
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Reschke Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc4709">RFC 4709</a> Mounting WebDAV Servers October 2006</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Alternative Approaches</span> |
| 506 |
|
| 507 |
<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. ...Through HTML/CSS Extensions</span> |
| 508 |
|
| 509 |
Microsoft Internet Explorer implements a Cascading Style Sheet (CSS) |
| 510 |
extension that allows switching to its own WebDAV client |
| 511 |
("Webfolder", see <<a href="http://msdn.microsoft.com/workshop/author/behaviors/reference/behaviors/anchor.asp">http://msdn.microsoft.com/workshop/author/</a> |
| 512 |
<a href="http://msdn.microsoft.com/workshop/author/behaviors/reference/behaviors/anchor.asp">behaviors/reference/behaviors/anchor.asp</a>>). However, at the time of |
| 513 |
this writing, this extension was not implemented by any other user |
| 514 |
agent. |
| 515 |
|
| 516 |
<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>. ...Through Custom URI Schemes</span> |
| 517 |
|
| 518 |
The "kio" library of the "K Desktop Enviroment" |
| 519 |
(<<a href="http://www.kde.org/">http://www.kde.org/</a>>) uses the URI scheme "webdav" to dispatch to |
| 520 |
the system's WebDAV client. This URI scheme is not registered, nor |
| 521 |
is it supported on other platforms. Furthermore, the W3C's |
| 522 |
"Architecture of the World Wide Web, Volume One" explicitly advises |
| 523 |
against defining new schemes when existing schemes can be used: |
| 524 |
|
| 525 |
A specification SHOULD reuse an existing URI scheme (rather than |
| 526 |
create a new one) when it provides the desired properties of |
| 527 |
identifiers and their relation to resources. |
| 528 |
|
| 529 |
(See [<a href="#ref-WEBARCH" title=""Architecture of the World Wide Web, Volume One"">WEBARCH</a>], Section 2.4.) |
| 530 |
|
| 531 |
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Implementations</span> |
| 532 |
|
| 533 |
<span class="h3"><a class="selflink" id="appendix-B.1" href="#appendix-B.1">B.1</a>. Example Implementation for Webfolder Client</span> |
| 534 |
|
| 535 |
The figure below shows a sample implementation of a dispatcher for |
| 536 |
the application/davmount+xml datatype, suited for Win32 systems and |
| 537 |
the Microsoft "Webfolder" client. |
| 538 |
|
| 539 |
// sample implementation of application/davmount+xml |
| 540 |
// dispatcher for Windows Webfolder client |
| 541 |
// |
| 542 |
// to install/uninstall: |
| 543 |
// wscript davmount.js |
| 544 |
// |
| 545 |
// to open the webfolder: |
| 546 |
// wscript davmount.js filename |
| 547 |
// (where filename refers to an XML document with MIME type |
| 548 |
// application/davmount+xml) |
| 549 |
|
| 550 |
var EXTENSION = ".davmount"; |
| 551 |
var MIMETYPE = "application/davmount+xml"; |
| 552 |
var REGKW = "WebDAV.mount"; |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Reschke Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc4709">RFC 4709</a> Mounting WebDAV Servers October 2006</span> |
| 559 |
|
| 560 |
|
| 561 |
var NS = "xmlns:m='http://purl.org/NET/webdav/mount"; |
| 562 |
|
| 563 |
// remove keys/entries from the registry |
| 564 |
|
| 565 |
function regdel(shell, key) { |
| 566 |
try { |
| 567 |
var x = shell.RegRead(key); |
| 568 |
try { |
| 569 |
shell.RegDelete(key); |
| 570 |
} |
| 571 |
catch(e) { |
| 572 |
WScript.Echo("Error removing key " + key + ": " + e); |
| 573 |
} |
| 574 |
} |
| 575 |
catch(e) { |
| 576 |
// entry not present |
| 577 |
} |
| 578 |
} |
| 579 |
|
| 580 |
|
| 581 |
// methods for registering/unregistering the handler |
| 582 |
|
| 583 |
function install() { |
| 584 |
|
| 585 |
var WshShell = new ActiveXObject("WScript.Shell"); |
| 586 |
if (WshShell == null) { |
| 587 |
WScript.Echo("Couldn't instantiate WScript.Shell object"); |
| 588 |
return 2; |
| 589 |
} |
| 590 |
|
| 591 |
var fso = new ActiveXObject("Scripting.FileSystemObject"); |
| 592 |
|
| 593 |
var RegExt = "HKCR\\" + EXTENSION + "\\"; |
| 594 |
var RegMimeType = "HKCR\\MIME\\DataBase\\Content Type\\" |
| 595 |
+ MIMETYPE + "\\"; |
| 596 |
var RegKw = "HKCR\\" + REGKW + "\\"; |
| 597 |
|
| 598 |
var extension = null; |
| 599 |
try { |
| 600 |
extension = WshShell.RegRead(RegMimeType + "Extension"); |
| 601 |
} |
| 602 |
catch (e) { |
| 603 |
} |
| 604 |
|
| 605 |
if (extension == null) { |
| 606 |
var but = WshShell.popup("Install the dispatcher for mime type " |
| 607 |
+ MIMETYPE + "?", 0, MIMETYPE + " installation", 4); |
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Reschke Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc4709">RFC 4709</a> Mounting WebDAV Servers October 2006</span> |
| 615 |
|
| 616 |
|
| 617 |
if (but == 6) { |
| 618 |
try { |
| 619 |
WshShell.RegWrite(RegExt, REGKW); |
| 620 |
WshShell.RegWrite(RegExt + "Content Type", MIMETYPE); |
| 621 |
WshShell.RegWrite(RegMimeType + "Extension", EXTENSION); |
| 622 |
WshShell.RegWrite(RegKw, "WebDAV Mount Request"); |
| 623 |
WshShell.RegWrite(RegKw + "DefaultIcon\\", |
| 624 |
"shell32.dll,103"); |
| 625 |
var path = fso.getAbsolutePathName("davmount.js"); |
| 626 |
WshShell.RegWrite(RegKw + "shell\\open\\command\\", |
| 627 |
"%SystemRoot%\\system32\\wscript.exe /nologo \"" |
| 628 |
+ path + "\" \"%1\"", "REG_EXPAND_SZ"); |
| 629 |
} |
| 630 |
catch (e) { |
| 631 |
WScript.Echo("Error writing to registry"); |
| 632 |
return 1; |
| 633 |
} |
| 634 |
|
| 635 |
return 0; |
| 636 |
} |
| 637 |
else { |
| 638 |
return 1; |
| 639 |
} |
| 640 |
} |
| 641 |
else { |
| 642 |
var but = WshShell.popup("Remove the dispatcher for mime type " |
| 643 |
+ MIMETYPE + "?", 0, MIMETYPE + " installation", 4); |
| 644 |
|
| 645 |
if (but == 6) { |
| 646 |
regdel(WshShell, RegExt + "Content Type"); |
| 647 |
regdel(WshShell, RegExt); |
| 648 |
regdel(WshShell, RegKw + "shell\\open\\command\\"); |
| 649 |
regdel(WshShell, RegKw + "DefaultIcon\\"); |
| 650 |
regdel(WshShell, RegKw); |
| 651 |
regdel(WshShell, RegMimeType + "Extension"); |
| 652 |
regdel(WshShell, RegMimeType); |
| 653 |
return 0; |
| 654 |
} |
| 655 |
else { |
| 656 |
return 1; |
| 657 |
} |
| 658 |
} |
| 659 |
} |
| 660 |
|
| 661 |
|
| 662 |
if (WScript.Arguments.length == 0) { |
| 663 |
// install/uninstall |
| 664 |
WScript.Quit(install()); |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Reschke Informational [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc4709">RFC 4709</a> Mounting WebDAV Servers October 2006</span> |
| 671 |
|
| 672 |
|
| 673 |
} |
| 674 |
else { |
| 675 |
// try to invoke Webfolder |
| 676 |
|
| 677 |
var inp = new ActiveXObject("MSXML2.DOMDocument"); |
| 678 |
var furi = encodeURI(WScript.Arguments(0)); |
| 679 |
if (! inp.load(furi)) { |
| 680 |
WScript.Echo("Can't read from '" |
| 681 |
+ WScript.Arguments(0) + "'!"); |
| 682 |
WScript.Quit(2); |
| 683 |
} |
| 684 |
|
| 685 |
inp.setProperty("SelectionLanguage", "XPath"); |
| 686 |
inp.setProperty("SelectionNamespaces", |
| 687 |
"xmlns:m='http://purl.org/NET/webdav/mount'"); |
| 688 |
|
| 689 |
var n1 = inp.selectSingleNode("/m:mount/m:url"); |
| 690 |
var n2 = inp.selectSingleNode("/m:mount/m:open"); |
| 691 |
|
| 692 |
if (n1 == null) { |
| 693 |
WScript.Echo("<url> element missing."); |
| 694 |
WScript.Quit(2); |
| 695 |
} |
| 696 |
|
| 697 |
var ie = new ActiveXObject("InternetExplorer.Application"); |
| 698 |
|
| 699 |
ie.Navigate("about:blank"); |
| 700 |
var doc = ie.Document; |
| 701 |
|
| 702 |
var folder = doc.createElement("span"); |
| 703 |
folder.addBehavior("#default#httpFolder"); |
| 704 |
|
| 705 |
var result = folder.navigate(n1.text + |
| 706 |
(n2 == null ? "" : n2.text)); |
| 707 |
|
| 708 |
// close the window again when there was no <open> element |
| 709 |
if (n2 == null) ie.Quit(); |
| 710 |
|
| 711 |
if (result != "OK") { |
| 712 |
if (result == "PROTOCOL_NOT_SUPPORTED") { |
| 713 |
WScript.Echo("This site doesn't seem to support WebDAV."); |
| 714 |
WScript.Quit(1); |
| 715 |
} |
| 716 |
else { |
| 717 |
WScript.Echo("Unexpected status: " + result); |
| 718 |
WScript.Quit(2); |
| 719 |
} |
| 720 |
} |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Reschke Informational [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc4709">RFC 4709</a> Mounting WebDAV Servers October 2006</span> |
| 727 |
|
| 728 |
|
| 729 |
} |
| 730 |
|
| 731 |
<span class="h3"><a class="selflink" id="appendix-B.2" href="#appendix-B.2">B.2</a>. Xythos</span> |
| 732 |
|
| 733 |
The "Xythos Drive" WebDAV client for WebDAV supports this |
| 734 |
specification starting with version 4.4. |
| 735 |
|
| 736 |
Author's Address |
| 737 |
|
| 738 |
Julian F. Reschke |
| 739 |
greenbytes GmbH |
| 740 |
Hafenweg 16 |
| 741 |
Muenster, NW 48155 |
| 742 |
Germany |
| 743 |
|
| 744 |
Phone: +49 251 2807760 |
| 745 |
Fax: +49 251 2807761 |
| 746 |
EMail: [email protected] |
| 747 |
URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a> |
| 748 |
|
| 749 |
|
| 750 |
|
| 751 |
|
| 752 |
|
| 753 |
|
| 754 |
|
| 755 |
|
| 756 |
|
| 757 |
|
| 758 |
|
| 759 |
|
| 760 |
|
| 761 |
|
| 762 |
|
| 763 |
|
| 764 |
|
| 765 |
|
| 766 |
|
| 767 |
|
| 768 |
|
| 769 |
|
| 770 |
|
| 771 |
|
| 772 |
|
| 773 |
|
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Reschke Informational [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc4709">RFC 4709</a> Mounting WebDAV Servers October 2006</span> |
| 783 |
|
| 784 |
|
| 785 |
Full Copyright Statement |
| 786 |
|
| 787 |
Copyright (C) The Internet Society (2006). |
| 788 |
|
| 789 |
This document is subject to the rights, licenses and restrictions |
| 790 |
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors |
| 791 |
retain all their rights. |
| 792 |
|
| 793 |
This document and the information contained herein are provided on an |
| 794 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
| 795 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET |
| 796 |
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, |
| 797 |
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE |
| 798 |
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 799 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 800 |
|
| 801 |
Intellectual Property |
| 802 |
|
| 803 |
The IETF takes no position regarding the validity or scope of any |
| 804 |
Intellectual Property Rights or other rights that might be claimed to |
| 805 |
pertain to the implementation or use of the technology described in |
| 806 |
this document or the extent to which any license under such rights |
| 807 |
might or might not be available; nor does it represent that it has |
| 808 |
made any independent effort to identify any such rights. Information |
| 809 |
on the procedures with respect to rights in RFC documents can be |
| 810 |
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>. |
| 811 |
|
| 812 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 813 |
assurances of licenses to be made available, or the result of an |
| 814 |
attempt made to obtain a general license or permission for the use of |
| 815 |
such proprietary rights by implementers or users of this |
| 816 |
specification can be obtained from the IETF on-line IPR repository at |
| 817 |
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 818 |
|
| 819 |
The IETF invites any interested party to bring to its attention any |
| 820 |
copyrights, patents or patent applications, or other proprietary |
| 821 |
rights that may cover technology that may be required to implement |
| 822 |
this standard. Please address the information to the IETF at |
| 823 |
[email protected]. |
| 824 |
|
| 825 |
Acknowledgement |
| 826 |
|
| 827 |
Funding for the RFC Editor function is provided by the IETF |
| 828 |
Administrative Support Activity (IASA). |
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
Reschke Informational [Page 15] |
| 837 |
</pre> |