CacheFile and MMapFile, the explanations in this guide cover the mod_cache caching architecture. To get the most from this document, you should be familiar with the basics of HTTP, and have read the Users' response must have a HTTP status code of 200, 203, 300, 301 or 410. 3. The request must be a HTTP GET request. 4. If the request contains an "Authorization:" header, the response will not be cached. option in the "Cache- Control:" header. 6. If the URL included a query string (e.g. from a HTML form GET method) it will not be cached unless the response specifies an explicit expiration by including an

CacheFile and MMapFile, the explanations in this guide cover the mod_cache caching architecture. To get the most from this document, you should be familiar with the basics of HTTP, and have read the Users' response must have a HTTP status code of 200, 203, 300, 301 or 410. 3. The request must be a HTTP GET request. 4. If the request contains an "Authorization:" header, the response will not be cached. option in the "Cache- Control:" header. 6. If the URL included a query string (e.g. from a HTML form GET method) it will not be cached unless the response specifies an explicit expiration by including an

CacheFile and MMapFile, the explanations in this guide cover the mod_cache caching architecture. To get the most from this document, you should be familiar with the basics of HTTP, and have read the Users' response must have a HTTP status code of 200, 203, 300, 301 or 410. 3. The request must be a HTTP GET request. 4. If the request contains an "Authorization:" header, the response will not be cached. option in the "Cache- Control:" header. 6. If the URL included a query string (e.g. from a HTML form GET method) it will not be cached unless the response specifies an explicit expiration by including an

CacheFile and MMapFile, the explanations in this guide cover the mod_cache caching architecture. To get the most from this document, you should be familiar with the basics of HTTP, and have read the Users' response must have a HTTP status code of 200, 203, 300, 301 or 410. 3. The request must be a HTTP GET request. 4. If the request contains an "Authorization:" header, the response will not be cached. option in the "Cache- Control:" header. 6. If the URL included a query string (e.g. from a HTML form GET method) it will not be cached unless the response specifies an explicit expiration by including an

CacheFile and MMapFile, the explanations in this guide cover the mod_cache caching architecture. To get the most from this document, you should be familiar with the basics of HTTP, and have read the Users' response must have a HTTP status code of 200, 203, 300, 301 or 410. 3. The request must be a HTTP GET request. 4. If the request contains an "Authorization:" header, the response will not be cached. option in the "Cache- Control:" header. 6. If the URL included a query string (e.g. from a HTML form GET method) it will not be cached unless the response specifies an explicit expiration by including an

configurations containing only old directives to facilitate the 2.4 upgrade. Please check the examples below to get a better idea about issues that might arise. Here are some examples of old and new ways to do the SetHandler server-status Require 127.0.0.1 access.log - GET /server-status 403 127.0.0.1 error.log - AH01797: client denied by server configuration: /var/www/html/server-status server-status Order deny,allow Deny from all Allow From 127.0.0.1 access.log - GET /server-status 200 127.0.0.1 So even if mixing configuration is still possible, please try to avoid

configurations containing only old directives to facilitate the 2.4 upgrade. Please check the examples below to get a better idea about issues that might arise. Here are some examples of old and new ways to do the SetHandler server-status Require 127.0.0.1 access.log - GET /server-status 403 127.0.0.1 error.log - AH01797: client denied by server configuration: /var/www/html/server-status server-status Order deny,allow Deny from all Allow From 127.0.0.1 access.log - GET /server-status 200 127.0.0.1 So even if mixing configuration is still possible, please try to avoid

files on disk. rotatelogs May now create a link to the current log file. May now invoke a custom post-rotate script. htpasswd, htdbm Support for the bcrypt algorithm (available in 2.4.4 and later). there are no errors in the configuration files. If your configuration file has errors in it, you will get an error message about that syntax error, and the server will refuse to restart. This avoids the situation file handles on files that are accessed often, as there is no need to go to disk on each request. To get the most from this document, you should be familiar with the basics of HTTP, and have read the Users'

files on disk. rotatelogs May now create a link to the current log file. May now invoke a custom post-rotate script. htpasswd, htdbm Support for the bcrypt algorithm (available in 2.4.4 and later). there are no errors in the configuration files. If your configuration file has errors in it, you will get an error message about that syntax error, and the server will refuse to restart. This avoids the situation file handles on files that are accessed often, as there is no need to go to disk on each request. To get the most from this document, you should be familiar with the basics of HTTP, and have read the Users'

files on disk. rotatelogs May now create a link to the current log file. May now invoke a custom post-rotate script. Documentation mod_rewrite The mod_rewrite documentation has been rearranged and there are no errors in the configuration files. If your configuration file has errors in it, you will get an error message about that syntax error, and the server will refuse to restart. This avoids the situation file handles on files that are accessed often, as there is no need to go to disk on each request. To get the most from this document, you should be familiar with the basics of HTTP, and have read the Users'