Add a bit of documentation to note the inclusion of #138

hapi-fhir-base/src/main/java/ca/uhn/fhir/rest/server/ApacheProxyAddressStrategy.java

@@ -20,8 +20,6 @@ package ca.uhn.fhir.rest.server;
  * #L%
  */
 
-import org.apache.commons.lang3.StringUtils;
-
 import javax.servlet.ServletContext;
 import javax.servlet.http.HttpServletRequest;
 

src/changes/changes.xml

@@ -95,6 +95,13 @@
 				server returns multiple pages. Thanks to Bill de Beaubien for 
 				reporting! 
 			</action>
+			<action type="add" issue="119" dev="wdebeau1">
+				Add new server address strategy "ApacheProxyAddressStrategy" which uses 
+				headers "x-forwarded-host" and "x-forwarded-proto" to determine the
+				server's address. This is useful if you are deploying a HAPI FHIR 
+				server behind an Apache proxy (e.g. for load balancing or other reasons).
+				Thanks to Bill de Beaubien for contributing!
+			</action>
 		</release>
 		<release version="0.9" date="2015-Mar-14">
 			<action type="add">

src/site/xdoc/doc_rest_server.xml

@@ -153,13 +153,27 @@
 				<p>
 					The server will attempt to determine what the base URL should be based on
 					what the request it receives looks like, but if it is not getting
-					the right address you may wish to hardcode the base URL, as shown
-					in the following example:
+					the right address you may wish to use a different "address strategy".
+				</p>
+				<p>
+					The simplest way to do this is to configure the server to use a hardcoded
+					base URL, which means that the server won't try to figure out the
+					"http://foo.com/fhir" part of the URL but will instead just use a fixed
+					value you supply. This is shown in the following example:
 				</p>
 				<macro name="snippet">
 					<param name="id" value="addressStrategy"/>
 					<param name="file" value="examples/src/main/java/example/ExampleProviders.java"/>
 				</macro>
+				
+				<h4>Other Strategies</h4>
+				<p>
+					See the 
+					<a href="./apidocs/ca/uhn/fhir/rest/server/IServerAddressStrategy.html">IServerAddressStrategy</a>
+					JavaDoc (specifically the list of "All Known Implementing Classes") to see
+					other strategies that are available.
+				</p>
+				
 			</subsection>
 
 			<subsection name="Deploy">