Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Domains: Configuration: Web Application

Configuration Options Related Tasks Related Topics

Use this page to define the domain-wide Web application configuration settings.

#### Configuration Options

Name | Description
--- | ---
Relogin Enabled | Beginning with the 9.0 release the FORM/BASIC authentication behavior has been modified to conform strictly to the J2EE Specification. If a user has logged-in but does not have privileges to access a resource, the 403 (FORBIDDEN) page will be returned. Turn this flag on to enable the old behavior, which was to return the user to the login form. MBean Attribute: `WebAppContainerMBean.ReloginEnabled` Changes take effect after you redeploy the module or restart the server.
Allow All Roles | In the security-constraints elements defined in a Web application's web.xml deployment descriptor, the auth-constraint element indicates the user roles that should be permitted access to this resource collection. Here role-name = "*" is a compact syntax for indicating all roles in the Web application. In previous releases, role-name = "*" was treated as all users/roles defined in the realm. This parameter is a backward-compatibility switch to restore old behavior. Default behavior is one required by the spec, meaning all roles defined in the web application. If set, the value defined in weblogic.xml (container-descriptor -> allow-all-roles) takes precedence (if set) over this value. MBean Attribute: `WebAppContainerMBean.AllowAllRoles` Changes take effect after you redeploy the module or restart the server.
Filter Dispatched Requests | Indicates whether or not to apply filters to dispatched requests. This is a backward compatibility flag. Until version 8.1, WebLogic Server applied ServletFilters (if configured for the Web application) on request dispatches (and includes/forwards). Servlet 2.4 has introduced the "Dispatcher" element to make this behavior explicit. The default value is Dispatcher=REQUEST. In order to be complaint with the J2EE specification, the default value for FilterDispatchedRequestsEnabled is false beginning with WebLogic Server 9.0. Note that if you are using old descriptors (meaning web.xml does not have version=2.4), then WebLogic Server automatically uses FilterDispatchedRequestsEnabled = true for the Web applications, unless filter-dispatched-requests-enabled is explicitly set to false in weblogic.xml. This means that old applications will work fine without any modification. Additionally, during migration of old domains to the 9.0 domain, the migration plugin automatically sets this flag to true. MBean Attribute: `WebAppContainerMBean.FilterDispatchedRequestsEnabled` Changes take effect after you redeploy the module or restart the server.
Overload Protection Enabled | This parameter is used to enable overload protection in the webapp container against low memory conditions. When a low memory situation occurs, new session creation attempts will result in weblogic.servlet.SessionCreationException. The application code needs to catch this exception and take proper action. Alternatively appropriate error-pages can be configured in web.xml against weblogic.servlet.SessionCreationException. This check is performed only on memory and replicated sessions. MBean Attribute: `WebAppContainerMBean.OverloadProtectionEnabled`
X-Powered-By Header | WebLogic Server uses the X-Powered-By HTTP header, as recommended by the Servlet 2.4 specification, to publish its implementation information. Following are the options: "NONE": X-Powered-By header will not be sent "SHORT" (default): "Servlet/2.4 JSP/2.0" "MEDIUM": "Servlet/2.4 JSP/2.0 (WebLogic/9.1)" "FULL": "Servlet/2.4 JSP/1.2 (WebLogic/9.1 JDK/1.4.1_05)" MBean Attribute: `WebAppContainerMBean.XPoweredByHeaderLevel`
Mime Mapping File | Returns the name of the file containing mime-mappings for the domain. Format of the file should be: extension=mime-type Example: htm=text/html gif=image/gif jpg=image/jpeg If this file does not exist, WebLogic Server uses an implicit mime-mapping set of mappings defined in weblogic.utils.http.HttpConstants (DEFAULT_MIME_MAPPINGS). To remove a mapping defined in implicit map just set it to blank. MBean Attribute: `WebAppContainerMBean.MimeMappingFile` Changes take effect after you redeploy the module or restart the server.
Optimistic Serialization | When OptimisticSerialization is turned on, WebLogic server does not serialize-deserialize context and request attributes upon getAttribute(name) when a request gets dispatched across servlet contexts. This means you will need to make sure that the attributes common to Web applications are scoped to a common parent classloader (they are application-scoped) or placed in the system classpath if the two Web applications do not belong to the same application. When OptimisticSerialization is turned off (which is the default) WebLogic Server does serialize-deserialize context and request attributes upon getAttribute(name) to avoid the possibility of ClassCastExceptions. The value of OptimisticSerialization can also be overridden for specific Web applications by setting the optimistic-serialization value in weblogic.xml. MBean Attribute: `WebAppContainerMBean.OptimisticSerialization` Changes take effect after you redeploy the module or restart the server.
Error on Name request time value | Global property which determines the behavior of the JSP compiler when a jsp:param attribute "name" has a request time value. Without this property set to "true", the JSP compiler throws an error for a JSP using a request time value for the "name" attribute as mandated by the JSP 2.0 spec. This property exists for backward compatibility. MBean Attribute: `WebAppContainerMBean.RtexprvalueJspParamName` Changes take effect after you redeploy the module or restart the server.
Client Cert Proxy Enabled | Specifies whether or not to honor the WL-Proxy-Client-Cert header coming with the request. MBean Attribute: `WebAppContainerMBean.ClientCertProxyEnabled` Changes take effect after you redeploy the module or restart the server.
Http Trace Support Enabled | Returns the value of HttpTraceSupportEnabled. MBean Attribute: `WebAppContainerMBean.HttpTraceSupportEnabled`
WebLogic Plugin Enabled | Specifies whether or not the proprietary `WL-Proxy-Client-IP` header should be honored. (This is needed only when WebLogic plugins are configured.) MBean Attribute: `WebAppContainerMBean.WeblogicPluginEnabled`
Auth Cookie Enabled | Whether authcookie feature is enabled or not. MBean Attribute: `WebAppContainerMBean.AuthCookieEnabled` Secure value: `true`
WAP Enabled | Indicates whether the session ID should include JVM information. (Checking this box may be necessary when using URL rewriting with WAP devices that limit the size of the URL to 128 characters, and may also affect the use of replicated sessions in a cluster.) When this box is selected, the default size of the URL will be set at 52 characters, and it will not contain any special characters. MBean Attribute: `WebAppContainerMBean.WAPEnabled`
Post Timeout | The amount of time this server waits between receiving chunks of data in an HTTP POST data before it times out. (This is used to prevent denial-of-service attacks that attempt to overload the server with POST data.) MBean Attribute: `WebAppContainerMBean.PostTimeoutSecs` Minimum value: `0` Maximum value: `120` Secure value: `30`
Maximum Post Time | Max Post Time (in seconds) for reading HTTP POST data in a servlet request. MaxPostTime < 0 means unlimited MBean Attribute: `WebAppContainerMBean.MaxPostTimeSecs`
Maximum Post Size | The maximum post size this server allows for reading HTTP POST data in a servlet request. A value less than 0 indicates an unlimited size. MBean Attribute: `WebAppContainerMBean.MaxPostSize`
WorkContext Propagation Enabled | Indicates whether or not WorkContextPropagation is enabled. By default it is turned on. There is a little overhead involved in propagating WorkContexts. Therefore, if you don't care about WorkContext propagation, turn this value off in production environments. MBean Attribute: `WebAppContainerMBean.WorkContextPropagationEnabled`
P3P Header Value | Returns the P3PHeader value that will be sent with all responses for http requests (if non-null). The value of this header should set to the location of the policy reference file for the Web site. For details see: http://www.w3.org/TR/p3pdeployment#Locating_PRF Alternatively, a servlet filter can be used to set the P3P header. MBean Attribute: `WebAppContainerMBean.P3PHeaderValue` Changes take effect after you redeploy the module or restart the server.
JSP Compiler Backwards Compatible | Global property to determine the behavior of the JSP compiler. When this property set to "true", the JSP compiler throws a translation error for JSPs that do not conform to the JSP2.0 specification. This property exists for backward compatibility. MBean Attribute: `WebAppContainerMBean.JSPCompilerBackwardsCompatible` Changes take effect after you redeploy the module or restart the server.

Related Tasks

- Deploy Web applications
- Stop deployed Web applications
- Delete Web applications
- Update run-time descriptors

Related Topics

- Developing Web Applications, Servlets, and JSPs for WebLogic Server
- Deploying Applications to WebLogic Server
- Developing Applications for WebLogic Server