Skip to Content
Last modified by Aaron Rosenzweig on 2020/09/03 22:17
From version 26.1
edited by Pascal Robert
on 2007/09/03 17:00
Change comment: There is no comment for this version
To version 27.1
edited by Pascal Robert
on 2007/09/03 21:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Programming__WebObjects-Web Applications-Deployment-Apache
1 +Web Applications-Deployment-Apache
Content
... ... @@ -1,12 +1,12 @@
1 -== Overview ==
1 +== Overview ==
2 2  
3 3  In a deployment scenario on Mac OS X, Linux, or Solaris, your applications will most likely be deployed on Apache. Additionally, if you develop with WODirectConnectEnabled=false (you **should**, see the [[Direct Connect>>Web Applications-Development-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.
4 4  
5 -== Split Install ==
5 +== Split Install ==
6 6  
7 7  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, ##/Library/WebObjects/Applications///YourApp//.woa##), while your ##WebServerResources## are installed in another location (on OS X, ##/Library/WebServer/Documents/WebObjects///YourApp//.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.
8 8  
9 -== mod//expires // ==
9 +== mod//expires// ==
10 10  
11 11  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.//
12 12  
... ... @@ -44,13 +44,13 @@
44 44  
45 45  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).
46 46  
47 -== mod//rewrite // ==
47 +== mod//rewrite// ==
48 48  
49 -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.//
49 +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.//
50 50  
51 51  Aaron Rosenzweig has a very thorough article about [[using mod//rewrite with Apache//>>http://www.jewelryluv.com/fashion/pageWithName/ModRewrite]].
52 52  
53 -=== mod//rewite with mod//webobjects ===
53 +=== mod//rewite with mod//webobjects ===
54 54  
55 55  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).//
56 56  
... ... @@ -72,9 +72,9 @@
72 72  
73 73  {{/noformat}}
74 74  
75 -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.
75 +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.
76 76  
77 -=== Mike Schrag ===
77 +=== Mike Schrag ===
78 78  
79 79  Here's an example mod//rewrite we use on one of our apps~://
80 80  
... ... @@ -90,11 +90,11 @@
90 90  
91 91  {{/code}}
92 92  
93 -The WOA produces URLs in the format ##http:~/~/site.com/page/HomePage?appNum=2##, which turns into ##http:~/~/site.com/cgi-bin/WebObjects/AppName.woa/2/viewPage?pageName=HomePage##.
93 +The WOA produces URLs in the format ##[[http://site.com/page/HomePage?appNum=2]]##, which turns into ##[[http://site.com/cgi-bin/WebObjects/AppName.woa/2/viewPage?pageName=HomePage]]##.
94 94  
95 -== WebObjects Adaptor for Apache 2.2 ==
95 +== WebObjects Adaptor for Apache 2.2 ==
96 96  
97 -=== Travis Cripps ===
97 +=== Travis Cripps ===
98 98  
99 99  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.
100 100  
... ... @@ -133,9 +133,9 @@
133 133  1. Test.
134 134  1. Curse again. Change the httpd.conf file as necessary.
135 135  1. apachectl graceful. Go to 8 as necessary.
136 -1. Finally! apachectl graceful
136 +1. Finally apachectl graceful
137 137  
138 -Enjoy your shiny new WO adaptor. :)
138 +Enjoy your shiny new WO adaptor. :-)
139 139  
140 140  * Note: if you are getting the error
141 141  
... ... @@ -149,5 +149,3 @@
149 149  
150 150  Add to the end of your make.config the following:
151 151  ##CC = gcc##
152 -
153 -Category:WebObjects