Configure > File Directives
This document describes the configuration directives of the file handler - a handler that for serving static files.
Two directives: file.dir and file.file are used to define the mapping.
Other directives modify the behavior of the mappings defined by the two.
- Description:
-
The directive maps extensions to a custom handler (e.g. FastCGI).
The directive accepts a mapping containing configuration directives that can be used at the
extensionlevel, together with a property namedextensionspecifying a extension (starting with.) or a sequence of extensions to which the directives should be applied. Only one handler must exist within the directives.Example. Mapping PHP files to FastCGIfile.custom-handler: extension: .php fastcgi.connect: port: /tmp/fcgi.sock type: unix - Level:
- global, host, path
- Description:
-
The directive specifies the directory under which should be served for the corresponding path.
Example. Serving files under different pathspaths: "/": file.dir: /path/to/doc-root "/icons": file.dir: /path/to/icons-dir - Level:
- path
- See also:
file.dirlisting,file.file,file.index
- Description:
-
A boolean flag (
OFF, orON) specifying whether or not to send the directory listing in case none of the index files exist. - Level:
- global, host, path
- Default:
file.dirlisting: OFF
- See also:
file.dir
- Description:
-
A boolean flag (
OFF, orON) specifying whether or not to send etags. - Level:
- global, host, path
- Default:
file.etag: ON
"file.file"
- Description:
-
The directive maps a path to a specific file.
Example. Mapping a path to a specific filepaths: /robots.txt: file.file: /path/to/robots.txt - Level:
- path
- See also:
file.dir
- Description:
-
Specifies the names of the files that should be served when the client sends a request against the directory.
The sequence of filenames are searched from left to right, and the first file that existed is sent to the client.
- Level:
- global, host, path
- Default:
file.index: [ 'index.html', 'index.htm', 'index.txt' ]
- See also:
file.dir
- Description:
-
The directive modifies the MIME mappings by adding the specified MIME type mappings.
Example. Adding MIME mappingsfile.mime.addtypes: "application/javascript": ".js" "image/jpeg": [ ".jpg", ".jpeg" ]The default mappings is hard-coded in lib/handler/mimemap/defaults.c.h.
It is also possible to set certain attributes for a MIME type. The example below maps
.cssfiles totext/csstype, settingis_compressibleflag toONandpriorityto highest.Example. Setting MIME attributesfile.mime.settypes: "text/css": extensions: [".css"] is_compressible: yes priority: highestFollowing attributes are recognized.
Attribute Possible Values Description is_compressibleON,OFFif content is compressible priorityhighest,normalsend priority of the content The
priorityattribute affects how the HTTP/2 protocol implementation handles the request. For detail, please refer to the HTTP/2 directives listed in the see also section below. By default, mime-types for CSS and JavaScript files are the only ones that are givenhighestpriority. - Level:
- global, host, path
- See also:
compress,http2-casper,http2-reprioritize-blocking-assets
- Description:
-
Removes the MIME mappings for specified extensions supplied as a sequence of extensions.
Example. Removing MIME mappingsfile.mime.removetypes: [ ".jpg", ".jpeg" ] - Level:
- global, host, path
- Description:
-
Sets the default MIME-type that is used when an extension does not exist in the MIME mappings
- Level:
- global, host, path
- Default:
file.mime.setdefaulttype: "application/octet-stream"
- Description:
-
Resets the MIME mappings to given mapping.
Example. Resetting the MIME mappings to minimumfile.mime.settypes: "text/html": [ ".html", ".htm" ] "text/plain": ".txt" - Level:
- global, host, path
"file.send-compressed"
- Description:
-
A flag indicating how a pre-compressed file should be served.
If set to
ON, the handler looks for a file with.bror.gzappended and sends the file, if the client is capable of transparently decoding a brotli or gzip-encoded response. For example, if a client requests a file namedindex.htmlwithAccept-Encoding: gzipheader and ifindex.html.gzexists, the.gzfile is sent as a response together with aContent-Encoding: gzipresponse header.If set to
OFF, the handler always serves the file specified by the client.Starting from version 2.2,
gunzipis also supported. If set, the handler acts identical to when the value was set toON. In addition, the handler will send an uncompressed response by dynamically decompressing the.gzfile if the client and the server failed to agree on using a pre-compressed file as the response and if a non-compressed file was not found. The option is useful when conserving disk space is important; it is possible to remove the uncompressed files in place for gzipped ones. - Level:
- global, host, path
- Default:
file.send-compressed: OFF
- See also:
compress
- Description:
-
Obsoleted in 2.0. Synonym of
file.send-compressed. - Level:
- global, host, path