Apache 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648 11.8 How filters work in Apache 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652 12 Glossary were made to the server API in Apache 2.0. Existing modules designed for the Apache 1.3 API will not work in Apache 2.0 without modification. Details are provided in the developer documentation (p. 620) types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example

| Glossary | Sitemap Third Party Modules Many third-party modules designed for version 2.0 will work unchanged with the Apache HTTP Server version 2.2. But all modules must be recompiled before being types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations

| Glossary | Sitemap Third Party Modules Many third-party modules designed for version 2.0 will work unchanged with the Apache HTTP Server version 2.2. But all modules must be recompiled before being types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations

| Glossary | Sitemap Third Party Modules Many third-party modules designed for version 2.0 will work unchanged with the Apache HTTP Server version 2.2. But all modules must be recompiled before being types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations

| Glossary | Sitemap Third Party Modules Many third-party modules designed for version 2.0 will work unchanged with the Apache HTTP Server version 2.2. But all modules must be recompiled before being types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations

the Apache HTTP Server 2.x . . . . . . . . . . . . . . . . . . . . . . . . . 764 11.8 How filters work in Apache 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768 11.9 Apache now a standard module. Third Party Modules Many third-party modules designed for version 2.0 will work unchanged with the Apache HTTP Server version 2.2. But all modules must be recompiled before being MOD AUTHNZ LDAP This module is a port of the 2.0 mod auth ldap module to the 2.2 Authn/Authz frame- work. New features include using LDAP attribute values and complicated search filters in the REQUIRE direc-

| Glossary | Sitemap Third Party Modules Many third-party modules designed for version 2.0 will work unchanged with the Apache HTTP Server version 2.2. But all modules must be recompiled before being types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations

(ASF) under one or more contributor license agreements. See the NO- TICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache HTTP Server 2.x . . . . . . . . . . . . . . . . . . . . . . . . . 974 11.9 How filters work in Apache 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977 11.10 Guide compression is larger than the data to be compressed. • Multi-language error documents from 2.2.x may not work unless they are adjusted to the new syntax of MOD INCLUDE’s #if expr= element or the directive SSILEGACYEXPRPARSER

(ASF) under one or more contributor license agreements. See the NO- TICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache HTTP Server 2.x . . . . . . . . . . . . . . . . . . . . . . . . . 974 11.9 How filters work in Apache 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977 11.10 Guide compression is larger than the data to be compressed. • Multi-language error documents from 2.2.x may not work unless they are adjusted to the new syntax of MOD INCLUDE’s #if expr= element or the directive SSILEGACYEXPRPARSER

compression is larger than the data to be compressed. Multi-language error documents from 2.2.x may not work unless they are adjusted to the new syntax of mod_include's #if expr= element or the directive SSILegacyExprParser recompiled for 2.4 before being loaded. Many third-party modules designed for version 2.2 will otherwise work unchanged with the Apache HTTP Server version 2.4. Some will require changes; see the API update overview underscores) are now silently dropped. Environment Variables in Apache has some pointers on how to work around broken legacy clients which require such headers. (This affects all modules which use these