1. Administering Oracle HTTP Server
  2. Configuring mod_proxy_fcgi and mod_authnz_fcgi Modules

B Configuring mod_proxy_fcgi and mod_authnz_fcgi Modules

The mod_proxy_fcgi module uses mod_proxy to provide FastCGI support. The mod_authnz_fcgi module allows FastCGI authorizer applications to authenticate users and authorize access to resources.

Complete the following tasks to migrate from the mod_fastcgi module to the mod_proxy_fcgi and mod_authnz_fcgi modules:

  • Configure mod_proxy_fcgi to Act as a Reverse Proxy to an External FastCGI Server
    The mod_proxy_fcgi module does not have configuration directives. Instead, it uses the directives set on the mod_proxy module. Unlike the mod_fcgid and mod_fastcgi modules, the mod_proxy_fcgi module has no provision for starting the application process. The purpose of mod_proxy_fcgi is to move this functionality outside of the web server for faster performance. So, mod_proxy_fcgi simply will act as a reverse proxy to an external FastCGI server.
  • Setup an External FastCGI Server
    An external FastCGI server enables you to run FastCGI scripts external to the web server or even on a remote machine. Therefore, you must set up an external FastCGI server.
  • Setup mod_authnz_fcgi to Work with FastCGI Authorizer Applications
    You can set up mod_authnz_fcgi module to work with FastCGI authorizer applications to authenticate users and authorize access to resources. It supports generic FastCGI authorizers that participate in a single phase for authentication and authorization, and Apache httpd specific authenticators and authorizers. FastCGI authorizers can authenticate using the user ID and password for basic authentication or authenticate using arbitrary mechanisms.

Configure mod_proxy_fcgi to Act as a Reverse Proxy to an External FastCGI Server

The mod_proxy_fcgi module does not have configuration directives. Instead, it uses the directives set on the mod_proxy module. Unlike the mod_fcgid and mod_fastcgi modules, the mod_proxy_fcgi module has no provision for starting the application process. The purpose of mod_proxy_fcgi is to move this functionality outside of the web server for faster performance. So, mod_proxy_fcgi simply will act as a reverse proxy to an external FastCGI server.

For examples of using mod_proxy_fcgi, see:

http://httpd.apache.org/docs/trunk/mod/mod_proxy_fcgi.html

For information about the directives available for mod_proxy, including reverse proxy examples, see:

http://httpd.apache.org/docs/trunk/mod/mod_proxy.html

Another way to setup the mod_proxy_fcgi module to act as a reverse proxy to a FastCGI server is to force a request to be handled as a reverse-proxy request. To do this, you must create a suitable Handler pass-through (also known as Access via Handler). For more information about how to set up a Handler pass-through, see:

http://httpd.apache.org/docs/trunk/mod/mod_proxy.html#handler

Parent topic: Configuring mod_proxy_fcgi and mod_authnz_fcgi Modules

Setup an External FastCGI Server

An external FastCGI server enables you to run FastCGI scripts external to the web server or even on a remote machine. Therefore, you must set up an external FastCGI server.

The following list provides information on some available FastCGI server solutions:

Parent topic: Configuring mod_proxy_fcgi and mod_authnz_fcgi Modules

Setup mod_authnz_fcgi to Work with FastCGI Authorizer Applications

You can set up mod_authnz_fcgi module to work with FastCGI authorizer applications to authenticate users and authorize access to resources. It supports generic FastCGI authorizers that participate in a single phase for authentication and authorization, and Apache httpd specific authenticators and authorizers. FastCGI authorizers can authenticate using the user ID and password for basic authentication or authenticate using arbitrary mechanisms.

For more information about using mod_authnz_fcgi, see http://httpd.apache.org/docs/trunk/mod/mod_authnz_fcgi.html.

Parent topic: Configuring mod_proxy_fcgi and mod_authnz_fcgi Modules