summaryrefslogtreecommitdiff
path: root/pod/nginx/ngx_http_index_module.pod
blob: 841a709e63ce3a3486a4486ccbefaba613455baa (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
=encoding utf-8

=head1 NAME

ngx_http_index_module - Module ngx_http_index_module




=head1



The C<ngx_http_index_module> module processes requests
ending with the slash character (‘C<E<sol>>’).
Such requests can also be processed by the
L<ngx_http_autoindex_module|ngx_http_autoindex_module>
and
L<ngx_http_random_index_module|ngx_http_random_index_module>
modules.




=head1 Example Configuration




    
    location / {
        index index.$geo.html index.html;
    }






=head1 Directives

=head2 index


B<syntax:> index I<I<C<file>> ...>


B<default:> I<index.html>


B<context:> I<http>


B<context:> I<server>


B<context:> I<location>





Defines files that will be used as an index.
The I<C<file>> name can contain variables.
Files are checked in the specified order.
The last element of the list can be a file with an absolute path.
Example:

    
    index index.$geo.html index.0.html /index.html;







It should be noted that using an index file causes an internal redirect,
and the request can be processed in a different location.
For example, with the following configuration:

    
    location = / {
        index index.html;
    }
    
    location / {
        ...
    }


a “C<E<sol>>” request will actually be processed in the
second location as “C<E<sol>index.html>”.