~ubuntu-branches/ubuntu/utopic/libhttp-dav-perl/utopic : revision 7

10

11

<body>

12

13

14

15

13

16

14

15

17

<!--

16

18

17

19

<ul>

35

37

36

38

<li><a href="#author_and_copyright">AUTHOR AND COPYRIGHT</a></li>

37

39

</ul>

40

38

41

-->

42

43

44

</div>

39

45

40

46

41

47

53

59

<pre>

54

60

use HTTP::DAV;

55

61

56

$d = new HTTP::DAV;

62

$d = HTTP::DAV->new();

57

63

$url = "<a href="http://host.org:8080/dav/&quot">http://host.org:8080/dav/&quot</a>;;

58

59

$d->credentials( -user=>"pcollins",-pass =>"mypass",

60

-url =>$url, -realm=>"DAV Realm" );

61

62

$d->open( -url=>"$url )

64

65

$d->credentials(

66

-user => "pcollins",

67

-pass => "mypass",

68

-url => $url,

69

-realm => "DAV Realm"

70

);

71

72

$d->open( -url => $url )

63

73

or die("Couldn't open $url: " .$d->message . "\n");

64

74

65

75

# Make a null lock on newdir

66

76

$d->lock( -url => "$url/newdir", -timeout => "10m" )

67

77

or die "Won't put unless I can lock for 10 minutes\n";</pre>

86

96

HTTP::DAV is part of the PerlDAV project hosted at <a href="http://www.webdav.org/perldav/">http://www.webdav.org/perldav/</a> and has the following features:

87

97

<ul>

88

98

<li>

89

Full RFC2518 method support. OPTIONS, TRACE, GET, HEAD, DELETE, PUT, COPY, MOVE, PROPFIND, PROPPATCH, LOCK, UNLOCK.

99

Full <a href="http://www.ietf.org/rfc/rfc2518.txt" class="rfc">RFC2518</a> method support. OPTIONS, TRACE, GET, HEAD, DELETE, PUT, COPY, MOVE, PROPFIND, PROPPATCH, LOCK, UNLOCK.

90

100

</li>

91

101

<li>

92

102

A fully object-oriented API.

104

114

Basic AND Digest authentication support (Digest auth requires the MD5 library). See INSTALLATION.

105

115

</li>

106

116

<li>

107

<a href="#item_dave"><code>dave</code></a>, 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've already installed HTTP::DAV, then dave will also have been installed (probably into /usr/local/bin). You can see it's man page by typing ``perldoc dave'' or going to <a href="http://www.webdav.org/perldav/dave/.">http://www.webdav.org/perldav/dave/.</a>

117

<a href="#dave"><code>dave</code></a>, 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've already installed HTTP::DAV, then dave will also have been installed (probably into /usr/local/bin). You can see it's man page by typing "perldoc dave" or going to <a href="http://www.webdav.org/perldav/dave/.">http://www.webdav.org/perldav/dave/.</a>

108

118

</li>

109

119

<li>

110

120

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.

111

121

</li>

112

122

<li>

113

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 ``sample scripts''. See ``make test'' and t/*.

123

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 "sample scripts". See "make test" and t/*.

114

124

</li>

115

125

</ul>

116

<code>HTTP::DAV</code> essentially has two API'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 ``down and dirty'' with your DAV and HTTP interactions.

117

The methods provided in <code>HTTP::DAV</code> should do most of what you want. If, however, you need more control over the client's operations or need more info about the server's responses then you will need to understand the rest of the HTTP::DAV::* interfaces. A good place to start is with the <a href="#item_http_3a_3adav_3a_3aresource"><code>HTTP::DAV::Resource</code></a> and <a href="#item_http_3a_3adav_3a_3aresponse"><code>HTTP::DAV::Response</code></a> documentation.

126

<code>HTTP::DAV</code> essentially has two API'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 "down and dirty" with your DAV and HTTP interactions.

127

The methods provided in <code>HTTP::DAV</code> should do most of what you want. If, however, you need more control over the client's operations or need more info about the server's responses then you will need to understand the rest of the HTTP::DAV::* interfaces. A good place to start is with the <a href="#http_dav_resource"><code>HTTP::DAV::Resource</code></a> and <a href="#http_dav_response"><code>HTTP::DAV::Response</code></a> documentation.

118

128

119

129

120

130

<hr />

142

152

<h2><a name="things_you_need_to_know">THINGS YOU NEED TO KNOW</a></h2>

143

153

In all of the methods specified in <a href="#public_methods">PUBLIC METHODS</a> there are some common concepts you'll need to understand:

144

154

<ul>

145

<li><a name="item_urls_represent_an_absolute_or_relative_uri_2e">URLs represent an absolute or relative URI.</a>

155

<li><a name="urls_represent_an_absolute_or_relative_uri" class="item">URLs represent an absolute or relative URI.</a>

146

156

147

157

<pre>

148

158

-url=>"host.org/dav_dir/" # Absolute

149

159

-url=>"/dav_dir/" # Relative

150

160

-url=>"file.txt" # Relative</pre>

151

You can only use a relative URL if you have already ``open''ed an absolute URL.

161

You can only use a relative URL if you have already "open"ed an absolute URL.

152

162

The HTTP::DAV module now consistently uses the named parameter: URL. The lower-level HTTP::DAV::Resource interface inconsistently interchanges URL and URI. I'm working to resolve this, in the meantime, you'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.

153

163

</li>

154

<li><a name="item_globs">GLOBS</a>

164

<li><a name="globs" class="item">GLOBS</a>

155

165

156

166

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.

157

The glob may contain the characters ``*'', ``?'' and the set operator ``[...]'' where ... contains multiple characters ([1t2]) or a range such ([1-5]). For the curious, the glob is converted to a regex and then matched: ``*'' to ``.*'', ``?'' to ``.'', and the [] is left untouched.

158

It is important to note that globs only operate at the leaf-level. For instance ``/my_dir/*/file.txt'' is not a valid glob.

167

The glob may contain the characters "*", "?" and the set operator "[...]" where ... contains multiple characters ([1t2]) or a range such ([1-5]). For the curious, the glob is converted to a regex and then matched: "*" to ".*", "?" to ".", and the [] is left untouched.

168

It is important to note that globs only operate at the leaf-level. For instance "/my_dir/*/file.txt" is not a valid glob.

159

169

If a glob matches no URL's the command will fail (which normally means returns 0).

160

Globs are useful in conjunction with <a href="#item_callbacks">CALLBACKS</a> to provide feedback as each operation completes.

170

Globs are useful in conjunction with <a href="#callbacks">CALLBACKS</a> to provide feedback as each operation completes.

161

171

See the documentation for each method to determine whether it supports globbing.

162

Globs are useful for interactive style applications (see the source code for <a href="#item_dave"><code>dave</code></a> as an example).

172

Globs are useful for interactive style applications (see the source code for <a href="#dave"><code>dave</code></a> as an example).

163

173

Example globs:

164

174

<pre>

165

175

$dav1->delete(-url=>"/my_dir/file[1-3]"); # Matches file1, file2, file3

166

176

$dav1->delete(-url=>"/my_dir/file[1-3]*.txt");# Matches file1*.txt,file2*.txt,file3*.txt

167

177

$dav1->delete(-url=>"/my_dir/*/file.txt"); # Invalid. Can only match at leaf-level</pre>

168

178

</li>

169

<li><a name="item_callbacks">CALLBACKS</a>

179

<li><a name="callbacks" class="item">CALLBACKS</a>

170

180

171

181

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 (\&ref) to the method.

172

182

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.

180

190

}

181

191

The <code>status</code> argument specifies whether the operation has succeeded (1), failed (0), or is in progress (-1).

182

192

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.

183

The <code>url</code> the remote URL.

184

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 ``56% to go'' style-gauges.

185

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 <a href="#item_put"><code>put</code></a>.

186

See the source code of <a href="#item_dave"><code>dave</code></a> for a useful sample of how to setup a callback.

193

The <a href="#url"><code>url</code></a> the remote URL.

194

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 "56% to go" style-gauges.

195

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 <a href="#put"><code>put</code></a>.

196

See the source code of <a href="#dave"><code>dave</code></a> for a useful sample of how to setup a callback.

187

197

Note that these arguments are NOT named parameters.

188

All error messages set during a ``multi-operation'' request (for instance a recursive get/put) are also retrievable via the <a href="#item_errors"><code>errors()</code></a> function once the operation has completed. See <code>ERROR HANDLING</code> for more information.

198

All error messages set during a "multi-operation" request (for instance a recursive get/put) are also retrievable via the <a href="#errors"><code>errors()</code></a> function once the operation has completed. See <code>ERROR HANDLING</code> for more information.

189

199

</li>

190

200

</ul>

191

201

192

202

193

203

<h2><a name="public_methods">PUBLIC METHODS</a></h2>

194

204

<dl>

195

<dt><a name="item_new">new(USERAGENT)</a></dt>

205

<dt><a name="new" class="item">new(USERAGENT)</a></dt>

206

207

<dt>new(USERAGENT, HEADERS)</dt>

196

208

197

209

<dd>

198

210

Creates a new <code>HTTP::DAV</code> client

199

211

<pre>

200

$d = HTTP::DAV->new()</pre>

201

The <code>-useragent</code> parameter expects an <code>HTTP::DAV::UserAgent</code> object. See the <a href="#item_dave"><code>dave</code></a> program for an advanced example of a custom UserAgent that interactively prompts the user for their username and password.

212

$d = HTTP::DAV->new();</pre>

213

The <code>-useragent</code> parameter allows you to pass your own user agent object and expects an <code>HTTP::DAV::UserAgent</code> object. See the <a href="#dave"><code>dave</code></a> program for an advanced example of a custom UserAgent that interactively prompts the user for their username and password.

214

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:

215

<pre>

216

{ "X-My-Header" => "value", ... }</pre>

217

or a <a href="HTTP/Headers.html">the HTTP::Headers manpage</a> object.

202

218

</dd>

203

<dt><a name="item_credentials">credentials(USER,PASS,[URL],[REALM])</a></dt>

219

<dt><a name="credentials" class="item">credentials(USER,PASS,[URL],[REALM])</a></dt>

204

220

205

221

<dd>

206

222

sets authorization credentials for a <code>URL</code> and/or <code>REALM</code>.

213

229

-user=>'pcollins',

214

230

-pass=>'mypass');</pre>

215

231

</dd>

216

<dt><a name="item_debuglevel">DebugLevel($val)</a></dt>

232

<dt><a name="debuglevel" class="item">DebugLevel($val)</a></dt>

217

233

218

234

<dd>

219

235

sets the debug level to <code>$val</code>. 0=off 3=noisy.

220

236

<code>$val</code> default is 0.

221

237

returns no value.

222

When the value is greater than 1, the <a href="#item_http_3a_3adav_3a_3acomms"><code>HTTP::DAV::Comms</code></a> module will log all of the client<=>server interactions into /tmp/perldav_debug.txt.

238

When the value is greater than 1, the <a href="#http_dav_comms"><code>HTTP::DAV::Comms</code></a> module will log all of the client<=>server interactions into /tmp/perldav_debug.txt.

223

239

</dd>

224

240

</dl>

225

241

227

243

<h2><a name="dav_operations">DAV OPERATIONS</a></h2>

228

244

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.

229

245

<dl>

230

<dt><a name="item_copy">copy(URL,DEST,[OVERWRITE],[DEPTH])</a></dt>

246

<dt><a name="copy" class="item">copy(URL,DEST,[OVERWRITE],[DEPTH])</a></dt>

231

247

232

248

<dd>

233

249

copies one remote resource to another

234

250

<dl>

235

251

236

252

237

253

<dd>

238

254

is the remote resource you'd like to copy. Mandatory

239

255

</dd>

240

256

241

257

242

258

<dd>

243

259

is the remote target for the copy command. Mandatory

244

260

</dd>

245

<dt><a name="item__2doverwrite"><code>-overwrite</code></a></dt>

261

<dt><a name="overwrite" class="item"><code>-overwrite</code></a></dt>

246

262

247

263

<dd>

248

optionally indicates whether the server should fail if the target exists. Valid values are ``T'' and ``F'' (1 and 0 are synonymous). Default is T.

264

optionally indicates whether the server should fail if the target exists. Valid values are "T" and "F" (1 and 0 are synonymous). Default is T.

249

265

</dd>

250

<dt><a name="item__2ddepth"><code>-depth</code></a></dt>

266

<dt><a name="depth" class="item"><code>-depth</code></a></dt>

251

267

252

268

<dd>

253

optionally indicates whether the server should do a recursive copy or not. Valid values are 0 and (1 or ``infinity''). Default is ``infinity'' (1).

269

optionally indicates whether the server should do a recursive copy or not. Valid values are 0 and (1 or "infinity"). Default is "infinity" (1).

254

270

</dd>

255

271

</dl>

256

272

The return value is always 1 or 0 indicating success or failure.

257

Requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

273

Requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

258

274

Note: if either <code>'URL'</code> or <code>'DEST'</code> are locked by this dav client, then the lock headers will be taken care of automatically. If the either of the two URL's are locked by someone else, the server should reject the request.

259

275

copy examples:

260

276

<pre>

273

289

<pre>

274

290

$d->copy("file.txt","/dav_dir/dir2/new_file.txt")</pre>

275

291

</dd>

276

292

277

293

278

294

<dd>

279

295

changes the remote working directory.

283

299

$d->cwd("../dir2");

284

300

$d->cwd(-url=>"../dir1");</pre>

285

301

The return value is always 1 or 0 indicating success or failure.

286

Requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

302

Requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

287

303

You can not cwd to files, only collections (directories).

288

304

</dd>

289

<dt><a name="item_delete">delete(URL)</a></dt>

305

<dt><a name="delete" class="item">delete(URL)</a></dt>

290

306

291

307

<dd>

292

308

deletes a remote resource.

296

312

$d->delete("./dir1");

297

313

$d->delete(-url=>"/dav_dir/dir2/file*",-callback=>\&mycallback);</pre>

298

314

</dd>

299

315

300

316

301

317

<dd>

302

is the remote <code>resource(s)</code> you'd like to delete. It can be a file, directory or <code>glob</code>.

318

is the remote resource(s) you'd like to delete. It can be a file, directory or <code>glob</code>.

303

319

</dd>

304

<dt><a name="item__2dcallback_is_a_reference_to_a_callback_function_"><a href="#item__2dcallback"><code>-callback</code></a> 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 href="#item_globs">GLOBS</a> deletes. See callbacks</a></dt>

320

<dt><a name="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" class="item"><a href="#callback"><code>-callback</code></a> 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 href="#globs">GLOBS</a> deletes. See callbacks</a></dt>

305

321

306

322

<dd>

307

323

The return value is always 1 or 0 indicating success or failure.

308

Requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

309

This command will recursively delete directories. BE CAREFUL of uninitialised file variables in situation like this: $d->delete(``$dir/$file''). This will trash your $dir if $file is not set.

324

Requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

325

This command will recursively delete directories. BE CAREFUL of uninitialised file variables in situation like this: $d-><a href="#delete"><code>delete("$dir/$file")</code></a>. This will trash your $dir if $file is not set.

310

326

</dd>

311

<dt><a name="item_get">get(URL,[TO],[CALLBACK])</a></dt>

327

<dt><a name="get" class="item">get(URL,[TO],[CALLBACK])</a></dt>

312

328

313

329

<dd>

314

330

downloads the file or directory at <code>URL</code> to the local location indicated by <code>TO</code>.

315

331

<dl>

316

332

317

333

318

334

<dd>

319

is the remote resource you'd like to get. It can be a file or directory or a ``glob''.

335

is the remote resource you'd like to get. It can be a file or directory or a "glob".

320

336

</dd>

321

337

322

338

323

339

<dd>

324

340

is where you'd like to put the remote resource. The -to parameter can be:

328

344

- a B<FileHandle reference>.</pre>

329

345

<pre>

330

346

- a reference to a B<scalar object> into which the contents will be saved.</pre>

331

If the <a href="#item__2durl"><code>-url</code></a> matches multiple files (via a glob or a directory download), then the <a href="#item_get"><code>get</code></a> routine will return an error if you try to use a FileHandle reference or a scalar reference.

347

If the <a href="#url"><code>-url</code></a> matches multiple files (via a glob or a directory download), then the <a href="#get"><code>get</code></a> routine will return an error if you try to use a FileHandle reference or a scalar reference.

332

348

</dd>

333

<dt><a name="item__2dcallback"><code>-callback</code></a></dt>

349

<dt><a name="callback" class="item"><code>-callback</code></a></dt>

334

350

335

351

<dd>

336

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's can take a very long time and the user may require some visual feedback. See <a href="#item_callbacks">CALLBACKS</a> for an examples and how to use a callback.

352

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's can take a very long time and the user may require some visual feedback. See <a href="#callbacks">CALLBACKS</a> for an examples and how to use a callback.

337

353

</dd>

338

354

</dl>

339

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'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 <a href="#item_errors"><code>errors()</code></a> routine to handle error conditions.

355

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'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 <a href="#errors"><code>errors()</code></a> routine to handle error conditions.

340

356

Previous versions of HTTP::DAV allowed the return value to be the file contents if no -to attribute was supplied. This functionality is deprecated.

341

Requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

357

Requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

342

358

get examples:

343

359

<pre>

344

360

$d->open("host.org/dav_dir/");</pre>

373

389

<pre>

374

390

$d->get("/dav_dir/*/index.html","/tmp"); # Can not glob like this.</pre>

375

391

</dd>

376

<dt><a name="item_lock">lock([URL],[OWNER],[DEPTH],[TIMEOUT],[SCOPE],[TYPE])</a></dt>

392

<dt><a name="lock" class="item">lock([URL],[OWNER],[DEPTH],[TIMEOUT],[SCOPE],[TYPE])</a></dt>

377

393

378

394

<dd>

379

395

locks a resource. If URL is not specified, it will lock the current working resource (opened resource).

384

400

-scope => "exclusive",

385

401

-type => "write",

386

402

-timeout => "10h" )</pre>

387

See <a href="#item_http_3a_3adav_3a_3aresource"><code>HTTP::DAV::Resource</code></a> <a href="#item_lock"><code>lock()</code></a> for details of the above parameters.

403

See <a href="#http_dav_resource"><code>HTTP::DAV::Resource</code></a> <a href="#lock"><code>lock()</code></a> for details of the above parameters.

388

404

The return value is always 1 or 0 indicating success or failure.

389

Requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

390

When you lock a resource, the lock is held against the current HTTP::DAV object. In fact, the locks are held in a <a href="#item_http_3a_3adav_3a_3aresourcelist"><code>HTTP::DAV::ResourceList</code></a> object. You can operate against all of the locks that you have created as follows:

405

Requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

406

When you lock a resource, the lock is held against the current HTTP::DAV object. In fact, the locks are held in a <a href="#http_dav_resourcelist"><code>HTTP::DAV::ResourceList</code></a> object. You can operate against all of the locks that you have created as follows:

391

407

<pre>

392

408

## Print and unlock all locks that we own.

393

409

my $rl_obj = $d->get_lockedresourcelist();

400

416

## Unlock them?

401

417

$resource->unlock;

402

418

}</pre>

403

Typically, a simple $d-><a href="#item_unlock"><code>unlock($uri)</code></a> will suffice.

419

Typically, a simple $d-><a href="#unlock"><code>unlock($uri)</code></a> will suffice.

404

420

lock example

405

421

<pre>

406

422

$d->lock($uri, -timeout=>"1d");

408

424

$d->put("/tmp/index.html",$uri);

409

425

$d->unlock($uri);</pre>

410

426

</dd>

411

<dt><a name="item_mkcol">mkcol(URL)</a></dt>

427

<dt><a name="mkcol" class="item">mkcol(URL)</a></dt>

412

428

413

429

<dd>

414

430

make a remote collection (directory)

415

431

The return value is always 1 or 0 indicating success or failure.

416

Requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

432

Requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

417

433

<pre>

418

434

$d->open("host.org/dav_dir/");

419

435

$d->mkcol("new_dir"); # Should succeed

420

436

$d->mkcol("/dav_dir/new_dir"); # Should succeed

421

437

$d->mkcol("/dav_dir/new_dir/xxx/yyy"); # Should fail</pre>

422

438

</dd>

423

<dt><a name="item_move">move(URL,DEST,[OVERWRITE],[DEPTH])</a></dt>

439

<dt><a name="move" class="item">move(URL,DEST,[OVERWRITE],[DEPTH])</a></dt>

424

440

425

441

<dd>

426

442

moves one remote resource to another

427

443

<dl>

428

444

429

445

430

446

<dd>

431

447

is the remote resource you'd like to move. Mandatory

432

448

</dd>

433

449

434

450

435

451

<dd>

436

452

is the remote target for the move command. Mandatory

437

453

</dd>

438

<dt><code>-overwrite</code></dt>

454

<dt><a name="overwrite2" class="item"><a href="#overwrite"><code>-overwrite</code></a></a></dt>

439

455

440

456

<dd>

441

optionally indicates whether the server should fail if the target exists. Valid values are ``T'' and ``F'' (1 and 0 are synonymous). Default is T.

457

optionally indicates whether the server should fail if the target exists. Valid values are "T" and "F" (1 and 0 are synonymous). Default is T.

442

458

</dd>

443

459

</dl>

444

Requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

460

Requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

445

461

The return value is always 1 or 0 indicating success or failure.

446

462

Note: if either <code>'URL'</code> or <code>'DEST'</code> are locked by this dav client, then the lock headers will be taken care of automatically. If either of the two URL's are locked by someone else, the server should reject the request.

447

463

move examples:

461

477

<pre>

462

478

$d->move("file.txt","/dav_dir/dir2/new_file.txt")</pre>

463

479

</dd>

464

480

465

481

466

482

<dd>

467

483

opens the directory (collection resource) at URL.

468

484

open will perform a propfind against URL. If the server does not understand the request then the open will fail.

469

485

Similarly, if the server indicates that the resource at URL is NOT a collection, the open command will fail.

470

486

</dd>

471

<dt><a name="item_options">options([URL])</a></dt>

487

<dt><a name="options" class="item">options([URL])</a></dt>

472

488

473

489

<dd>

474

490

Performs an OPTIONS request against the URL or the working resource if URL is not supplied.

475

Requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

491

Requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

476

492

The return value is a string of comma separated OPTIONS that the server states are legal for URL or undef otherwise.

477

493

A fully compliant DAV server may offer as many methods as: OPTIONS, TRACE, GET, HEAD, DELETE, PUT, COPY, MOVE, PROPFIND, PROPPATCH, LOCK, UNLOCK

478

494

Note: IIS5 does not support PROPPATCH or LOCK on collections.

489

505

print "OK to proppatch\n";

490

506

}</pre>

491

507

</dd>

492

<dt><a name="item_propfind">propfind([URL],[DEPTH])</a></dt>

508

<dt><a name="propfind" class="item">propfind([URL],[DEPTH])</a></dt>

493

509

494

510

<dd>

495

511

Perform a propfind against URL at DEPTH depth.

496

<a href="#item__2ddepth"><code>-depth</code></a> can be used to specify how deep the propfind goes. ``0'' is collection only. ``1'' is collection and it's immediate members (This is the default value). ``infinity'' is the entire directory tree. Note that most DAV compliant servers deny ``infinity'' depth propfinds for security reasons.

497

Requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

498

The return value is an <a href="#item_http_3a_3adav_3a_3aresource"><code>HTTP::DAV::Resource</code></a> object on success or 0 on failure.

512

<a href="#depth"><code>-depth</code></a> can be used to specify how deep the propfind goes. "0" is collection only. "1" is collection and it's immediate members (This is the default value). "infinity" is the entire directory tree. Note that most DAV compliant servers deny "infinity" depth propfinds for security reasons.

513

Requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

514

The return value is an <a href="#http_dav_resource"><code>HTTP::DAV::Resource</code></a> object on success or 0 on failure.

499

515

The Resource object can be used for interrogating properties or performing other operations.

500

516

<pre>

501

517

## Print collection or content length

509

525

}</pre>

510

526

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'm working on the solution.

511

527

</dd>

512

<dt><a name="item_proppatch">proppatch([URL],[NAMESPACE],PROPNAME,PROPVALUE,ACTION,[NSABBR])</a></dt>

528

<dt><a name="proppatch" class="item">proppatch([URL],[NAMESPACE],PROPNAME,PROPVALUE,ACTION,[NSABBR])</a></dt>

513

529

514

530

<dd>

515

If <code>-action</code> equals ``set'' then we set a property named <code>-propname</code> to <code>-propvalue</code> in the namespace <code>-namespace</code> for <a href="#item__2durl"><code>-url</code></a>.

516

If <code>-action</code> equals ``remove'' then we unset a property named <code>-propname</code> in the namespace <code>-namespace</code> for <a href="#item__2durl"><code>-url</code></a>.

517

If no action is supplied then the default action is ``set''.

518

The return value is an <a href="#item_http_3a_3adav_3a_3aresource"><code>HTTP::DAV::Resource</code></a> object on success or 0 on failure.

531

If <code>-action</code> equals "set" then we set a property named <code>-propname</code> to <code>-propvalue</code> in the namespace <code>-namespace</code> for <a href="#url"><code>-url</code></a>.

532

If <code>-action</code> equals "remove" then we unset a property named <code>-propname</code> in the namespace <code>-namespace</code> for <a href="#url"><code>-url</code></a>.

533

If no action is supplied then the default action is "set".

534

The return value is an <a href="#http_dav_resource"><code>HTTP::DAV::Resource</code></a> object on success or 0 on failure.

519

535

The Resource object can be used for interrogating properties or performing other operations.

520

536

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're welcome to play around with DAV namespaces.

521

Requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

522

It is recommended that you use <a href="#item_set_prop"><code>set_prop</code></a> and <a href="#item_unset_prop"><code>unset_prop</code></a> instead of proppatch for readability.

523

<a href="#item_set_prop"><code>set_prop</code></a> simply calls <a href="#item_proppatch"><code>proppatch(-action=</code></a>set)> and <a href="#item_unset_prop"><code>unset_prop</code></a> calls <a href="#item_proppatch"><code>proppatch(-action=</code></a>``remove'')>

524

See <a href="#item_set_prop"><code>set_prop</code></a> and <a href="#item_unset_prop"><code>unset_prop</code></a> for examples.

537

Requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

538

It is recommended that you use <a href="#set_prop"><code>set_prop</code></a> and <a href="#unset_prop"><code>unset_prop</code></a> instead of proppatch for readability.

539

<a href="#set_prop"><code>set_prop</code></a> simply calls <a href="#proppatch"><code>proppatch(-action=</code></a>set)> and <a href="#unset_prop"><code>unset_prop</code></a> calls <a href="#proppatch"><code>proppatch(-action=</code></a>"remove")>

540

See <a href="#set_prop"><code>set_prop</code></a> and <a href="#unset_prop"><code>unset_prop</code></a> for examples.

525

541

</dd>

526

<dt><a name="item_put">put(LOCAL,[URL],[CALLBACK])</a></dt>

542

<dt><a name="put" class="item">put(LOCAL,[URL],[CALLBACK],[HEADERS])</a></dt>

527

543

528

544

<dd>

529

uploads the files or directories at -local to the remote destination at -url.

530

-local points to a file, directory or series of files or directories (indicated by a glob).

545

uploads the files or directories at <code>-local</code> to the remote destination at <a href="#url"><code>-url</code></a>.

546

<code>-local</code> points to a file, directory or series of files or directories (indicated by a glob).

531

547

If the filename contains any of the characters `*', `?' or `[' it is a candidate for filename substitution, also known as ``globbing''. This word is then regarded as a pattern (``glob-pattern''), and replaced with an alphabetically sorted list of file names which match the pattern.

532

548

One can upload/put a string by passing a reference to a scalar in the -local parameter. See example below.

533

put requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

549

put requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

534

550

The return value is always 1 or 0 indicating success or failure.

535

See <a href="#item_get">get()</a> for a description of what the optional callback parameter does.

551

See <a href="#get">get()</a> for a description of what the optional callback parameter does.

552

You can also pass a <code>-headers</code> argument. That allows to specify custom HTTP headers. It can be either a hashref with header names and values, or a <a href="HTTP/Headers.html">the HTTP::Headers manpage</a> object.

536

553

put examples:

537

554

Put a string to the server:

538

555

<pre>

550

567

551

568

uploads file1.html, file1, file2.html, file2.txt and the directory file2/ to dav_dir/.</pre>

552

569

</dd>

553

<dt><a name="item_set_prop">set_prop([URL],[NAMESPACE],PROPNAME,PROPVALUE)</a></dt>

570

<dt><a name="set_prop" class="item">set_prop([URL],[NAMESPACE],PROPNAME,PROPVALUE)</a></dt>

554

571

555

572

<dd>

556

Sets a property named <code>-propname</code> to <code>-propvalue</code> in the namespace <code>-namespace</code> for <a href="#item__2durl"><code>-url</code></a>.

557

Requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

558

The return value is an <a href="#item_http_3a_3adav_3a_3aresource"><code>HTTP::DAV::Resource</code></a> object on success or 0 on failure.

573

Sets a property named <code>-propname</code> to <code>-propvalue</code> in the namespace <code>-namespace</code> for <a href="#url"><code>-url</code></a>.

574

Requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

575

The return value is an <a href="#http_dav_resource"><code>HTTP::DAV::Resource</code></a> object on success or 0 on failure.

559

576

The Resource object can be used for interrogating properties or performing other operations.

560

577

Example:

561

578

<pre>

570

587

}</pre>

571

588

See the note in propfind about namespace support in HTTP::DAV. They're settable, but not readable.

572

589

</dd>

573

<dt><a name="item_steal">steal([URL])</a></dt>

590

<dt><a name="steal" class="item">steal([URL])</a></dt>

574

591

575

592

<dd>

576

593

forcefully steals any locks held against URL.

577

594

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.

578

Requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

595

Requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

579

596

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.

580

597

<pre>

581

598

if ($d->steal()) {

584

601

print "Steal failed: ". $d->message() . "\n";

585

602

}</pre>

586

603

</dd>

587

<dt><a name="item_unlock">unlock([URL])</a></dt>

604

<dt><a name="unlock" class="item">unlock([URL])</a></dt>

588

605

589

606

<dd>

590

607

unlocks any of our locks on URL.

591

Requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

608

Requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

592

609

The return value is always 1 or 0 indicating success or failure.

593

610

<pre>

594

611

if ($d->unlock()) {

597

614

print "Unlock failed: ". $d->message() . "\n";

598

615

}</pre>

599

616

</dd>

600

<dt><a name="item_unset_prop">unset_prop([URL],[NAMESPACE],PROPNAME)</a></dt>

617

<dt><a name="unset_prop" class="item">unset_prop([URL],[NAMESPACE],PROPNAME)</a></dt>

601

618

602

619

<dd>

603

Unsets a property named <code>-propname</code> in the namespace <code>-namespace</code> for <a href="#item__2durl"><code>-url</code></a>.

604

Requires a working resource to be set before being called. See <a href="#item_open"><code>open</code></a>.

605

The return value is an <a href="#item_http_3a_3adav_3a_3aresource"><code>HTTP::DAV::Resource</code></a> object on success or 0 on failure.

620

Unsets a property named <code>-propname</code> in the namespace <code>-namespace</code> for <a href="#url"><code>-url</code></a>.

621

Requires a working resource to be set before being called. See <a href="#open"><code>open</code></a>.

622

The return value is an <a href="#http_dav_resource"><code>HTTP::DAV::Resource</code></a> object on success or 0 on failure.

606

623

The Resource object can be used for interrogating properties or performing other operations.

607

624

Example:

608

625

<pre>

621

638

622

639

<h2><a name="accessor_methods">ACCESSOR METHODS</a></h2>

623

640

<dl>

624

<dt><a name="item_get_user_agent">get_user_agent</a></dt>

641

<dt><a name="get_user_agent" class="item">get_user_agent</a></dt>

625

642

626

643

<dd>

627

644

Returns the clients' working <code>HTTP::DAV::UserAgent</code> object.

629

646

to modify request headers or provide advanced authentication

630

647

procedures. See dave for an advanced authentication procedure.

631

648

</dd>

632

<dt><a name="item_get_last_request">get_last_request</a></dt>

649

<dt><a name="get_last_request" class="item">get_last_request</a></dt>

633

650

634

651

<dd>

635

Takes no arguments and returns the clients' last outgoing <a href="#item_http_3a_3arequest"><code>HTTP::Request</code></a> object.

652

Takes no arguments and returns the clients' last outgoing <a href="#http_request"><code>HTTP::Request</code></a> object.

636

653

You would only use this to inspect a request that has already occurred.

637

If you would like to modify the <a href="#item_http_3a_3arequest"><code>HTTP::Request</code></a> BEFORE the HTTP request takes place (for instance to add another header), you will need to get the <code>HTTP::DAV::UserAgent</code> using <a href="#item_get_user_agent"><code>get_user_agent</code></a> and interact with that.

654

If you would like to modify the <a href="#http_request"><code>HTTP::Request</code></a> BEFORE the HTTP request takes place (for instance to add another header), you will need to get the <code>HTTP::DAV::UserAgent</code> using <a href="#get_user_agent"><code>get_user_agent</code></a> and interact with that.

638

655

</dd>

639

<dt><a name="item_get_workingresource">get_workingresource</a></dt>

656

<dt><a name="get_workingresource" class="item">get_workingresource</a></dt>

640

657

641

658

<dd>

642

Returns the currently ``opened'' or ``working'' resource (<a href="#item_http_3a_3adav_3a_3aresource"><code>HTTP::DAV::Resource</code></a>).

659

Returns the currently "opened" or "working" resource (<a href="#http_dav_resource"><code>HTTP::DAV::Resource</code></a>).

643

660

The working resource is changed whenever you open a url or use the cwd command.

644

661

e.g.

645

662

$r = $d->get_workingresource

646

print ``pwd: '' . $r->get_uri . ``\n'';

663

print "pwd: " . $r->get_uri . "\n";

647

664

</dd>

648

<dt><a name="item_get_workingurl">get_workingurl</a></dt>

665

<dt><a name="get_workingurl" class="item">get_workingurl</a></dt>

649

666

650

667

<dd>

651

Returns the currently ``opened'' or ``working'' <code>URL</code>.

668

Returns the currently "opened" or "working" <code>URL</code>.

652

669

The working resource is changed whenever you open a url or use the cwd command.

653

670

<pre>

654

671

print "pwd: " . $d->get_workingurl . "\n";</pre>

655

672

</dd>

656

<dt><a name="item_get_lockedresourcelist">get_lockedresourcelist</a></dt>

673

<dt><a name="get_lockedresourcelist" class="item">get_lockedresourcelist</a></dt>

657

674

658

675

<dd>

659

Returns an <a href="#item_http_3a_3adav_3a_3aresourcelist"><code>HTTP::DAV::ResourceList</code></a> object that represents all of the locks we've created using THIS dav client.

676

Returns an <a href="#http_dav_resourcelist"><code>HTTP::DAV::ResourceList</code></a> object that represents all of the locks we've created using THIS dav client.

660

677

<pre>

661

678

print "pwd: " . $d->get_workingurl . "\n";</pre>

662

679

</dd>

663

<dt><a name="item_get_absolute_uri">get_absolute_uri(REL_URI,[BASE_URI])</a></dt>

680

<dt><a name="get_absolute_uri" class="item">get_absolute_uri(REL_URI,[BASE_URI])</a></dt>

664

681

665

682

<dd>

666

683

This is a useful utility function which joins <code>BASE_URI</code> and <code>REL_URI</code> and returns a new URI.

667

684

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.

668

685

For instance:

669

$d->open(``http://host.org/webdav/dir1/'');

686

$d->open("http://host.org/webdav/dir1/");

670

687

<pre>

671

688

# Returns "<a href="http://host.org/webdav/dir2/&quot">http://host.org/webdav/dir2/&quot</a>;

672

689

$d->get_absolute_uri(-rel_uri=>"../dir2");</pre>

681

698

682

699

<h2><a name="error_handling_methods">ERROR HANDLING METHODS</a></h2>

683

700

<dl>

684

<dt><a name="item_message">message</a></dt>

701

<dt><a name="message" class="item">message</a></dt>

685

702

686

703

<dd>

687

<a href="#item_message"><code>message</code></a> gets the last success or error message.

704

<a href="#message"><code>message</code></a> gets the last success or error message.

688

705

The return value is always a scalar (string) and will change everytime a dav operation is invoked (lock, cwd, put, etc).

689

See also <a href="#item_errors"><code>errors</code></a> for operations which contain multiple error messages.

706

See also <a href="#errors"><code>errors</code></a> for operations which contain multiple error messages.

690

707

</dd>

691

<dt><a name="item_errors">errors</a></dt>

708

<dt><a name="errors" class="item">errors</a></dt>

692

709

693

710

<dd>

694

711

Returns an @array of error messages that had been set during a multi-request operation.

695

712

Some of <code>HTTP::DAV</code>'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.

696

713

In these situations you should check the errors array if to determine if any of the requests failed.

697

The <a href="#item_errors"><code>errors</code></a> 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 <a href="#item_http_3a_3adav_3a_3aresponse"><code>HTTP::DAV::Response</code></a>.

714

The <a href="#errors"><code>errors</code></a> 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 <a href="#http_dav_response"><code>HTTP::DAV::Response</code></a>.

698

715

<pre>

699

716

# Recursive put

700

717

if (!$d->put( "/tmp/my_dir", $url ) ) {

704

721

foreach $err ( $d->errors ) { print " Error:$err\n" }

705

722

}</pre>

706

723

</dd>

707

<dt><a name="item_is_success">is_success</a></dt>

724

<dt><a name="is_success" class="item">is_success</a></dt>

708

725

709

726

<dd>

710

727

Returns the status of the last DAV operation performed through the HTTP::DAV interface.

713

730

# This will always evaluate to true

714

731

($d->lock($url) eq $d->is_success) ?</pre>

715

732

You may want to use the is_success method if you didn't capture the return value immediately. But in most circumstances you're better off just evaluating as follows:

716

if($d-><a href="#item_lock"><code>lock($url))</code></a> { ... }

733

if($d->lock($url)) { ... }

717

734

</dd>

718

<dt><a name="item_get_lastresponse">get_lastresponse</a></dt>

735

<dt><a name="get_last_response" class="item">get_last_response</a></dt>

719

736

720

737

<dd>

721

Takes no arguments and returns the last seen <a href="#item_http_3a_3adav_3a_3aresponse"><code>HTTP::DAV::Response</code></a> object.

738

Takes no arguments and returns the last seen <a href="#http_dav_response"><code>HTTP::DAV::Response</code></a> object.

722

739

You may want to use this if you have just called a propfind and need the individual error messages returned in a MultiStatus.

723

If you find that you're using <code>get_last_response()</code> 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're always wanting a detailed understanding of the server's response headers or messages, then you're probably better off using the <a href="#item_http_3a_3adav_3a_3aresource"><code>HTTP::DAV::Resource</code></a> methods and interpreting the <a href="#item_http_3a_3adav_3a_3aresponse"><code>HTTP::DAV::Response</code></a> directly.

724

To perform detailed analysis of the server's response (if for instance you got back a multistatus response) you can call get_lastresponse 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.

740

If you find that you're using <a href="#get_last_response"><code>get_last_response()</code></a> 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're always wanting a detailed understanding of the server's response headers or messages, then you're probably better off using the <a href="#http_dav_resource"><code>HTTP::DAV::Resource</code></a> methods and interpreting the <a href="#http_dav_response"><code>HTTP::DAV::Response</code></a> directly.

741

To perform detailed analysis of the server's response (if for instance you got back a multistatus response) you can call <a href="#get_last_response"><code>get_last_response()</code></a> 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.

725

742

For example:

726

743

<pre>

727

744

# Print all of the messages in a multistatus response

728

745

if (! $d->unlock($url) ) {

729

$response = $d->get_lastresponse();

746

$response = $d->get_last_response();

730

747

if ($response->is_multistatus() ) {

731

748

foreach $num ( 0 .. $response->response_count() ) {

732

749

($err_code,$mesg,$url,$desc) =

741

758

742

759

<h2><a name="advanced_methods">ADVANCED METHODS</a></h2>

743

760

<dl>

744

<dt><a name="item_new_resource">new_resource</a></dt>

761

<dt><a name="new_resource" class="item">new_resource</a></dt>

745

762

746

763

<dd>

747

764

Creates a new resource object with which to play.

748

This is the preferred way of creating an <a href="#item_http_3a_3adav_3a_3aresource"><code>HTTP::DAV::Resource</code></a> object if required.

765

This is the preferred way of creating an <a href="#http_dav_resource"><code>HTTP::DAV::Resource</code></a> object if required.

749

766

Why? Because each Resource object needs to sit within a global HTTP::DAV client.

750

767

Also, because the new_resource routine checks the <code>HTTP::DAV</code> locked resource

751

768

list before creating a new object.

752

769

<pre>

753

770

$dav->new_resource( -uri => "<a href="http://...&quot">http://...&quot</a>; );</pre>

754

771

</dd>

755

<dt><a name="item_set_workingresource">set_workingresource(URL)</a></dt>

772

<dt><a name="set_workingresource" class="item">set_workingresource(URL)</a></dt>

756

773

757

774

<dd>

758

775

Sets the current working resource to URL.

759

776

You shouldn't need this method. Call open or cwd to set the working resource.

760

You CAN call <a href="#item_set_workingresource"><code>set_workingresource()</code></a> but you will need to perform a

761

<a href="#item_propfind"><code>propfind</code></a> immediately following it to ensure that the working

777

You CAN call <a href="#set_workingresource"><code>set_workingresource()</code></a> but you will need to perform a

778

<a href="#propfind"><code>propfind</code></a> immediately following it to ensure that the working

762

779

resource is valid.

763

780

</dd>

764

781

</dl>

766

783

767

784

<hr />

768

785

<h1><a name="installation__todo__mailing_lists_and_revision_history">INSTALLATION, TODO, MAILING LISTS and REVISION HISTORY</a></h1>

786

[OUTDATED]

769

787

Please see the primary HTTP::DAV webpage at

770

788

(http://www.webdav.org/perldav/http-dav/)

771

789

or the README file in this library.

775

793

776

794

You'll want to also read:

777

795

<dl>

778

<dt><a name="item_http_3a_3adav_3a_3aresponse"><code>HTTP::DAV::Response</code></a></dt>

779

780

<dt><a name="item_http_3a_3adav_3a_3aresource"><code>HTTP::DAV::Resource</code></a></dt>

781

782

796

<dt><a name="http_dav_response" class="item"><code>HTTP::DAV::Response</code></a></dt>

797

798

<dt><a name="http_dav_resource" class="item"><code>HTTP::DAV::Resource</code></a></dt>

799

800

783

801

784

802

</dl>

785

803

and maybe if you're more inquisitive:

786

804

<dl>

787

<dt><a name="item_lwp_3a_3auseragent"><code>LWP::UserAgent</code></a></dt>

788

789

<dt><a name="item_http_3a_3arequest"><code>HTTP::Request</code></a></dt>

790

791

<dt><a name="item_http_3a_3adav_3a_3acomms"><code>HTTP::DAV::Comms</code></a></dt>

792

793

794

795

<dt><a name="item_http_3a_3adav_3a_3aresourcelist"><code>HTTP::DAV::ResourceList</code></a></dt>

796

797

<dt><a name="item_http_3a_3adav_3a_3autils"><code>HTTP::DAV::Utils</code></a></dt>

805

<dt><a name="lwp_useragent" class="item"><code>LWP::UserAgent</code></a></dt>

806

807

<dt><a name="http_request" class="item"><code>HTTP::Request</code></a></dt>

808

809

<dt><a name="http_dav_comms" class="item"><code>HTTP::DAV::Comms</code></a></dt>

810

811

812

813

<dt><a name="http_dav_resourcelist" class="item"><code>HTTP::DAV::ResourceList</code></a></dt>

814

815

<dt><a name="http_dav_utils" class="item"><code>HTTP::DAV::Utils</code></a></dt>

798

816

799

817

</dl>

800

818

810

828

Email: pcollins@cpan.org

811

829

Phone: +61 2 9663 4916</pre>

812

830

813

Current co-maintainer of the module is Opera Software ASA,

814

<a href="mailto:opera@cpan.org">opera@cpan.org</a>.

831

Current co-maintainer of the module is Cosimo Streppone

832

for Opera Software ASA, <a href="mailto:opera@cpan.org">opera@cpan.org</a>.

815

833

You may distribute this module under the terms of either the

816

834

GNU General Public License or the Artistic License,

817

835

as specified in the Perl README file.