The toolkit includes two reverse proxy servlets which can be used to serve static resources from a distant application and can use the cache to improve performance.
These servlet can also be used to start a Web Assemble Tool-based application without installing a separate Apache http server.
The reverse proxy is a servlet that has to be configured in the web.xml file.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"> <web-app> <servlet> <servlet-name>proxy</servlet-name> <servlet-class>org.esigate.servlet.ProxyServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>proxy</servlet-name> <url-pattern>/images/*</url-pattern> </servlet-mapping> </web-app>
This servlet has the ability to rewrite scheme, port, url and query string before processing the request (proxy or redirect). This is a simple alternative to Apache + mod_rewrite + mod_proxy.
Once configured, this servlet is equivalent to the following Apache configuration :
RewriteEngine On
ProxyRequests Off
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
# URL rewriting
RewriteRule ^/myurl(/?.*)$ http://localhost:8080/webappcontext$1 [P,L]
# URL + query rewriting
RewriteCond %{QUERY_STRING} ^(.+)$
RewriteRule ^/myurl(/?.*)$
http://localhost:8080/webappcontext$1?%1&additionnalparam=value [P,L]
<Location /myurl>
ProxyPassReverse http://localhost:8080/webappcontext
ProxyPassReverseCookiePath /webappcontext /
</Location>
# URL + redirect
RewriteRule ^/myurl(/?.*)$ http://localhost:8080/webappcontext$1 [R=301,L]
# URL + scheme
RewriteCond %{HTTPS} on
RewriteRule ^/myurl(/?.*)$ http://localhost:8080/webappcontext$1 [R=301,L]
# URL + port
RewriteCond %{SERVER_PORT} 8181
RewriteRule ^/myurl(/?.*)$ http://localhost:8080/webappcontext$1 [R=301,L]
Add this servlet to your web application. You can also create a dedicated application deployed on the ROOT context. This way you have full control on the url.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"> <web-app> <servlet> <servlet-name>proxy</servlet-name> <servlet-class>org.esigate.RewriteProxyServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>proxy</servlet-name> <url-pattern>/images/*</url-pattern> </servlet-mapping> </web-app>
Then the proxy has to be configured in both /esigate.properties and org/esigate/rewrite-proxy.properties :
esigate.properties
#esigate.properties webapp.remoteUrlBase=http://localhost:8080/webappcontext/
rewrite-proxy.properties
#org/esigate/rewrite-proxy.properties # Rule 1. (replace <rulename1> by the real rule name) <rulename1>.pattern=^/myurl(/?.*)$ <rulename1>.rewrite=$1 <rulename1>.provider=webapp # Rule 2 (replace <rulename2> by the real rule name) <rulename2>.pattern=^/myurl(/?.*)$ <rulename2>.queryPattern=^(.+)$ <rulename2>.rewrite=$1 <rulename2>.queryRewrite=$1&additionnalparam=value <rulename2>.provider=webapp # Rule 3 (replace <rulename3> by the real rule name) <rulename3>.pattern=^/myurl(/?.*)$ <rulename3>.rewrite=/webappcontext$1 <rulename3>.redirect=301 # Rule 4 (replace <rulename4> by the real rule name) <rulename4>.pattern=^/myurl(/?.*)$ <rulename4>.rewrite=/webappcontext$1 <rulename4>.schemePattern=https <rulename4>.schemeRewrite=http <rulename4>.redirect=301 # Rule 5 (replace <rulename5> by the real rule name) <rulename5>.pattern=^/myurl(/?.*)$ <rulename5>.rewrite=/webappcontext$1 <rulename5>.portPattern=8181 <rulename5>.portRewrite=8080 <rulename5>.redirect=301
In a production environment under very heavy load it may be more efficient to use instead other tools such as Apache mod_proxy