Debian Codegraph @

doc/html/HTTP-DAV.html

raw
1 <?xml version="1.0" ?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml">
4 <head>
5 <title>HTTP::DAV - A WebDAV client library for Perl5</title>
6 <link rel="stylesheet" href="perldav_plain.css" type="text/css" />
7 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
8 <link rev="made" href="mailto:root@localhost" />
9 </head>
10
11 <body>
12
13
14
15 <h1 id="NAME">NAME</h1>
16
17 <p>HTTP::DAV - A WebDAV client library for Perl5</p>
18
19 <h1 id="SYNOPSIS">SYNOPSIS</h1>
20
21 <pre><code> # DAV script that connects to a webserver, safely makes
22 # a new directory and uploads all html files in
23 # the /tmp directory.
24
25 use HTTP::DAV;
26
27 $d = HTTP::DAV-&gt;new();
28 $url = &quot;http://host.org:8080/dav/&quot;;
29
30 $d-&gt;credentials(
31 -user =&gt; &quot;pcollins&quot;,
32 -pass =&gt; &quot;mypass&quot;,
33 -url =&gt; $url,
34 -realm =&gt; &quot;DAV Realm&quot;
35 );
36
37 $d-&gt;open( -url =&gt; $url )
38 or die(&quot;Couldn&#39;t open $url: &quot; .$d-&gt;message . &quot;\n&quot;);
39
40 # Make a null lock on newdir
41 $d-&gt;lock( -url =&gt; &quot;$url/newdir&quot;, -timeout =&gt; &quot;10m&quot; )
42 or die &quot;Won&#39;t put unless I can lock for 10 minutes\n&quot;;
43
44 # Make a new directory
45 $d-&gt;mkcol( -url =&gt; &quot;$url/newdir&quot; )
46 or die &quot;Couldn&#39;t make newdir at $url\n&quot;;
47
48 # Upload multiple files to newdir.
49 if ( $d-&gt;put( -local =&gt; &quot;/tmp/*.html&quot;, -url =&gt; $url ) ) {
50 print &quot;successfully uploaded multiple files to $url\n&quot;;
51 } else {
52 print &quot;put failed: &quot; . $d-&gt;message . &quot;\n&quot;;
53 }
54
55 $d-&gt;unlock( -url =&gt; $url );</code></pre>
56
57 <h1 id="DESCRIPTION">DESCRIPTION</h1>
58
59 <p>HTTP::DAV is a Perl API for interacting with and modifying content on webservers using the WebDAV protocol. Now you can LOCK, DELETE and PUT files and much more on a DAV-enabled webserver.</p>
60
61 <p>HTTP::DAV is part of the PerlDAV project hosted at http://www.webdav.org/perldav/ and has the following features:</p>
62
63 <ul>
64
65 <li><p>Full RFC2518 method support. OPTIONS, TRACE, GET, HEAD, DELETE, PUT, COPY, MOVE, PROPFIND, PROPPATCH, LOCK, UNLOCK.</p>
66
67 </li>
68 <li><p>A fully object-oriented API.</p>
69
70 </li>
71 <li><p>Recursive GET and PUT for site backups and other scripted transfers.</p>
72
73 </li>
74 <li><p>Transparent lock handling when performing LOCK/COPY/UNLOCK sequences.</p>
75
76 </li>
77 <li><p>http and https support (https requires the Crypt::SSLeay library). See INSTALLATION.</p>
78
79 </li>
80 <li><p>Basic AND Digest authentication support (Digest auth requires the MD5 library). See INSTALLATION.</p>
81
82 </li>
83 <li><p><code>dave</code>, a fully-functional ftp-style interface written on top of the HTTP::DAV API and bundled by default with the HTTP::DAV library. (If you&#39;ve already installed HTTP::DAV, then dave will also have been installed (probably into /usr/local/bin). You can see it&#39;s man page by typing &quot;perldoc dave&quot; or going to http://www.webdav.org/perldav/dave/.</p>
84
85 </li>
86 <li><p>It is built on top of the popular LWP (Library for WWW access in Perl). This means that HTTP::DAV inherits proxy support, redirect handling, basic (and digest) authorization and many other HTTP operations. See <code>LWP</code> for more information.</p>
87
88 </li>
89 <li><p>Popular server support. HTTP::DAV has been tested against the following servers: mod_dav, IIS5, Xythos webfile server and mydocsonline. The library is growing an impressive interoperability suite which also serves as useful &quot;sample scripts&quot;. See &quot;make test&quot; and t/*.</p>
90
91 </li>
92 </ul>
93
94 <p><code>HTTP::DAV</code> essentially has two API&#39;s, one which is accessed through this module directly (HTTP::DAV) and is a simple abstraction to the rest of the HTTP::DAV::* Classes. The other interface consists of the HTTP::DAV::* classes which if required allow you to get &quot;down and dirty&quot; with your DAV and HTTP interactions.</p>
95
96 <p>The methods provided in <code>HTTP::DAV</code> should do most of what you want. If, however, you need more control over the client&#39;s operations or need more info about the server&#39;s responses then you will need to understand the rest of the HTTP::DAV::* interfaces. A good place to start is with the <code>HTTP::DAV::Resource</code> and <code>HTTP::DAV::Response</code> documentation.</p>
97
98 <h1 id="METHODS">METHODS</h1>
99
100 <h2 id="METHOD-CALLING:-Named-vs-Unnamed-parameters">METHOD CALLING: Named vs Unnamed parameters</h2>
101
102 <p>You can pass parameters to <code>HTTP::DAV</code> methods in one of two ways: named or unnamed.</p>
103
104 <p>Named parameters provides for a simpler/easier to use interface. A named interface affords more readability and allows the developer to ignore a specific order on the parameters. (named parameters are also case insensitive)</p>
105
106 <p>Each argument name is preceded by a dash. Neither case nor order matters in the argument list. -url, -Url, and -URL are all acceptable. In fact, only the first argument needs to begin with a dash. If a dash is present in the first argument, <code>HTTP::DAV</code> assumes dashes for the subsequent ones.</p>
107
108 <p>Each method can also be called with unnamed parameters which often makes sense for methods with only one parameter. But the developer will need to ensure that the parameters are passed in the correct order (as listed in the docs).</p>
109
110 <pre><code>Doc: method( -url=&gt;$url, [-depth=&gt;$depth] )
111 Named: $d-&gt;method( -url=&gt;$url, -depth=&gt;$d ); # VALID
112 Named: $d-&gt;method( -Depth=&gt;$d, -Url=&gt;$url ); # VALID
113 Named: $d-&gt;method( Depth=&gt;$d, Url=&gt;$url ); # INVALID (needs -)
114 Named: $d-&gt;method( -Arg2=&gt;$val2 ); # INVALID, ARG1 is not optional
115 Unnamed: $d-&gt;method( $val1 ); # VALID
116 Unnamed: $d-&gt;method( $val2,$val1 ); # INVALID, ARG1 must come first.</code></pre>
117
118 <p>IMPORTANT POINT!!!! If you specify a named parameter first but then forget for the second and third parameters, you WILL get weird things happen. E.g. this is bad:</p>
119
120 <pre><code>$d-&gt;method( -url=&gt;$url, $arg2, $arg3 ); # BAD BAD BAD</code></pre>
121
122 <h2 id="THINGS-YOU-NEED-TO-KNOW">THINGS YOU NEED TO KNOW</h2>
123
124 <p>In all of the methods specified in <a href="#PUBLIC-METHODS">&quot;PUBLIC METHODS&quot;</a> there are some common concepts you&#39;ll need to understand:</p>
125
126 <ul>
127
128 <li><p>URLs represent an absolute or relative URI.</p>
129
130 <pre><code>-url=&gt;&quot;host.org/dav_dir/&quot; # Absolute
131 -url=&gt;&quot;/dav_dir/&quot; # Relative
132 -url=&gt;&quot;file.txt&quot; # Relative</code></pre>
133
134 <p>You can only use a relative URL if you have already &quot;open&quot;ed an absolute URL.</p>
135
136 <p>The HTTP::DAV module now consistently uses the named parameter: URL. The lower-level HTTP::DAV::Resource interface inconsistently interchanges URL and URI. I&#39;m working to resolve this, in the meantime, you&#39;ll just need to remember to use the right one by checking the documentation if you need to mix up your use of both interfaces.</p>
137
138 </li>
139 <li><p>GLOBS</p>
140
141 <p>Some methods accept wildcards in the URL. A wildcard can be used to indicate that the command should perform the command on all Resources that match the wildcard. These wildcards are called GLOBS.</p>
142
143 <p>The glob may contain the characters &quot;*&quot;, &quot;?&quot; and the set operator &quot;[...]&quot; where ... contains multiple characters ([1t2]) or a range such ([1-5]). For the curious, the glob is converted to a regex and then matched: &quot;*&quot; to &quot;.*&quot;, &quot;?&quot; to &quot;.&quot;, and the [] is left untouched.</p>
144
145 <p>It is important to note that globs only operate at the leaf-level. For instance &quot;/my_dir/*/file.txt&quot; is not a valid glob.</p>
146
147 <p>If a glob matches no URL&#39;s the command will fail (which normally means returns 0).</p>
148
149 <p>Globs are useful in conjunction with <a>CALLBACKS</a> to provide feedback as each operation completes.</p>
150
151 <p>See the documentation for each method to determine whether it supports globbing.</p>
152
153 <p>Globs are useful for interactive style applications (see the source code for <code>dave</code> as an example).</p>
154
155 <p>Example globs:</p>
156
157 <pre><code>$dav1-&gt;delete(-url=&gt;&quot;/my_dir/file[1-3]&quot;); # Matches file1, file2, file3
158 $dav1-&gt;delete(-url=&gt;&quot;/my_dir/file[1-3]*.txt&quot;);# Matches file1*.txt,file2*.txt,file3*.txt
159 $dav1-&gt;delete(-url=&gt;&quot;/my_dir/*/file.txt&quot;); # Invalid. Can only match at leaf-level</code></pre>
160
161 </li>
162 <li><p>CALLBACKS</p>
163
164 <p>Callbacks are used by some methods (primarily get and put) to give the caller some insight as to how the operation is progressing. A callback allows you to define a subroutine as defined below and pass a reference (\&amp;ref) to the method.</p>
165
166 <p>The rationale behind the callback is that a recursive get/put or an operation against many files (using a <code>glob</code>) can actually take a long time to complete.</p>
167
168 <p>Example callback:</p>
169
170 <pre><code>$d-&gt;get( -url=&gt;$url, -to=&gt;$to, -callback=&gt;\&amp;mycallback );</code></pre>
171
172 <p>Your callback function MUST accept arguments as follows: sub cat_callback { my($status,$mesg,$url,$so_far,$length,$data) = @_; ... }</p>
173
174 <p>The <code>status</code> argument specifies whether the operation has succeeded (1), failed (0), or is in progress (-1).</p>
175
176 <p>The <code>mesg</code> argument is a status message. The status message could contain any string and often contains useful error messages or success messages.</p>
177
178 <p>The <code>url</code> the remote URL.</p>
179
180 <p>The <code>so_far</code>, <code>length</code> - these parameters indicate how many bytes have been downloaded and how many we should expect. This is useful for doing &quot;56% to go&quot; style-gauges.</p>
181
182 <p>The <code>data</code> parameter - is the actual data transferred. The <code>cat</code> command uses this to print the data to the screen. This value will be empty for <code>put</code>.</p>
183
184 <p>See the source code of <code>dave</code> for a useful sample of how to setup a callback.</p>
185
186 <p>Note that these arguments are NOT named parameters.</p>
187
188 <p>All error messages set during a &quot;multi-operation&quot; request (for instance a recursive get/put) are also retrievable via the <code>errors()</code> function once the operation has completed. See <code>ERROR HANDLING</code> for more information.</p>
189
190 </li>
191 </ul>
192
193 <h2 id="PUBLIC-METHODS">PUBLIC METHODS</h2>
194
195 <dl>
196
197 <dt id="new-USERAGENT"><b>new(USERAGENT)</b></dt>
198 <dd>
199
200 </dd>
201 <dt id="new-USERAGENT-HEADERS"><b>new(USERAGENT, HEADERS)</b></dt>
202 <dd>
203
204 <p>Creates a new <code>HTTP::DAV</code> client</p>
205
206 <pre><code>$d = HTTP::DAV-&gt;new();</code></pre>
207
208 <p>The <code>-useragent</code> parameter allows you to pass your own <b>user agent object</b> and expects an <code>HTTP::DAV::UserAgent</code> object. See the <code>dave</code> program for an advanced example of a custom UserAgent that interactively prompts the user for their username and password.</p>
209
210 <p>The <code>-headers</code> parameter allows you to specify a list of headers to be sent along with all requests. This can be either a hashref like:</p>
211
212 <pre><code>{ &quot;X-My-Header&quot; =&gt; &quot;value&quot;, ... }</code></pre>
213
214 <p>or a <a>HTTP::Headers</a> object.</p>
215
216 </dd>
217 <dt id="credentials-USER-PASS-URL-REALM"><b>credentials(USER,PASS,[URL],[REALM])</b></dt>
218 <dd>
219
220 <p>sets authorization credentials for a <code>URL</code> and/or <code>REALM</code>.</p>
221
222 <p>When the client hits a protected resource it will check these credentials to see if either the <code>URL</code> or <code>REALM</code> match the authorization response.</p>
223
224 <p>Either <code>URL</code> or <code>REALM</code> must be provided.</p>
225
226 <p>returns no value</p>
227
228 <p>Example:</p>
229
230 <pre><code>$d-&gt;credentials( -url=&gt;&#39;myhost.org:8080/test/&#39;,
231 -user=&gt;&#39;pcollins&#39;,
232 -pass=&gt;&#39;mypass&#39;);</code></pre>
233
234 </dd>
235 <dt id="DebugLevel-val"><b>DebugLevel($val)</b></dt>
236 <dd>
237
238 <p>sets the debug level to <code>$val</code>. 0=off 3=noisy.</p>
239
240 <p><code>$val</code> default is 0.</p>
241
242 <p>returns no value.</p>
243
244 <p>When the value is greater than 1, the <code>HTTP::DAV::Comms</code> module will log all of the client&lt;=&gt;server interactions into /tmp/perldav_debug.txt.</p>
245
246 </dd>
247 </dl>
248
249 <h2 id="DAV-OPERATIONS">DAV OPERATIONS</h2>
250
251 <p>For all of the following operations, URL can be absolute (http://host.org/dav/) or relative (../dir2/). The only operation that requires an absolute URL is open.</p>
252
253 <dl>
254
255 <dt id="copy-URL-DEST-OVERWRITE-DEPTH"><b>copy(URL,DEST,[OVERWRITE],[DEPTH])</b></dt>
256 <dd>
257
258 <p>copies one remote resource to another</p>
259
260 <dl>
261
262 <dt id="url"><code>-url</code></dt>
263 <dd>
264
265 <p>is the remote resource you&#39;d like to copy. Mandatory</p>
266
267 </dd>
268 <dt id="dest"><code>-dest</code></dt>
269 <dd>
270
271 <p>is the remote target for the copy command. Mandatory</p>
272
273 </dd>
274 <dt id="overwrite"><code>-overwrite</code></dt>
275 <dd>
276
277 <p>optionally indicates whether the server should fail if the target exists. Valid values are &quot;T&quot; and &quot;F&quot; (1 and 0 are synonymous). Default is T.</p>
278
279 </dd>
280 <dt id="depth"><code>-depth</code></dt>
281 <dd>
282
283 <p>optionally indicates whether the server should do a recursive copy or not. Valid values are 0 and (1 or &quot;infinity&quot;). Default is &quot;infinity&quot; (1).</p>
284
285 </dd>
286 </dl>
287
288 <p>The return value is always 1 or 0 indicating success or failure.</p>
289
290 <p>Requires a working resource to be set before being called. See <code>open</code>.</p>
291
292 <p>Note: if either <code>&#39;URL&#39;</code> or <code>&#39;DEST&#39;</code> are locked by this dav client, then the lock headers will be taken care of automatically. If the either of the two URL&#39;s are locked by someone else, the server should reject the request.</p>
293
294 <p><b>copy examples:</b></p>
295
296 <pre><code>$d-&gt;open(-url=&gt;&quot;host.org/dav_dir/&quot;);</code></pre>
297
298 <p>Recursively copy dir1/ to dir2/</p>
299
300 <pre><code>$d-&gt;copy(-url=&gt;&quot;dir1/&quot;, -dest=&gt;&quot;dir2/&quot;);</code></pre>
301
302 <p>Non-recursively and non-forcefully copy dir1/ to dir2/</p>
303
304 <pre><code>$d-&gt;copy(-url=&gt;&quot;dir1/&quot;, -dest=&gt;&quot;dir2/&quot;,-overwrite=&gt;0,-depth=&gt;0);</code></pre>
305
306 <p>Create a copy of dir1/file.txt as dir2/file.txt</p>
307
308 <pre><code>$d-&gt;cwd(-url=&gt;&quot;dir1/&quot;);
309 $d-&gt;copy(&quot;file.txt&quot;,&quot;../dir2&quot;);</code></pre>
310
311 <p>Create a copy of file.txt as dir2/new_file.txt</p>
312
313 <pre><code>$d-&gt;copy(&quot;file.txt&quot;,&quot;/dav_dir/dir2/new_file.txt&quot;)</code></pre>
314
315 </dd>
316 <dt id="cwd-URL"><b>cwd(URL)</b></dt>
317 <dd>
318
319 <p>changes the remote working directory.</p>
320
321 <p>This is synonymous to open except that the URL can be relative and may contain a <code>glob</code> (the first match in a glob will be used).</p>
322
323 <pre><code>$d-&gt;open(&quot;host.org/dav_dir/dir1/&quot;);
324 $d-&gt;cwd(&quot;../dir2&quot;);
325 $d-&gt;cwd(-url=&gt;&quot;../dir1&quot;);</code></pre>
326
327 <p>The return value is always 1 or 0 indicating success or failure.</p>
328
329 <p>Requires a working resource to be set before being called. See <code>open</code>.</p>
330
331 <p>You can not cwd to files, only collections (directories).</p>
332
333 </dd>
334 <dt id="delete-URL"><b>delete(URL)</b></dt>
335 <dd>
336
337 <p>deletes a remote resource.</p>
338
339 <pre><code>$d-&gt;open(&quot;host.org/dav_dir/&quot;);
340 $d-&gt;delete(&quot;index.html&quot;);
341 $d-&gt;delete(&quot;./dir1&quot;);
342 $d-&gt;delete(-url=&gt;&quot;/dav_dir/dir2/file*&quot;,-callback=&gt;\&amp;mycallback);</code></pre>
343
344 </dd>
345 <dt id="url1"><code>-url</code></dt>
346 <dd>
347
348 <p>is the remote resource(s) you&#39;d like to delete. It can be a file, directory or <code>glob</code>.</p>
349
350 </dd>
351 <dt id="callback-is-a-reference-to-a-callback-function-which-will-be-called-everytime-a-file-is-deleted.-This-is-mainly-useful-when-used-in-conjunction-with-GLOBS-deletes.-See-callbacks"><code>-callback</code> is a reference to a callback function which will be called everytime a file is deleted. This is mainly useful when used in conjunction with <a>GLOBS</a> deletes. See <a>callbacks</a></dt>
352 <dd>
353
354 <p>The return value is always 1 or 0 indicating success or failure.</p>
355
356 <p>Requires a working resource to be set before being called. See <code>open</code>.</p>
357
358 <p>This command will recursively delete directories. BE CAREFUL of uninitialised file variables in situation like this: $d-&gt;delete(&quot;$dir/$file&quot;). This will trash your $dir if $file is not set.</p>
359
360 </dd>
361 <dt id="get-URL-TO-CALLBACK"><b>get(URL,[TO],[CALLBACK])</b></dt>
362 <dd>
363
364 <p>downloads the file or directory at <code>URL</code> to the local location indicated by <code>TO</code>.</p>
365
366 <dl>
367
368 <dt id="url2"><code>-url</code></dt>
369 <dd>
370
371 <p>is the remote resource you&#39;d like to get. It can be a file or directory or a &quot;glob&quot;.</p>
372
373 </dd>
374 <dt id="to"><code>-to</code></dt>
375 <dd>
376
377 <p>is where you&#39;d like to put the remote resource. The -to parameter can be:</p>
378
379 <pre><code>- a B&lt;filename&gt; indicating where to save the contents.
380
381 - a B&lt;FileHandle reference&gt;.
382
383 - a reference to a B&lt;scalar object&gt; into which the contents will be saved.</code></pre>
384
385 <p>If the <code>-url</code> matches multiple files (via a glob or a directory download), then the <code>get</code> routine will return an error if you try to use a FileHandle reference or a scalar reference.</p>
386
387 </dd>
388 <dt id="callback"><code>-callback</code></dt>
389 <dd>
390
391 <p>is a reference to a callback function which will be called everytime a file is completed downloading. The idea of the callback function is that some recursive get&#39;s can take a very long time and the user may require some visual feedback. See <a>CALLBACKS</a> for an examples and how to use a callback.</p>
392
393 </dd>
394 </dl>
395
396 <p>The return value of get is always 1 or 0 indicating whether the entire get sequence was a success or if there was ANY failures. For instance, in a recursive get, if the server couldn&#39;t open 1 of the 10 remote files, for whatever reason, then the return value will be 0. This is so that you can have your script call the <code>errors()</code> routine to handle error conditions.</p>
397
398 <p>Previous versions of HTTP::DAV allowed the return value to be the file contents if no -to attribute was supplied. This functionality is deprecated.</p>
399
400 <p>Requires a working resource to be set before being called. See <code>open</code>.</p>
401
402 <p><b>get examples:</b></p>
403
404 <pre><code>$d-&gt;open(&quot;host.org/dav_dir/&quot;);</code></pre>
405
406 <p>Recursively get remote my_dir/ to .</p>
407
408 <pre><code>$d-&gt;get(&quot;my_dir/&quot;,&quot;.&quot;);</code></pre>
409
410 <p>Recursively get remote my_dir/ to /tmp/my_dir/ calling &amp;mycallback($success,$mesg) everytime a file operation is completed.</p>
411
412 <pre><code>$d-&gt;get(&quot;my_dir&quot;,&quot;/tmp&quot;,\&amp;mycallback);</code></pre>
413
414 <p>Get remote my_dir/index.html to /tmp/index.html</p>
415
416 <pre><code>$d-&gt;get(-url=&gt;&quot;/dav_dir/my_dir/index.html&quot;,-to=&gt;&quot;/tmp&quot;);</code></pre>
417
418 <p>Get remote index.html to /tmp/index1.html</p>
419
420 <pre><code>$d-&gt;get(&quot;index.html&quot;,&quot;/tmp/index1.html&quot;);</code></pre>
421
422 <p>Get remote index.html to a filehandle</p>
423
424 <pre><code>my $fh = new FileHandle;
425 $fh-&gt;open(&quot;&gt;/tmp/index1.html&quot;);
426 $d-&gt;get(&quot;index.html&quot;,\$fh);</code></pre>
427
428 <p>Get remote index.html as a scalar (into the string $file_contents):</p>
429
430 <pre><code>my $file_contents;
431 $d-&gt;get(&quot;index.html&quot;,\$file_contents);</code></pre>
432
433 <p>Get all of the files matching the globs file1* and file2*:</p>
434
435 <pre><code>$d-&gt;get(&quot;file[12]*&quot;,&quot;/tmp&quot;);</code></pre>
436
437 <p>Get all of the files matching the glob file?.html:</p>
438
439 <pre><code>$d-&gt;get(&quot;file?.html&quot;,&quot;/tmp&quot;); # downloads file1.html and file2.html but not file3.html or file1.txt</code></pre>
440
441 <p>Invalid glob:</p>
442
443 <pre><code>$d-&gt;get(&quot;/dav_dir/*/index.html&quot;,&quot;/tmp&quot;); # Can not glob like this.</code></pre>
444
445 </dd>
446 <dt id="lock-URL-OWNER-DEPTH-TIMEOUT-SCOPE-TYPE"><b>lock([URL],[OWNER],[DEPTH],[TIMEOUT],[SCOPE],[TYPE])</b></dt>
447 <dd>
448
449 <p>locks a resource. If URL is not specified, it will lock the current working resource (opened resource).</p>
450
451 <pre><code>$d-&gt;lock( -url =&gt; &quot;index.html&quot;,
452 -owner =&gt; &quot;Patrick Collins&quot;,
453 -depth =&gt; &quot;infinity&quot;,
454 -scope =&gt; &quot;exclusive&quot;,
455 -type =&gt; &quot;write&quot;,
456 -timeout =&gt; &quot;10h&quot; )</code></pre>
457
458 <p>See <code>HTTP::DAV::Resource</code> lock() for details of the above parameters.</p>
459
460 <p>The return value is always 1 or 0 indicating success or failure.</p>
461
462 <p>Requires a working resource to be set before being called. See <code>open</code>.</p>
463
464 <p>When you lock a resource, the lock is held against the current HTTP::DAV object. In fact, the locks are held in a <code>HTTP::DAV::ResourceList</code> object. You can operate against all of the locks that you have created as follows:</p>
465
466 <pre><code>## Print and unlock all locks that we own.
467 my $rl_obj = $d-&gt;get_lockedresourcelist();
468 foreach $resource ( $rl_obj-&gt;get_resources() ) {
469 @locks = $resource-&gt;get_locks(-owned=&gt;1);
470 foreach $lock ( @locks ) {
471 print $resource-&gt;get_uri . &quot;\n&quot;;
472 print $lock-&gt;as_string . &quot;\n&quot;;
473 }
474 ## Unlock them?
475 $resource-&gt;unlock;
476 }</code></pre>
477
478 <p>Typically, a simple $d-&gt;unlock($uri) will suffice.</p>
479
480 <p><b>lock example</b></p>
481
482 <pre><code>$d-&gt;lock($uri, -timeout=&gt;&quot;1d&quot;);
483 ...
484 $d-&gt;put(&quot;/tmp/index.html&quot;,$uri);
485 $d-&gt;unlock($uri);</code></pre>
486
487 </dd>
488 <dt id="mkcol-URL"><b>mkcol(URL)</b></dt>
489 <dd>
490
491 <p>make a remote collection (directory)</p>
492
493 <p>The return value is always 1 or 0 indicating success or failure.</p>
494
495 <p>Requires a working resource to be set before being called. See <code>open</code>.</p>
496
497 <pre><code>$d-&gt;open(&quot;host.org/dav_dir/&quot;);
498 $d-&gt;mkcol(&quot;new_dir&quot;); # Should succeed
499 $d-&gt;mkcol(&quot;/dav_dir/new_dir&quot;); # Should succeed
500 $d-&gt;mkcol(&quot;/dav_dir/new_dir/xxx/yyy&quot;); # Should fail</code></pre>
501
502 </dd>
503 <dt id="move-URL-DEST-OVERWRITE-DEPTH"><b>move(URL,DEST,[OVERWRITE],[DEPTH])</b></dt>
504 <dd>
505
506 <p>moves one remote resource to another</p>
507
508 <dl>
509
510 <dt id="url3"><code>-url</code></dt>
511 <dd>
512
513 <p>is the remote resource you&#39;d like to move. Mandatory</p>
514
515 </dd>
516 <dt id="dest1"><code>-dest</code></dt>
517 <dd>
518
519 <p>is the remote target for the move command. Mandatory</p>
520
521 </dd>
522 <dt id="overwrite1"><code>-overwrite</code></dt>
523 <dd>
524
525 <p>optionally indicates whether the server should fail if the target exists. Valid values are &quot;T&quot; and &quot;F&quot; (1 and 0 are synonymous). Default is T.</p>
526
527 </dd>
528 </dl>
529
530 <p>Requires a working resource to be set before being called. See <code>open</code>.</p>
531
532 <p>The return value is always 1 or 0 indicating success or failure.</p>
533
534 <p>Note: if either <code>&#39;URL&#39;</code> or <code>&#39;DEST&#39;</code> are locked by this dav client, then the lock headers will be taken care of automatically. If either of the two URL&#39;s are locked by someone else, the server should reject the request.</p>
535
536 <p><b>move examples:</b></p>
537
538 <pre><code>$d-&gt;open(-url=&gt;&quot;host.org/dav_dir/&quot;);</code></pre>
539
540 <p>move dir1/ to dir2/</p>
541
542 <pre><code>$d-&gt;move(-url=&gt;&quot;dir1/&quot;, -dest=&gt;&quot;dir2/&quot;);</code></pre>
543
544 <p>non-forcefully move dir1/ to dir2/</p>
545
546 <pre><code>$d-&gt;move(-url=&gt;&quot;dir1/&quot;, -dest=&gt;&quot;dir2/&quot;,-overwrite=&gt;0);</code></pre>
547
548 <p>Move dir1/file.txt to dir2/file.txt</p>
549
550 <pre><code>$d-&gt;cwd(-url=&gt;&quot;dir1/&quot;);
551 $d-&gt;move(&quot;file.txt&quot;,&quot;../dir2&quot;);</code></pre>
552
553 <p>move file.txt to dir2/new_file.txt</p>
554
555 <pre><code>$d-&gt;move(&quot;file.txt&quot;,&quot;/dav_dir/dir2/new_file.txt&quot;)</code></pre>
556
557 </dd>
558 <dt id="open-URL"><b>open(URL)</b></dt>
559 <dd>
560
561 <p>opens the directory (collection resource) at URL.</p>
562
563 <p>open will perform a propfind against URL. If the server does not understand the request then the open will fail.</p>
564
565 <p>Similarly, if the server indicates that the resource at URL is NOT a collection, the open command will fail.</p>
566
567 </dd>
568 <dt id="options-URL"><b>options([URL])</b></dt>
569 <dd>
570
571 <p>Performs an OPTIONS request against the URL or the working resource if URL is not supplied.</p>
572
573 <p>Requires a working resource to be set before being called. See <code>open</code>.</p>
574
575 <p>The return value is a string of comma separated OPTIONS that the server states are legal for URL or undef otherwise.</p>
576
577 <p>A fully compliant DAV server may offer as many methods as: OPTIONS, TRACE, GET, HEAD, DELETE, PUT, COPY, MOVE, PROPFIND, PROPPATCH, LOCK, UNLOCK</p>
578
579 <p>Note: IIS5 does not support PROPPATCH or LOCK on collections.</p>
580
581 <p>Example:</p>
582
583 <pre><code>$options = $d-&gt;options($url);
584 print $options . &quot;\n&quot;;
585 if ($options=~ /\bPROPPATCH\b/) {
586 print &quot;OK to proppatch\n&quot;;
587 }</code></pre>
588
589 <p>Or, put more simply:</p>
590
591 <pre><code>if ( $d-&gt;options($url) =~ /\bPROPPATCH\b/ ) {
592 print &quot;OK to proppatch\n&quot;;
593 }</code></pre>
594
595 </dd>
596 <dt id="propfind-URL-DEPTH"><b>propfind([URL],[DEPTH])</b></dt>
597 <dd>
598
599 <p>Perform a propfind against URL at DEPTH depth.</p>
600
601 <p><code>-depth</code> can be used to specify how deep the propfind goes. &quot;0&quot; is collection only. &quot;1&quot; is collection and it&#39;s immediate members (This is the default value). &quot;infinity&quot; is the entire directory tree. Note that most DAV compliant servers deny &quot;infinity&quot; depth propfinds for security reasons.</p>
602
603 <p>Requires a working resource to be set before being called. See <code>open</code>.</p>
604
605 <p>The return value is an <code>HTTP::DAV::Resource</code> object on success or 0 on failure.</p>
606
607 <p>The Resource object can be used for interrogating properties or performing other operations.</p>
608
609 <pre><code>## Print collection or content length
610 if ( $r=$d-&gt;propfind( -url=&gt;&quot;/my_dir&quot;, -depth=&gt;1) ) {
611 if ( $r-&gt;is_collection ) {
612 print &quot;Collection\n&quot;
613 print $r-&gt;get_resourcelist-&gt;as_string . &quot;\n&quot;
614 } else {
615 print $r-&gt;get_property(&quot;getcontentlength&quot;) .&quot;\n&quot;;
616 }
617 }</code></pre>
618
619 <p>Please note that although you may set a different namespace for a property of a resource during a set_prop, HTTP::DAV currently ignores all XML namespaces so you will get clashes if two properties have the same name but in different namespaces. Currently this is unavoidable but I&#39;m working on the solution.</p>
620
621 </dd>
622 <dt id="proppatch-URL-NAMESPACE-PROPNAME-PROPVALUE-ACTION-NSABBR"><b>proppatch([URL],[NAMESPACE],PROPNAME,PROPVALUE,ACTION,[NSABBR])</b></dt>
623 <dd>
624
625 <p>If <code>-action</code> equals &quot;set&quot; then we set a property named <code>-propname</code> to <code>-propvalue</code> in the namespace <code>-namespace</code> for <code>-url</code>.</p>
626
627 <p>If <code>-action</code> equals &quot;remove&quot; then we unset a property named <code>-propname</code> in the namespace <code>-namespace</code> for <code>-url</code>.</p>
628
629 <p>If no action is supplied then the default action is &quot;set&quot;.</p>
630
631 <p>The return value is an <code>HTTP::DAV::Resource</code> object on success or 0 on failure.</p>
632
633 <p>The Resource object can be used for interrogating properties or performing other operations.</p>
634
635 <p>To explicitly set a namespace in which to set the propname then you can use the <code>-namespace</code> and <code>-nsabbr</code> (namespace abbreviation) parameters. But you&#39;re welcome to play around with DAV namespaces.</p>
636
637 <p>Requires a working resource to be set before being called. See <code>open</code>.</p>
638
639 <p>It is recommended that you use <code>set_prop</code> and <code>unset_prop</code> instead of proppatch for readability.</p>
640
641 <p><code>set_prop</code> simply calls <code>proppatch(-action=</code>set)&gt; and <code>unset_prop</code> calls <code>proppatch(-action=</code>&quot;remove&quot;)&gt;</p>
642
643 <p>See <code>set_prop</code> and <code>unset_prop</code> for examples.</p>
644
645 </dd>
646 <dt id="put-LOCAL-URL-CALLBACK-HEADERS"><b>put(LOCAL,[URL],[CALLBACK],[HEADERS])</b></dt>
647 <dd>
648
649 <p>uploads the files or directories at <code>-local</code> to the remote destination at <code>-url</code>.</p>
650
651 <p><code>-local</code> points to a file, directory or series of files or directories (indicated by a glob).</p>
652
653 <p>If the filename contains any of the characters `*&#39;, `?&#39; or `[&#39; it is a candidate for filename substitution, also known as ``globbing&#39;&#39;. This word is then regarded as a pattern (``glob-pattern&#39;&#39;), and replaced with an alphabetically sorted list of file names which match the pattern.</p>
654
655 <p>One can upload/put a string by passing a reference to a scalar in the -local parameter. See example below.</p>
656
657 <p>put requires a working resource to be set before being called. See <code>open</code>.</p>
658
659 <p>The return value is always 1 or 0 indicating success or failure.</p>
660
661 <p>See <a>get()</a> for a description of what the optional callback parameter does.</p>
662
663 <p>You can also pass a <code>-headers</code> argument. That allows one to specify custom HTTP headers. It can be either a hashref with header names and values, or a <a>HTTP::Headers</a> object.</p>
664
665 <p><b>put examples:</b></p>
666
667 <p>Put a string to the server:</p>
668
669 <pre><code>my $myfile = &quot;This is the contents of a file to be uploaded\n&quot;;
670 $d-&gt;put(-local=&gt;\$myfile,-url=&gt;&quot;http://www.host.org/dav_dir/file.txt&quot;);</code></pre>
671
672 <p>Put a local file to the server:</p>
673
674 <pre><code>$d-&gt;put(-local=&gt;&quot;/tmp/index.html&quot;,-url=&gt;&quot;http://www.host.org/dav_dir/&quot;);</code></pre>
675
676 <p>Put a series of local files to the server:</p>
677
678 <pre><code> In these examples, /tmp contains file1.html, file1, file2.html,
679 file2.txt, file3.html, file2/
680
681 $d-&gt;put(-local=&gt;&quot;/tmp/file[12]*&quot;,-url=&gt;&quot;http://www.host.org/dav_dir/&quot;);
682
683 uploads file1.html, file1, file2.html, file2.txt and the directory file2/ to dav_dir/.</code></pre>
684
685 </dd>
686 <dt id="set_prop-URL-NAMESPACE-PROPNAME-PROPVALUE"><b>set_prop([URL],[NAMESPACE],PROPNAME,PROPVALUE)</b></dt>
687 <dd>
688
689 <p>Sets a property named <code>-propname</code> to <code>-propvalue</code> in the namespace <code>-namespace</code> for <code>-url</code>.</p>
690
691 <p>Requires a working resource to be set before being called. See <code>open</code>.</p>
692
693 <p>The return value is an <code>HTTP::DAV::Resource</code> object on success or 0 on failure.</p>
694
695 <p>The Resource object can be used for interrogating properties or performing other operations.</p>
696
697 <p>Example:</p>
698
699 <pre><code>if ( $r = $d-&gt;set_prop(-url=&gt;$url,
700 -namespace=&gt;&quot;dave&quot;,
701 -propname=&gt;&quot;author&quot;,
702 -propvalue=&gt;&quot;Patrick Collins&quot;
703 ) ) {
704 print &quot;Author property set\n&quot;;
705 } else {
706 print &quot;set_prop failed:&quot; . $d-&gt;message . &quot;\n&quot;;
707 }</code></pre>
708
709 <p>See the note in propfind about namespace support in HTTP::DAV. They&#39;re settable, but not readable.</p>
710
711 </dd>
712 <dt id="steal-URL"><b>steal([URL])</b></dt>
713 <dd>
714
715 <p>forcefully steals any locks held against URL.</p>
716
717 <p>steal will perform a propfind against URL and then, any locks that are found will be unlocked one by one regardless of whether we own them or not.</p>
718
719 <p>Requires a working resource to be set before being called. See <code>open</code>.</p>
720
721 <p>The return value is always 1 or 0 indicating success or failure. If multiple locks are found and unlocking one of them fails then the operation will be aborted.</p>
722
723 <pre><code>if ($d-&gt;steal()) {
724 print &quot;Steal succeeded\n&quot;;
725 } else {
726 print &quot;Steal failed: &quot;. $d-&gt;message() . &quot;\n&quot;;
727 }</code></pre>
728
729 </dd>
730 <dt id="unlock-URL"><b>unlock([URL])</b></dt>
731 <dd>
732
733 <p>unlocks any of our locks on URL.</p>
734
735 <p>Requires a working resource to be set before being called. See <code>open</code>.</p>
736
737 <p>The return value is always 1 or 0 indicating success or failure.</p>
738
739 <pre><code>if ($d-&gt;unlock()) {
740 print &quot;Unlock succeeded\n&quot;;
741 } else {
742 print &quot;Unlock failed: &quot;. $d-&gt;message() . &quot;\n&quot;;
743 }</code></pre>
744
745 </dd>
746 <dt id="unset_prop-URL-NAMESPACE-PROPNAME"><b>unset_prop([URL],[NAMESPACE],PROPNAME)</b></dt>
747 <dd>
748
749 <p>Unsets a property named <code>-propname</code> in the namespace <code>-namespace</code> for <code>-url</code>. Requires a working resource to be set before being called. See <code>open</code>.</p>
750
751 <p>The return value is an <code>HTTP::DAV::Resource</code> object on success or 0 on failure.</p>
752
753 <p>The Resource object can be used for interrogating properties or performing other operations.</p>
754
755 <p>Example:</p>
756
757 <pre><code>if ( $r = $d-&gt;unset_prop(-url=&gt;$url,
758 -namespace=&gt;&quot;dave&quot;,
759 -propname=&gt;&quot;author&quot;,
760 ) ) {
761 print &quot;Author property was unset\n&quot;;
762 } else {
763 print &quot;set_prop failed:&quot; . $d-&gt;message . &quot;\n&quot;;
764 }</code></pre>
765
766 <p>See the note in propfind about namespace support in HTTP::DAV. They&#39;re settable, but not readable.</p>
767
768 </dd>
769 </dl>
770
771 <h2 id="ACCESSOR-METHODS">ACCESSOR METHODS</h2>
772
773 <dl>
774
775 <dt id="get_user_agent"><b>get_user_agent</b></dt>
776 <dd>
777
778 <p>Returns the clients&#39; working <code>HTTP::DAV::UserAgent</code> object.</p>
779
780 <p>You may want to interact with the <code>HTTP::DAV::UserAgent</code> object to modify request headers or provide advanced authentication procedures. See dave for an advanced authentication procedure.</p>
781
782 </dd>
783 <dt id="get_last_request"><b>get_last_request</b></dt>
784 <dd>
785
786 <p>Takes no arguments and returns the clients&#39; last outgoing <code>HTTP::Request</code> object.</p>
787
788 <p>You would only use this to inspect a request that has already occurred.</p>
789
790 <p>If you would like to modify the <code>HTTP::Request</code> BEFORE the HTTP request takes place (for instance to add another header), you will need to get the <code>HTTP::DAV::UserAgent</code> using <code>get_user_agent</code> and interact with that.</p>
791
792 </dd>
793 <dt id="get_workingresource"><b>get_workingresource</b></dt>
794 <dd>
795
796 <p>Returns the currently &quot;opened&quot; or &quot;working&quot; resource (<code>HTTP::DAV::Resource</code>).</p>
797
798 <p>The working resource is changed whenever you open a url or use the cwd command.</p>
799
800 <p>e.g. $r = $d-&gt;get_workingresource print &quot;pwd: &quot; . $r-&gt;get_uri . &quot;\n&quot;;</p>
801
802 </dd>
803 <dt id="get_workingurl"><b>get_workingurl</b></dt>
804 <dd>
805
806 <p>Returns the currently &quot;opened&quot; or &quot;working&quot; <code>URL</code>.</p>
807
808 <p>The working resource is changed whenever you open a url or use the cwd command.</p>
809
810 <pre><code>print &quot;pwd: &quot; . $d-&gt;get_workingurl . &quot;\n&quot;;</code></pre>
811
812 </dd>
813 <dt id="get_lockedresourcelist"><b>get_lockedresourcelist</b></dt>
814 <dd>
815
816 <p>Returns an <code>HTTP::DAV::ResourceList</code> object that represents all of the locks we&#39;ve created using THIS dav client.</p>
817
818 <pre><code>print &quot;pwd: &quot; . $d-&gt;get_workingurl . &quot;\n&quot;;</code></pre>
819
820 </dd>
821 <dt id="get_absolute_uri-REL_URI-BASE_URI"><b>get_absolute_uri(REL_URI,[BASE_URI])</b></dt>
822 <dd>
823
824 <p>This is a useful utility function which joins <code>BASE_URI</code> and <code>REL_URI</code> and returns a new URI.</p>
825
826 <p>If <code>BASE_URI</code> is not supplied then the current working resource (as indicated by get_workingurl) is used. If <code>BASE_URI</code> is not set and there is no current working resource the <code>REL_URI</code> will be returned.</p>
827
828 <p>For instance: $d-&gt;open(&quot;http://host.org/webdav/dir1/&quot;);</p>
829
830 <pre><code># Returns &quot;http://host.org/webdav/dir2/&quot;
831 $d-&gt;get_absolute_uri(-rel_uri=&gt;&quot;../dir2&quot;);
832
833 # Returns &quot;http://x.org/dav/dir2/file.txt&quot;
834 $d-&gt;get_absolute_uri(-rel_uri =&gt;&quot;dir2/file.txt&quot;,
835 -&gt;base_uri=&gt;&quot;http://x.org/dav/&quot;);</code></pre>
836
837 <p>Note that it subtly takes care of trailing slashes.</p>
838
839 </dd>
840 </dl>
841
842 <h2 id="ERROR-HANDLING-METHODS">ERROR HANDLING METHODS</h2>
843
844 <dl>
845
846 <dt id="message"><b>message</b></dt>
847 <dd>
848
849 <p><code>message</code> gets the last success or error message.</p>
850
851 <p>The return value is always a scalar (string) and will change everytime a dav operation is invoked (lock, cwd, put, etc).</p>
852
853 <p>See also <code>errors</code> for operations which contain multiple error messages.</p>
854
855 </dd>
856 <dt id="errors"><b>errors</b></dt>
857 <dd>
858
859 <p>Returns an @array of error messages that had been set during a multi-request operation.</p>
860
861 <p>Some of <code>HTTP::DAV</code>&#39;s operations perform multiple request to the server. At the time of writing only put and get are considered multi-request since they can operate recursively requiring many HTTP requests.</p>
862
863 <p>In these situations you should check the errors array if to determine if any of the requests failed.</p>
864
865 <p>The <code>errors</code> function is used for multi-request operations and not to be confused with a multi-status server response. A multi-status server response is when the server responds with multiple error messages for a SINGLE request. To deal with multi-status responses, see <code>HTTP::DAV::Response</code>.</p>
866
867 <pre><code># Recursive put
868 if (!$d-&gt;put( &quot;/tmp/my_dir&quot;, $url ) ) {
869 # Get the overall message
870 print $d-&gt;message;
871 # Get the individual messages
872 foreach $err ( $d-&gt;errors ) { print &quot; Error:$err\n&quot; }
873 }</code></pre>
874
875 </dd>
876 <dt id="is_success"><b>is_success</b></dt>
877 <dd>
878
879 <p>Returns the status of the last DAV operation performed through the HTTP::DAV interface.</p>
880
881 <p>This value will always be the same as the value returned from an HTTP::DAV::method. For instance:</p>
882
883 <pre><code># This will always evaluate to true
884 ($d-&gt;lock($url) eq $d-&gt;is_success) ?</code></pre>
885
886 <p>You may want to use the is_success method if you didn&#39;t capture the return value immediately. But in most circumstances you&#39;re better off just evaluating as follows: if($d-&gt;lock($url)) { ... }</p>
887
888 </dd>
889 <dt id="get_last_response"><b>get_last_response</b></dt>
890 <dd>
891
892 <p>Takes no arguments and returns the last seen <code>HTTP::DAV::Response</code> object.</p>
893
894 <p>You may want to use this if you have just called a propfind and need the individual error messages returned in a MultiStatus.</p>
895
896 <p>If you find that you&#39;re using get_last_response() method a lot, you may be better off using the more advanced <code>HTTP::DAV</code> interface and interacting with the HTTP::DAV::* interfaces directly as discussed in the intro. For instance, if you find that you&#39;re always wanting a detailed understanding of the server&#39;s response headers or messages, then you&#39;re probably better off using the <code>HTTP::DAV::Resource</code> methods and interpreting the <code>HTTP::DAV::Response</code> directly.</p>
897
898 <p>To perform detailed analysis of the server&#39;s response (if for instance you got back a multistatus response) you can call <code>get_last_response()</code> which will return to you the most recent response object (always the result of the last operation, PUT, PROPFIND, etc). With the returned HTTP::DAV::Response object you can handle multi-status responses.</p>
899
900 <p>For example:</p>
901
902 <pre><code># Print all of the messages in a multistatus response
903 if (! $d-&gt;unlock($url) ) {
904 $response = $d-&gt;get_last_response();
905 if ($response-&gt;is_multistatus() ) {
906 foreach $num ( 0 .. $response-&gt;response_count() ) {
907 ($err_code,$mesg,$url,$desc) =
908 $response-&gt;response_bynum($num);
909 print &quot;$mesg ($err_code) for $url\n&quot;;
910 }
911 }
912 }</code></pre>
913
914 </dd>
915 </dl>
916
917 <h2 id="ADVANCED-METHODS">ADVANCED METHODS</h2>
918
919 <dl>
920
921 <dt id="new_resource"><b>new_resource</b></dt>
922 <dd>
923
924 <p>Creates a new resource object with which to play. This is the preferred way of creating an <code>HTTP::DAV::Resource</code> object if required. Why? Because each Resource object needs to sit within a global HTTP::DAV client. Also, because the new_resource routine checks the <code>HTTP::DAV</code> locked resource list before creating a new object.</p>
925
926 <pre><code>$dav-&gt;new_resource( -uri =&gt; &quot;http://...&quot; );</code></pre>
927
928 </dd>
929 <dt id="set_workingresource-URL"><b>set_workingresource(URL)</b></dt>
930 <dd>
931
932 <p>Sets the current working resource to URL.</p>
933
934 <p>You shouldn&#39;t need this method. Call open or cwd to set the working resource.</p>
935
936 <p>You CAN call <code>set_workingresource()</code> but you will need to perform a <code>propfind</code> immediately following it to ensure that the working resource is valid.</p>
937
938 </dd>
939 </dl>
940
941 <h1 id="INSTALLATION-TODO-MAILING-LISTS-and-REVISION-HISTORY">INSTALLATION, TODO, MAILING LISTS and REVISION HISTORY</h1>
942
943 <p>[OUTDATED]</p>
944
945 <p>Please see the primary HTTP::DAV webpage at (http://www.webdav.org/perldav/http-dav/) or the README file in this library.</p>
946
947 <h1 id="SEE-ALSO">SEE ALSO</h1>
948
949 <p>You&#39;ll want to also read:</p>
950
951 <dl>
952
953 <dt id="HTTP::DAV::Response"><code>HTTP::DAV::Response</code></dt>
954 <dd>
955
956 </dd>
957 <dt id="HTTP::DAV::Resource"><code>HTTP::DAV::Resource</code></dt>
958 <dd>
959
960 </dd>
961 <dt id="dave"><code>dave</code></dt>
962 <dd>
963
964 </dd>
965 </dl>
966
967 <p>and maybe if you&#39;re more inquisitive:</p>
968
969 <dl>
970
971 <dt id="LWP::UserAgent"><code>LWP::UserAgent</code></dt>
972 <dd>
973
974 </dd>
975 <dt id="HTTP::Request"><code>HTTP::Request</code></dt>
976 <dd>
977
978 </dd>
979 <dt id="HTTP::DAV::Comms"><code>HTTP::DAV::Comms</code></dt>
980 <dd>
981
982 </dd>
983 <dt id="HTTP::DAV::Lock"><code>HTTP::DAV::Lock</code></dt>
984 <dd>
985
986 </dd>
987 <dt id="HTTP::DAV::ResourceList"><code>HTTP::DAV::ResourceList</code></dt>
988 <dd>
989
990 </dd>
991 <dt id="HTTP::DAV::Utils"><code>HTTP::DAV::Utils</code></dt>
992 <dd>
993
994 </dd>
995 </dl>
996
997 <h1 id="AUTHOR-AND-COPYRIGHT">AUTHOR AND COPYRIGHT</h1>
998
999 <p>This module is Copyright (C) 2001-2008 by</p>
1000
1001 <pre><code>Patrick Collins
1002 G03 Gloucester Place, Kensington
1003 Sydney, Australia
1004
1005 Email: [email protected]
1006 Phone: +61 2 9663 4916</code></pre>
1007
1008 <p>All rights reserved.</p>
1009
1010 <p>Current co-maintainer of the module is Cosimo Streppone for Opera Software ASA, <a>[email protected]</a>.</p>
1011
1012 <p>You may distribute this module under the terms of either the GNU General Public License or the Artistic License, as specified in the Perl README file.</p>
1013
1014
1015 </body>
1016
1017 </html>
1018
1019