|
Lines 68-75
Link Here
|
| 68 |
# be turned off when serving from networked-mounted |
68 |
# be turned off when serving from networked-mounted |
| 69 |
# filesystems or if support for these functions is otherwise |
69 |
# filesystems or if support for these functions is otherwise |
| 70 |
# broken on your system. |
70 |
# broken on your system. |
| 71 |
#EnableMMAP off |
71 |
EnableMMAP On |
| 72 |
#EnableSendfile off |
72 |
EnableSendfile On |
|
|
73 |
|
| 74 |
# FileEtag: Configures the file attributes that are used to create |
| 75 |
# the ETag (entity tag) response header field when the document is |
| 76 |
# based on a static file. (The ETag value is used in cache management |
| 77 |
# to save network bandwidth.) |
| 78 |
FileEtag INode MTime Size |
| 79 |
|
| 80 |
# ContentDigest: This directive enables the generation of Content-MD5 |
| 81 |
# headers as defined in RFC1864 respectively RFC2616. |
| 82 |
# The Content-MD5 header provides an end-to-end message integrity |
| 83 |
# check (MIC) of the entity-body. A proxy or client may check this |
| 84 |
# header for detecting accidental modification of the entity-body |
| 85 |
# in transit. |
| 86 |
# Note that this can cause performance problems on your server since |
| 87 |
# the message digest is computed on every request (the values are |
| 88 |
# not cached). |
| 89 |
# Content-MD5 is only sent for documents served by the core, and not |
| 90 |
# by any module. For example, SSI documents, output from CGI scripts, |
| 91 |
# and byte range responses do not have this header. |
| 92 |
ContentDigest Off |
| 73 |
|
93 |
|
| 74 |
# ErrorLog: The location of the error log file. |
94 |
# ErrorLog: The location of the error log file. |
| 75 |
# If you do not specify an ErrorLog directive within a <VirtualHost> |
95 |
# If you do not specify an ErrorLog directive within a <VirtualHost> |
