In a deployment scenario on Mac OS X, Linux, Solaris or even Windows, your applications will most likely use Apache to server static resources. Additionally, if you develop with WODirectConnectEnabled=false (you should, see the Direct Connect section for details), you will be running your application locally through Apache as well. Apache is a very extensible web server that provides a huge number of capabilities, some of which we will detail here.
WebObjects applications are deployed in a "split install". A split install means that your application code, components, and resources are deployed in one location to be served from your WebObjects application (on OS X,
.woa), while your
WebServerResources are installed in another location (on OS X,
.woa/Contents/WebServerResources) to be served directly by Apache. This provides the optimal performance scenario, as Apache is specifically tuned for serving static content, and it does not make sense to send requests for large binary files through WebObjects if it is not necessary.
To get the most performance out of Apache, you should make sure that you have mod_expires enabled. mod_expires controls the caching headers that are applied to static resource requests. Depending on your installation, Apache may default to mod_expires disabled, which would cause your end-users' browser to re-request every resource on your site on every page, even if it's a common header graphic.
An example mod_expires configuration might look like:
You will also need the corresponding type-extension mappings:
This tells Apache that when a request is made for a type image/gif, the requesting browser will be told not to request the image again for an hour (A3600 = 3600 seconds).
Anyone who has used WebObjects has likely noticed that WebObjects URLs are long
http://yoursite.com/cgi-bin/WebObjects/AppName.woa/wa/something. It is a common request to make these URLs nicer for end-users who are used to just requesting
http://yoursite.com. Fortunately Apache provides an amazingly extensive module called "mod_rewrite" that allows you to rewrite the URL requests of your site based on a series of regular expressions and rules.
mod_rewrite with mod_webobjects
I ran into a problem with mod_rewrite when using mod_WebObjects where mod_WebObjects had be loaded first or it just wouldn't work properly (it would work fine with cgi-bin adaptor).
So in http.conf, search for mod_rewrite and change it to:
, find again:
There's still a load module in /System/Library/WebObjects/Adaptors/Apache/apache.conf, but you can just ignore it - it produces a warning about being loaded twice.
Here's an example mod_rewrite we use on one of our apps:
The WOA produces URLs in the format
http://site.com/page/HomePage?appNum=2, which turns into
This one stumped me for a couple days, so thought I'd add it. Was trying to add mod_rewrite functionality as described above, and things went well on my dev machine by adding the rewrite rules just to the /etc/apache2/httpd.conf file. However, on the deployment machine I also had to add them to the /etc/apache2/sites/0000_any_.conf file.
WebObjects Adaptor for Apache 2.2
A number of people have expressed interest in using the WebObjects adaptor with Apache 2.2.x. I finally gotten a chance to sit down and work on it today. I'm writing to let you know that it's available in the Project Wonder CVS repository. (also there are precompiled binaries for various OS available)
The necessary changes turned out to be mostly minor updates to change calls to outdated/deprecated functions. The biggest (and non-trivial) change was for SSL support. It's been re-written to use Apache's mod_ssl module.
I've tested with MacOS X 10.4.7, Apache 2.2.2, with and without ssl support. It works in all of my tests.
Configuration of the web server to work with the adaptor turned out to be surprisingly challenging, due to the new, very strict default access rules that ship in Apache 2.2.x httpd.conf file. Once I discovered that, it was trivial to change the setting, but it's worth mentioning here to save some people a lot of frustration.
The new default configuration is:
Your options are to comment out the last 2 lines of that block, or to override them in a VirtualHost block. Just setting the usual Location block didn't seem to work for me.
And, of course, either change the name of the WebObjectsAlias setting from /cgi-bin/WebObjects to <foo>/WebObjects or comment out the ScriptAlias definition for the /cgi-bin/ directory.
ScriptAlias directive in the 10.5 and 10.6
httpd.conf files is:
/cgi-bin/WebObjects from matching, so no change to
ScriptAlias is necessary.
Other than these tips, it's pretty much the standard compilation and installation, and configuration.
- Alter the make.config file in the Adaptors directory of the Wonder repository to reflect your apache installation setup.*
- Run make to build the Adaptor
- Curse because of that one setting you forgot. Fix it.
- make clean; make
- Install the mod_WebObjects module with apxs
- Configure your httpd.conf and either link or copy the WebObjects directory from the standard location (if on MacOS X) to your new htdocs directory.
- apachectl configtest; apachectl graceful
- Curse again. Change the httpd.conf file as necessary.
- apachectl graceful. Go to 8 as necessary.
- Finally! apachectl graceful
Enjoy your shiny new WO adaptor.
Note: if you are getting the error
Add to the end of your make.config the following:
CC = gcc
Webobjects Adaptor for Apache 2.4
In 2.4, such access control is done in the same way as other authorization checks, using the new module
mod_authz_host. The old access control idioms should be replaced by the new authentication mechanisms, although for compatibility with old configurations, the new module
mod_access_compat is provided.