? my $ctx = $main::context; ? $_mt->wrapper_file("wrapper.mt", "Configure", "File Directives")->(sub {
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.
The directive accepts a mapping containing configuration directives that can be used at the extension
level, together with a property named extension
specifying a extension (starting with .
) or a sequence of extensions to which the directives should be applied.
Only one handler must exist within the directives.
file.dirlisting
,
file.file
,
file.index
EOT
)->(sub {
?>
= $ctx->{example}->('Serving files under different paths', <<'EOT')
paths:
"/":
file.dir: /path/to/doc-root
"/icons":
file.dir: /path/to/icons-dir
EOT
?>
? })
$ctx->{directive}->(
name => "file.dirlisting",
levels => [ qw(global host path) ],
default => 'file.dirlisting: OFF',
desc => <<'EOT',
A boolean flag (OFF
, or ON
) specifying whether or not to send the directory listing in case none of the index files exist.
EOT
see_also => render_mt(<file.dir
EOT
)->(sub {});
$ctx->{directive}->(
name => "file.etag",
levels => [ qw(global host path) ],
default => 'file.etag: ON',
desc => <<'EOT',
A boolean flag (OFF
, or ON
) specifying whether or not to send etags.
EOT
)->(sub {});
?>
$ctx->{directive}->(
name => "file.file",
levels => [ qw(path) ],
desc => q{The directive maps a path to a specific file.},
see_also => render_mt(<file.dir
EOT
since => '2.0',
)->(sub {
?>
= $ctx->{example}->('Mapping a path to a specific file', <<'EOT')
paths:
/robots.txt:
file.file: /path/to/robots.txt
EOT
?>
? })
$ctx->{directive}->(
name => "file.index",
levels => [ qw(global host path) ],
default => "file.index: [ 'index.html', 'index.htm', 'index.txt' ]",
desc => q{Specifies the names of the files that should be served when the client sends a request against the directory.},
see_also => render_mt(<file.dir
EOT
)->(sub {
?>
The sequence of filenames are searched from left to right, and the first file that existed is sent to the client.
? }) $ctx->{directive}->( name => "file.mime.addtypes", levels => [ qw(global host path) ], see_also => render_mt(<<'EOT'),compress
,
http2-casper
,
http2-reprioritize-blocking-assets
EOT
desc => q{The directive modifies the MIME mappings by adding the specified MIME type mappings.},
)->(sub {
?>
= $ctx->{example}->('Adding MIME mappings', <<'EOT')
file.mime.addtypes:
"application/javascript": ".js"
"image/jpeg": [ ".jpg", ".jpeg" ]
EOT
?>
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 .css
files to text/css
type, setting is_compressible
flag to ON
and priority
to highest.
Following attributes are recognized.
Attribute | Possible Values | Description |
---|---|---|
is_compressible | ON , OFF | if content is compressible |
priority | highest |
The priority
attribute 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 given highest
priority.
compress
EOT
since => '2.0',
desc => <<'EOT',
A flag indicating how a pre-compressed file should be served.
EOT
)->(sub {
?>
If set to ON
, the handler looks for a file with .br
or .gz
appended 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 named index.html
with Accept-Encoding: gzip
header and if index.html.gz
exists, the .gz
file is sent as a response together with a Content-Encoding: gzip
response header.
If set to OFF
, the handler always serves the file specified by the client.
Starting from version 2.2, gunzip
is also supported.
If set, the handler acts identical to when the value was set to ON
.
In addition, the handler will send an uncompressed response by dynamically decompressing the .gz
file 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.
file.send-compressed
.
EOT
)->(sub {})
?>
? })