Managing the HTTP server that is built into Data ONTAP involves several tasks.
More information
Enabling or disabling the Data ONTAP HTTP server
You can use the httpd.enable option to enable or disable the HTTP server that is built into Data ONTAP. By default, this option is off. When this option is enabled, web browsers can access all of the files in the HTTP server's root directory.
Enabling or disabling the bypassing of HTTP traverse checking
You can enable or disable the bypassing of HTTP traverse checking by setting the httpd.bypass_traverse_checking option to on or off, respectively. By default, this option is set to off.
Specifying the root directory for the Data ONTAP HTTP server
You can set the httpd.rootdir option to specify the root directory for the HTTP server that is built into Data ONTAP. This is the directory that contains all of the files that an HTTP client can access.
Specifying the maximum size of the log file for the Data ONTAP HTTP server
You can set the ftpd.log.filesize option to specify the maximum size of the log file for the HTTP server that is built into Data ONTAP. This option specifies the maximum log file size of the HTTP and FTP log files in the /etc/log directory, including the ftp.cmd, ftp.xfer, and httpd.log files. By default, this option is set to 512 kilobytes.
Testing the Data ONTAP HTTP server
To confirm that the HTTP server that is built into Data ONTAP is working, you can copy an HTML file into the HTTP server's root directory and then access the file from a web browser. You can also access the HTTP server's root directory (or a subdirectory of the HTTP server's root directory) directly from a web browser.
Specifying how the Data ONTAP HTTP server maps MIME content types to file name extensions
You can create or edit the /etc/httpd.mimetypes file to specify how the HTTP server that is built into Data ONTAP maps Multipurpose Internet Mail Extensions (MIME) content types to file name extensions. If the /etc/httpd.mimetypes file does not exist, the HTTP server uses the mappings in the /etc/httpd.mimetypes.sample file. For more information, see the na_httpd.mimetypes(5) man page.
Specifying how the Data ONTAP HTTP server translates HTTP requests
You can add map, redirect, pass, or fail translation rules to the /etc/httpd.translations configuration file. This allows you to specify how the HTTP server that is built into Data ONTAP responds to HTTP requests.
Configuring MIME Content-Type values
You can configure the storage system to send the appropriate MIME (Multipurpose Internet Mail Extensions) Content-Type value in each response to a get request from a client by mapping the file name suffix, for example, .gif, .html, or .mpg, according to information in the /etc/httpd.mimetypes file.
Maintaining security for the Data ONTAP HTTP server
You can maintain security for the HTTP server that is built into Data ONTAP by using the HTTP options to restrict access, using an HTTP virtual firewall, protecting web pages with user authentication, disabling support for the HTTP TRACE method, and specifying how long Data ONTAP keeps idle HTTP connections open.
Displaying HTTP server statistics
You can use the httpstat command to display five types of statistics about operations of the HTTP server that is built into Data ONTAP.
Viewing HTTP server connection information
You can view many types of information in the /etc/log/httpd.log file for each connection established by the HTTP server that is built into Data ONTAP.