10/12/22 Other proxies ● HAProxy (in the cloud / openshift for example) ● mod_cluster (httpd dynamic load balancer) ● Undertow proxy (jboss servlet container) ● Ingress (in kubernetes, well Nginx or GCE)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 7 Platform-specific Notes 233 7.1 Platform Specific Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and more stable on non-Unix platforms such as BeOS, OS/2, and Windows. With the introduction of platform-specific multi-processing modules (p. 70) (MPMs) and the Apache Portable Runtime (APR), these platforms on Windows, see Using Apache HTTPd with Microsoft Windows (p. 235) . For other platforms, see the platform (p. 234) documentation. Apache HTTPd uses libtool and autoconf to create a build environment that

and more stable on non-Unix platforms such as BeOS, OS/2, and Windows. With the introduction of platform-specific multi-processing modules (MPMs) and the Apache Portable Runtime (APR), these platforms installation on Windows, see Using Apache HTTPd with Microsoft Windows. For other platforms, see the platform documentation. Apache HTTPd uses libtool and autoconf to create a build environment that looks the source tree The next step is to configure the Apache HTTPd source tree for your particular platform and personal requirements. This is done using the script configure included in the root directory

and more stable on non-Unix platforms such as BeOS, OS/2, and Windows. With the introduction of platform-specific multi-processing modules (MPMs) and the Apache Portable Runtime (APR), these platforms installation on Windows, see Using Apache HTTPd with Microsoft Windows. For other platforms, see the platform documentation. Apache HTTPd uses libtool and autoconf to create a build environment that looks the source tree The next step is to configure the Apache HTTPd source tree for your particular platform and personal requirements. This is done using the script configure included in the root directory

and more stable on non-Unix platforms such as BeOS, OS/2, and Windows. With the introduction of platform-specific multi-processing modules (MPMs) and the Apache Portable Runtime (APR), these platforms installation on Windows, see Using Apache HTTPd with Microsoft Windows. For other platforms, see the platform documentation. Apache HTTPd uses libtool and autoconf to create a build environment that looks the source tree The next step is to configure the Apache HTTPd source tree for your particular platform and personal requirements. This is done using the script configure included in the root directory

and more stable on non-Unix platforms such as BeOS, OS/2, and Windows. With the introduction of platform-specific multi-processing modules (MPMs) and the Apache Portable Runtime (APR), these platforms installation on Windows, see Using Apache HTTPd with Microsoft Windows. For other platforms, see the platform documentation. Apache HTTPd uses libtool and autoconf to create a build environment that looks the source tree The next step is to configure the Apache HTTPd source tree for your particular platform and personal requirements. This is done using the script configure included in the root directory

and more stable on non-Unix platforms such as BeOS, OS/2, and Windows. With the introduction of platform-specific multi-processing modules (MPMs) and the Apache Portable Runtime (APR), these platforms installation on Windows, see Using Apache HTTPd with Microsoft Windows. For other platforms, see the platform documentation. Apache HTTPd uses libtool and autoconf to create a build environment that looks the source tree The next step is to configure the Apache HTTPd source tree for your particular platform and personal requirements. This is done using the script configure included in the root directory

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 CONTENTS v 7 Platform-specific Notes 245 7.1 Platform Specific Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LBMETHOD BYBUSYNESS. You might need to build and load any of these that your configuration uses. • Platform support has been removed for BeOS, TPF, and even older platforms such as A/UX, Next, and Tandem Advanced authorization logic may now be specified using the REQUIRE directive and the related container directives, such as . MOD REWRITE MOD REWRITE adds the [QSD] (Query String Discard)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 CONTENTS v 7 Platform-specific Notes 245 7.1 Platform Specific Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LBMETHOD BYBUSYNESS. You might need to build and load any of these that your configuration uses. • Platform support has been removed for BeOS, TPF, and even older platforms such as A/UX, Next, and Tandem Advanced authorization logic may now be specified using the REQUIRE directive and the related container directives, such as . MOD REWRITE MOD REWRITE adds the [QSD] (Query String Discard)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 CONTENTS v 7 Platform-specific Notes 267 7.1 Platform Specific Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LBMETHOD BYBUSYNESS. You might need to build and load any of these that your configuration uses. • Platform support has been removed for BeOS, TPF, and even older platforms such as A/UX, Next, and Tandem Advanced authorization logic may now be specified using the REQUIRE directive and the related container directives, such as . MOD REWRITE MOD REWRITE adds the [QSD] (Query String Discard)