|1HTTPd Web Update||

|^ The |*Upd||ate facility allows Web documents and file
environments to be administered from a standard browser.  This capability is
available to Web administrator and user alike.  Availability and capability
depends on the authorization environment within the server.

|^ It |*should be stressed|| that this is not designed as a full
hypertext administration or authoring tool, and for document preparation
relies on the editing capabilities of the <TEXTAREA> widget of the
user's browser. It does however, allow |*ad-hoc changes|| to be
made to documents fairly easily, as well as allowing documents to be deleted,
and directories to be created and deleted.

|^ Consult the 
|link%|https://wasd.kicks-ass.net/httpd/-/updhelp.html|\
Current UPDate documentation| for usage detail.

|^ Here is |link%|/upd/wasd_root/|an example of the interface| (access may be
denied).

|image%%|./update.png|

|image%%|./edit.png|

|0Update Access Permission||

|^ If SSL is in use (see |link|Transport Layer Security||) then
username/password privacy of the authorization environment is inherently
secured via the encrypted communications. To restrict web update functionality
to this secure environment add the following to the WASD_CONFIG_MAP
configuration file:

|code|
/upd/*  "403 Access denied."  ![sc:https]
|!code|

|^ Of course, the user must have write (POST/PUT) access to the document or
area on the server (i.e. the |/path||) and the server account have file
system permission to write into the |_parent directory||.

|^ The server will report "Insufficient privilege or object protection
violation ... /path/document" if it does not have file system permission to
write into a directory.

|^ Also see |link|Controlling Server Write Access|| for information on write
access control for the server account.