|
Firewall PluginTry It Out
What It DoesThe Firewall Plugin demonstrates how to use the setFirewallInfo method on RequestInfo or the FirewallRequestEditor bean to select what firewall settings a given transaction uses. Normally, WBI uses a single proxy or socks settings, as specified in the http://_wbi/setup or the "etc\config\wbi\TCPIP.prop" file. Using the setFirewallInfo method or the FirewallRequestEditor bean, however, the firewall settings can be on a per request basis. This plugin provides a sample RequestEditor for an intranet application that routes requests through a socks firewall when they are destined for hosts outside the local intranet. Requests for pages inside the firewall are unaffected. This plugin also provides an sample generator that allows a user to request individual URLs using specific firewall settings. How It WorksThere are two examples here. The first uses the FirewallRequestEditor bean to route requests through a specific socks or proxy machine depending on whether a request is for a local page (within the firewall) or a distant page (outside the firewall). Note that the example is hardcoded to use settings for IBM's intranet. To make it work in your enviornment, you must modify the code. The first example uses a RequestEditor to determine whether the request is being made of a host inside o outside the local firewall. If the request is being made of a host inside the firewall, the the request editor simply rejects the request, effectively passing it along without touching it. If the request is for a document on a host outside the firewall, the request editor forwards the request to a FirewallRequestEditor that has the appropriate socks server set. The second example shows how to use the RequestInfo.setFirewallInfo() method to modify the proxy or socks settings for a particular transaction. In this case, the FirewallGenerator provides a way fetch individual URLs through a specific firewall. That is, a client can request "http://_wbiFetch/get?url=http://www.ibm.com/&socks=socks.almaden.ibm.com" and WBI will fetch" http://www.ibm.com/" through the socks server "socks.lmaden.ibm.com" and return the result to the client. Known Problems
Some key WBI classes that were used:
The Source
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||