Installing the Java Module on Weblogic

  Last updated 2022-04-11

IMPORTANT

This guide only applies to Next-Gen WAF customers with access to the Next-Gen WAF control panel. If you have access to the Next-Gen WAF product in the Fastly control panel, you can only deploy the Next-Gen WAF with the Edge WAF deployment method.

Compatibility

The Next-Gen WAF Java module is compatible with WebLogic version 12c (12.2.1) or higher.

Installation

To deploy the Next-Gen WAF Java module on WebLogic servers, you must first add it to your application as a servlet filter.

Then, deploy your application to your WebLogic server through the same process you would deploy any other Web Application.

Module Configuration

OptionDefaultDescription
rpcServerURIRequired, tcp://127.0.0.1:9999The Unix domain socket or TCP connection to communicate with the agent.
rpcTimeoutRequired, 300msThe timeout in milliseconds that the RPC client waits for a response back from the agent.
maxResponseTimeOptional, no defaultThe maximum time in seconds that the server response time will be evaluated against (i.e., to see if it exceeds this value) to determine if the module should send a post request to the agent.
maxResponseSizeOptional, no defaultThe maximum size in bytes that the server response size will be evaluated against (i.e. to see if it exceeds this value) to determine if the module should send a post request to the agent.
maxPostOptional, no defaultThe maximum POST body size in bytes that can be sent to the Next-Gen WAF agent. For any POST body size exceeding this limit, the module will not send the request to the agent for detection.
asyncStartFixOptional, falseThis can be set to true to workaround missing request body when handling requests asynchronously in servlets.
altResponseCodesOptional, no defaultSpace separated alternative agent response codes used to block the request in addition to 406. For example 403 429 503.
excludeCidrBlockOptional, no defaultA comma-delimited list of CIDR blocks or specific IP addresses to be excluded from filter processing.
excludeIpRangeOptional, no defaultA comma-delimited list of IP ranges or specific IP addresses to be excluded from filter processing.
excludePathOptional, no defaultA comma-delimited list of paths to be excluded from filter processing. If the URL starts with the specified value it will be excluded. Matching is case-insensitive.
excludeHostOptional, no defaultA comma-delimited list of host names to be excluded from filter processing. Matching is case-insensitive.

Sample module configuration:

Module configuration changes must be made in the <!-- Signal Sciences Filter --> section of your application's web.xml file:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
<!-- Signal Sciences Filter -->
<filter>
    <filter-name>sigSciFilter</filter-name>
    <filter-class>com.signalsciences.servlet.filter.SigSciFilter</filter-class>
     <async-supported>true</async-supported>
<init-param>
   <param-name>rpcTimeout</param-name>
   <param-value>500</param-value>
</init-param>
  <init-param>
   <param-name>asyncStartFix</param-name>
   <param-value>true</param-value>
</init-param>
</filter>
<filter-mapping>
    <filter-name>sigSciFilter</filter-name>
    <url-pattern>/*</url-pattern>
</filter-mapping>
<!-- end Signal Sciences Filter -->
Was this guide helpful?

Do not use this form to send sensitive information. If you need assistance, contact support. This form is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Fastly
© Fastly 2024