[0001]
[0002]
[0003]
[0004]
[0005]
[0006]
[0007]
[0008]
[0009]
[0010]
[0011]
[0012]
[0013]
[0014]
[0015]
[0016]
[0017]
[0018]
[0019]
[0020]
[0021]
[0022]
[0023]
[0024]
[0025]
[0026]
[0027]
[0028]
[0029]
[0030]
[0031]
[0032]
[0033]
[0034]
[0035]
[0036]
[0037]
[0038]
[0039]
[0040]
[0041]
[0042]
[0043]
[0044]
[0045]
[0046]
[0047]

|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.