Zeta Components - high quality PHP components

1.  $server = ezcWebdavServer::getInstance();
2.  
3.  // Optionally register aditional transport handlers
4.  
5.  // This step is only required, if you want to add custom or third party extensions
6.  // implementations for special clients.
7.  // Create a new configuration set for the client
8.  $newClientConf = new ezcWebdavServerConfiguration(
9.      // Regular expression to match client name
10.      '(My.*Webdav\s+Cliengt)i',
11.      // Class name of transport handler, extending <a href="ezcWebdavTransport.html">ezcWebdavTransport</a>
12.      'myCustomTransportTransport'
13.      // There are more settings you can provide, see //.
14.  );
15.  // Append the configuration at front, because the last configuration is a
16.  // catch all for misc clients.
17.  $server->configurations->insertBefore( $newClientConf, 0 );
18.  
19.  // If you want to use a different path factory globally, you need to replace
20.  // it in every configuration.
21.  $myPathFactory = new ezcWebdavBasicPathFactory( 'http://webdav.server/base/path' );
22.  foreach ( $server->configuration as $config )
23.  {
24.      $config->pathFactory = $myPathFactory;
25.  }
26.  
27.  // Serve data using file backend with data in the local directory "/path"
28.  // Make sure this directory is read and writable for your server and that
29.  // the umask is set accordingly in the server settings, if you want to
30.  // access the files as a different user, too.
31.  $backend = new ezcWebdavBackendFile( '/path' );
32.  
33.  // Make the server serve WebDAV requests
34.  $server->handle( $backend );

The instantiation of 2 WebDAV servers at the same time does not make sense and could possibly cause strange effects, like double sending of a response. Therefore the server implements a singleton and its only instance must be retrieved using this method. Configuration changes can then be performed through the properties of this instance.

The constructor is protected due to singleton reasons. Use getInstance() and then use the properties of the server to adjust its configuration.

Creates a ezcWebdavErrorResponse object with status code ezcWebdavResponse::STATUS_401 and a corresponding WWW-Authenticate header using the $realm define in ezcWebdavServerOptions. The $uri and $desc parameters are used to create the error response.

Creates a ezcWebdavErrorResponse object with status code ezcWebdavResponse::STATUS_403. The $uri and $desc parameters are used to create the error response.

This method is the absolute heart of the Webdav component. It is called to make the server instance handle the current request. This means, a ezcWebdavTransport is selected and instantiated through the ezcWebdavServerConfigurationManager in $configurations. This transport (and all other objects, created from the configuration) is used to parse the incoming request into an instance of ezcWebdavRequest, which is then handed to the submitted $backend for handling. The resulting ezcWebdavResponse is serialized by the ezcWebdavTransport and send back to the client.

The method receives at least an instance of ezcWebdavBackend, which is used to server the request. Optionally, the request URI can be submitted in $uri. If this is not the case, the request URI is determined by the server variables

• $_SERVER['SERVER_NAME']
• $_SERVER['REQUEST_URI']

This method is marked proteced, because it is intended to be used by by ezcWebdavServerConfiguration instances and instances of derived classes, but not directly.

This method does several things:

• Check if authorization is enabled by ezcWebdavServer->$auth
• If it is, extract username from Authenticate header or choose ''
• Check authorization

Resets the internal server state as if a new instance has just been constructed.