longer accept requests with PATH INFO. Filters such as INCLUDES (p. 450) or PHP1 are implemented on top of the core handler, and therefore reject requests with PATH INFO. You can use the ACCEPTPATHINFO directive directive was put together with the HEADER directive, since it was a misnomer. Use Header always set foo bar instead to get the desired behaviour. Misc Changes • The module MOD AUTH DIGEST, which was experimental apachectl. You may also directly edit the apachectl script by changing the HTTPD variable near the top to specify the correct location of the httpd binary and any command-line arguments that you wish to

apachectl. You may also directly edit the apachectl script by changing the HTTPD variable near the top to specify the correct location of the httpd binary and any command-line arguments that you wish to are moved to the new directory /bar/, you can instruct clients to request the content at the new location as follows: Redirect permanent /foo/ http://www.example.com/bar/ This will redirect any URL-Path URL-Path starting in /foo/ to the same URL path on the www.example.com server with /bar/ substituted for /foo/. You can redirect clients to any server, not only the origin server. Apache also provides a RedirectMatch

apachectl. You may also directly edit the apachectl script by changing the HTTPD variable near the top to specify the correct location of the httpd binary and any command-line arguments that you wish to are moved to the new directory /bar/, you can instruct clients to request the content at the new location as follows: Redirect permanent /foo/ http://www.example.com/bar/ This will redirect any URL-Path URL-Path starting in /foo/ to the same URL path on the www.example.com server with /bar/ substituted for /foo/. You can redirect clients to any server, not only the origin server. Apache also provides a RedirectMatch

apachectl. You may also directly edit the apachectl script by changing the HTTPD variable near the top to specify the correct location of the httpd binary and any command-line arguments that you wish to are moved to the new directory /bar/, you can instruct clients to request the content at the new location as follows: Redirect permanent /foo/ http://www.example.com/bar/ This will redirect any URL-Path URL-Path starting in /foo/ to the same URL path on the www.example.com server with /bar/ substituted for /foo/. You can redirect clients to any server, not only the origin server. Apache also provides a RedirectMatch

apachectl. You may also directly edit the apachectl script by changing the HTTPD variable near the top to specify the correct location of the httpd binary and any command-line arguments that you wish to are moved to the new directory /bar/, you can instruct clients to request the content at the new location as follows: Redirect permanent /foo/ http://www.example.com/bar/ This will redirect any URL-Path URL-Path starting in /foo/ to the same URL path on the www.example.com server with /bar/ substituted for /foo/. You can redirect clients to any server, not only the origin server. Apache also provides a RedirectMatch

apachectl. You may also directly edit the apachectl script by changing the HTTPD variable near the top to specify the correct location of the httpd binary and any command-line arguments that you wish to directory /bar/, you can instruct clients to request the content at the new location as follows: 2.9. MAPPING URLS TO FILESYSTEM LOCATIONS 53 Redirect permanent /foo/ http://www.example.com/bar/ This will will redirect any URL-Path starting in /foo/ to the same URL path on the www.example.com server with /bar/ substituted for /foo/. You can redirect clients to any server, not only the origin server. Apache

apachectl. You may also directly edit the apachectl script by changing the HTTPD variable near the top to specify the correct location of the httpd binary and any command-line arguments that you wish to are moved to the new directory /bar/, you can instruct clients to request the content at the new location as follows: Redirect permanent /foo/ http://www.example.com/bar/ This will redirect any URL-Path URL-Path starting in /foo/ to the same URL path on the www.example.com server with /bar/ substituted for /foo/. You can redirect clients to any server, not only the origin server. Apache also provides a RedirectMatch

well as on showing you when other solutions are more appropriate. The Rewrite Guide (p. 134) is now a top-level section with much more detail and better organization. mod ssl The MOD SSL documentation has apachectl. You may also directly edit the apachectl script by changing the HTTPD variable near the top to specify the correct location of the httpd binary and any command-line arguments that you wish to be: bar> es on the other hand, are mapped vice-versa: Alias /foo/bar /srv/www/uncommon/bar Alias /foo /srv/www/common/foo The same is true

usage, as well as on showing you when other solutions are more appropriate. The Rewrite Guide is now a top-level section with much more detail and better organization. mod_ssl The mod_ssl documentation has apachectl. You may also directly edit the apachectl script by changing the HTTPD variable near the top to specify the correct location of the httpd binary and any command-line arguments that you wish to bar"> es on the other hand, are mapped vice-versa: Alias "/foo/bar" "/srv/www/uncommon/bar" Alias "/foo" "/srv/www/common/foo" The same

usage, as well as on showing you when other solutions are more appropriate. The Rewrite Guide is now a top-level section with much more detail and better organization. mod_ssl The mod_ssl documentation has apachectl. You may also directly edit the apachectl script by changing the HTTPD variable near the top to specify the correct location of the httpd binary and any command-line arguments that you wish to bar"> es on the other hand, are mapped vice-versa: Alias "/foo/bar" "/srv/www/uncommon/bar" Alias "/foo" "/srv/www/common/foo" The same