If the method succeeds, the return value is non-zero. If the
command is not recognized, the method will return zero. If the
method fails, the GetLastError method will return more
information about the last error that has occurred.
The DisableCommand method is used to disable access to a
specific command on the server, typically for security purposes. For
example, the PUT command can be disabled, preventing any client from
attempting to upload files directly to the server. The
IsCommandEnabled method can be used to determine if a
command is enabled or not.
The command name provided to this method must match the commands
defined in RFC 2616 or related protocol standards. Refer to
Hypertext Transfer Protocol
Commands for a complete list of server commands.
Some commands cannot be disabled because they are required to
perform essential server functions. For example, the GET and HEAD
commands cannot be disabled. If you attempt to disable a required
command, this method will return zero and the last error code will
be set to ST_ERROR_COMMAND_REQUIRED. Because this method affects
all clients connected to the server, it should not be used to limit
access to certain commands for specific clients. Instead, use an
event handler to filter the commands.
The OPTIONS and TRACE commands are disabled by default for all
server instances and must be explicitly enabled using the
EnableCommand method if you wish permit clients to use them. It is
not recommended that you enable these commands if your server is going
to be publicly accessible over the Internet. If the server started
with the option HTTP_SERVER_READONLY, commands that can be used to
create or modify files on the server will be disabled by default.