HTTP Methods Usage

WASD Hypertext Services - Technical Overview

[next] [previous][contents]

3 - HTTP Methods Usage

This section primarily describes server-specific characteristics of the POST and PUT methods. Kludges support the creation of directories, and deletion of files and directories.

3.1 - GET Method

Of course, the GET method is used to access documents supplied by the server. There is nothing WASD server-specific about this method.

3.2 - POST, PUT Methods

The WASD HTTPd does not differentiate between POST and PUT methods, both are handled identically.

In environments where authentication and authorization are enabled these methods can be used to upload data to both CGI scripts and the server. The handling of POST and PUT by scripts is script-specific, see 9 - HTTPd Scripting.

3.2.1 - File Creation/Upload

The WASD HTTPd itself will accept POST and PUT data, creating a file corresponding to the specified path. The data stream may be text or binary.

Processing is according to MIME content type:

3.2.2 - Directory Creation

A directory will be created by the HTTPd if a directory path is provided with the POST or PUT methods. For example:

  /dir1/dir2/dir-to-be-created/

3.2.3 - File Deletion

A file will be deleted by the HTTPd if the file path ending with a wildard version specification is provided with the POST or PUT methods. For example:

  /dir1/dir2/file-to-be.deleted;*

3.2.4 - Directory Deletion

A directory will be deleted by the HTTPd if a directory path ending with a wildard version specification is provided with the POST or PUT methods. For example:

  /dir1/dir2/dir-to-be-deleted/;*

3.3 - DELETE Method

The DELETE method should delete the file or directory corresponding to the supplied path.


[next] [previous][contents]