Oracle B12255-01 Manuale Utente
9-4
Oracle HTTP Server Administrator’s Guide
Supporting PHP
mod_php
is not supported, however, you have the following two options:
■
Install mod_php by yourself and use it. If there is a support question on any
aspect of Oracle HTTP Server, you might be asked to reproduce the problem
without mod_php.
aspect of Oracle HTTP Server, you might be asked to reproduce the problem
without mod_php.
■
Use PHP in a CGI mode, in which case support of the rest of the Oracle HTTP
Server stack would not be an issue.
Server stack would not be an issue.
Creating Application Name Space that Works Across Firewalls and Clusters
The general idea is that all servers in a distributed Web site should agree on a single
URL namespace. Every server serves some part of that namespace, and is able to
redirect or proxy requests for URLs that it does not serve to a server that is “closer”
to that URL. For example, your namespaces could be the following:
URL namespace. Every server serves some part of that namespace, and is able to
redirect or proxy requests for URLs that it does not serve to a server that is “closer”
to that URL. For example, your namespaces could be the following:
/app1/login.html
/app1/catalog.html
/app1/dologin.jsp
/app2/orderForm.html
/apps/placeOrder.jsp
We could initially map this namespace to two Web servers by putting app1 on
server1 and app2 on server2. Server1’s configuration might look like the following:
server1 and app2 on server2. Server1’s configuration might look like the following:
Redirect permanent /app2 http://server2/app2
Alias /app1 /myApps/application1
<Directory /myApps/application1>
...
</Directory>
Server2’s configuration is complementary. If you decide to partition the namespace
by content type (HTML on server, JSP on server2), change server configuration and
move files around, but do not have to make changes to the application itself. The
resulting configuration of server1 might look like the following:
by content type (HTML on server, JSP on server2), change server configuration and
move files around, but do not have to make changes to the application itself. The
resulting configuration of server1 might look like the following:
RedirectMatch permanent (.*) \.jsp$ http://server2/$1.jsp
AliasMatch ^/app(.*) \.html$ /myPages/application$1.html
<DirectoryMatch "^/myPages/application\d">
...
</DirectoryMatch>
Note that the amount of actual redirection can be minimized by configuring a
hardware load balancer to send requests to server1 or server2 based on the URL.
hardware load balancer to send requests to server1 or server2 based on the URL.