to log errors that occur with the client's connection. When logged, the message includes the client IP address. Test Configuration Hook Added A new hook, test_config has been added to aid modules that The often confusing Port and BindAddress directives are gone; only the Listen directive is used for IP address binding; the ServerName directive specifies the server name and port number only for redirection HTTP negotiation, should not be cached. If you have dynamic content which changes depending on the IP address of the requester, or changes every 5 minutes, it should almost certainly not be cached. If

to log errors that occur with the client's connection. When logged, the message includes the client IP address. Test Configuration Hook Added A new hook, test_config has been added to aid modules that The often confusing Port and BindAddress directives are gone; only the Listen directive is used for IP address binding; the ServerName directive specifies the server name and port number only for redirection HTTP negotiation, should not be cached. If you have dynamic content which changes depending on the IP address of the requester, or changes every 5 minutes, it should almost certainly not be cached. If

to log errors that occur with the client's connection. When logged, the message includes the client IP address. Test Configuration Hook Added A new hook, test_config has been added to aid modules that The often confusing Port and BindAddress directives are gone; only the Listen directive is used for IP address binding; the ServerName directive specifies the server name and port number only for redirection HTTP negotiation, should not be cached. If you have dynamic content which changes depending on the IP address of the requester, or changes every 5 minutes, it should almost certainly not be cached. If

to log errors that occur with the client's connection. When logged, the message includes the client IP address. Test Configuration Hook Added A new hook, test_config has been added to aid modules that The often confusing Port and BindAddress directives are gone; only the Listen directive is used for IP address binding; the ServerName directive specifies the server name and port number only for redirection HTTP negotiation, should not be cached. If you have dynamic content which changes depending on the IP address of the requester, or changes every 5 minutes, it should almost certainly not be cached. If

Virtual Host Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 3.3 Apache IP-based Virtual Host Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 3.4 for use with RewriteMap . . . . . . . . . . . . . . . . . . . . . . 296 8.13 logresolve - Resolve IP-addresses to hostnames in Apache log files . . . . . . . . . . . . . . . . . 297 8.14 rotatelogs - to log errors that occur with the client’s connection. When logged, the message includes the client IP address. Test Configuration Hook Added A new hook, test config has been added to aid modules that

to log errors that occur with the client's connection. When logged, the message includes the client IP address. Test Configuration Hook Added A new hook, test_config has been added to aid modules that The often confusing Port and BindAddress directives are gone; only the Listen directive is used for IP address binding; the ServerName directive specifies the server name and port number only for redirection HTTP negotiation, should not be cached. If you have dynamic content which changes depending on the IP address of the requester, or changes every 5 minutes, it should almost certainly not be cached. If

.. in place of Require group .... Access control In 2.2, access control based on client hostname, IP address, and other characteristics of client requests was done using the directives Order, Allow, Deny AuthUserFile /example.com/conf/users.passwd AuthName secure Require valid-user Require ip 127.0.0.1 In configurations where both authentication and access control were meaningfully /example.com/conf/users.passwd AuthName secure # Implicitly Require valid-user Require ip 127.0.0.1 Other configuration changes Some other small adjustments may be necessary for particular

.. in place of Require group .... Access control In 2.2, access control based on client hostname, IP address, and other characteristics of client requests was done using the directives Order, Allow, Deny AuthUserFile /example.com/conf/users.passwd AuthName secure Require valid-user Require ip 127.0.0.1 In configurations where both authentication and access control were meaningfully /example.com/conf/users.passwd AuthName secure # Implicitly Require valid-user Require ip 127.0.0.1 Other configuration changes Some other small adjustments may be necessary for particular

Host Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 3.3 Apache IP-based Virtual Host Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 3.4 for use with RewriteMap . . . . . . . . . . . . . . . . . . . . . . 333 8.14 logresolve - Resolve IP-addresses to hostnames in Apache log files . . . . . . . . . . . . . . . . . 334 8.15 log server status . in place of Require group .... Access control In 2.2, access control based on client hostname, IP address, and other characteristics of client requests was done using the directives ORDER, ALLOW, DENY

Host Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 3.3 Apache IP-based Virtual Host Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 3.4 for use with RewriteMap . . . . . . . . . . . . . . . . . . . . . . 333 8.14 logresolve - Resolve IP-addresses to hostnames in Apache log files . . . . . . . . . . . . . . . . . 334 8.15 log server status . in place of Require group .... Access control In 2.2, access control based on client hostname, IP address, and other characteristics of client requests was done using the directives ORDER, ALLOW, DENY