Under Apache HTTP Server 1.3, for example, a Perl script would be handled in its entirety bythe Perl module (mod_perl). Under Apache HTTP Server 2.0, the request is initially handled bythe core module — which serves static files — and is then filtered by mod_perl.Exactly how to use this, and all other new features of Apache HTTP Server 2.0, is beyond thescope of this document; however, the change has ramifications if the PATH_INFO directive isused for a document which is handled by a module that is now implemented as a filter, as eachcontains trailing path information after the true file name. The core module, which initiallyhandles the request, does not by default understand PATH_INFO and returns 404 Not Founderrors for requests that contain such information. As an alternative, use the AcceptPathInfodirective to coerce the core module into accepting requests with PATH_INFO.The following is an example of this directive:AcceptPathInfo onFor more on this topic, refer to the following documentation on the Apache SoftwareFoundation's website:• http://httpd.apache.org/docs-2.0/mod/core.html#acceptpathinfo• http://httpd.apache.org/docs-2.0/handler.html• http://httpd.apache.org/docs-2.0/filter.html2.4.1. The suexec ModuleIn Apache HTTP Server 2.0, the mod_suexec module uses the SuexecUserGroup directive,rather than the User and Group directives, which is used for configuring virtual hosts. The Userand Group directives can still be used in general, but are deprecated for configuring virtualhosts.For example, the following is a sample Apache HTTP Server 1.3 directive: User someone Group somegroupTo migrate this setting to Apache HTTP Server 2.0, use the following structure: SuexecUserGroup someone somegroup2.4.2. The mod_ssl ModuleThe configuration for mod_ssl has been moved from the httpd.conf file into theChapter 10. Apache HTTP Server156
