RESTful Edit Management Interface for Oracle WebLogic Server

View This Web App Container

get

/management/weblogic/{version}/edit/webAppContainer

View this web app container.

Request

Path Parameters

version(required): string

The version of the WebLogic REST interface.

Query Parameters

excludeFields: string

The 'excludeFields' query parameter is used to restrict which fields are returned in the response. It is a comma separated list of field names. If present, only fields whose name is not on the list will be returned. If not present, all fields are returned (unless the 'fields' query parameter is specified). Note: 'fields' must not be specified if 'excludeFields' is specified.
excludeLinks: string

The 'excludeLinks' query parameter is used to restrict which links are returned in the response. It is a comma separated list of link relationship names. If present, only links whose relationship name is not on the list will be returned. If not present, all links are returned (unless the 'links' query parameter is specified). Note: 'links' must not be specified if 'excludeLinks' is specified.
fields: string

The 'fields' query parameter is used to restrict which fields are returned in the response. It is a comma separated list of field names. If present, only fields with matching names are returned. If not present, all fields are returned (unless the 'excludeFields' query parameter is specified). Note: 'excludeFields' must not be specified if 'fields' is specified.
links: string

The 'links' query parameter is used to restrict which links are returned in the response. It is a comma separated list of link relationship names. If present, only links with matching relationship names are returned. If not present, all links are returned (unless the 'excludeLinks' query parameter is specified). Note: 'excludeLinks' must not be specified if 'links' is specified.

Security

Admin: basic

Type: basic

Description: A user in the Admin security role.
Deployer: basic

Type: basic

Description: A user in the Deployer security role.
Monitor: basic

Type: basic

Description: A user in the Monitor security role.
Operator: basic

Type: basic

Description: A user in the Operator security role.

Response

Supported Media Types

application/json

200 Response

Returns this web app container.

This method can return the following links:

rel=gzipCompression uri=/management/weblogic/{version}/edit/webAppContainer/gzipCompression
This resource's gzipCompression singleton resource.
rel=http2Config uri=/management/weblogic/{version}/edit/webAppContainer/http2Config
This resource's http2Config singleton resource.

Root Schema : Web App Container

Type: object

Show Source

allowAllRoles: boolean

Default Value: false

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 specification, 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.
authCookieEnabled: boolean

Default Value: true

Specifies whether the AuthCookie feature is enabled or not.
changeSessionIDOnAuthentication: boolean

Default Value: true

Global property to determine if we need to generate a new SessionID after authentication. When this property is set to "false", the previous sessionID will be retained even after authorization.
clientCertProxyEnabled: boolean

Default Value: false

Specifies whether or not to honor the WL-Proxy-Client-Cert header coming with the request.
dynamicallyCreated: boolean

Read Only: true

Default Value: false

Return whether the MBean was created dynamically or is persisted to config.xml
filterDispatchedRequestsEnabled: boolean

Default Value: false

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 compliant with the Java EE 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 plug-in automatically sets this flag to true.
formAuthXFrameOptionsHeaderValue: string
Returns the X-Frame-Options header value (DENY, SAMEORIGIN, or ALLOW-FROM uri) that will be set in the responses for all requests to the "j_security_check" endpoint when using FORM authentication.
A system property has been added and is used for the same purpose: weblogic.web.servlet.FormAuth.X-Frame-Options.
The FormAuthXFrameOptionsHeaderValue is decided by both the MBean attribute and the system property. The valid values are: DENY, SAMEORIGIN or ALLOW-FROM uri:
1. If the MBean attribute is set and valid, then use the MBean attribute value.
2. If not, then check the system property.
3. If it is set and valid, then use the system property value.
4. If neither is set and valid, then use default value: DENY.
httpTraceSupportEnabled: boolean

Default Value: false

Returns the value of HttpTraceSupportEnabled.
id: integer(int64)

Read Only: true

Return the unique id of this MBean instance
jaxRsMonitoringDefaultBehavior: boolean

Default Value: true

Global property to determine the behavior of monitoring in JAX-RS applications. When the property is set to true (or not set) the monitoring is turned on (if not overridden by properties set directly in application). If the property is set to false the monitoring for all JAX-RS applications is disabled.
JSPCompilerBackwardsCompatible: boolean

Default Value: false

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.
maxPostSize: integer(int32)

Default Value: -1

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.
maxPostTimeSecs: integer(int32)

Default Value: -1

Maximum post time (in seconds) for reading HTTP POST data in a servlet request. MaxPostTime < 0 means unlimited
maxRequestParameterCount: integer(int32)

Default Value: 10000

The maximum request parameter count this server allows for reading maximum HTTP POST parameters count in a servlet request.
Gets the maxRequestParameterCount attribute of the WebServerMBean object.
maxSingleHeaderSize: integer(int32)

Default Value: -1

The maximum size of a single header (name and value) this server allows in a servlet request.
A value less than 0 indicates an unlimited size.
maxTotalHeadersSize: integer(int32)

Default Value: 131072

The maximum total headers size this server allows for reading HTTP headers in a servlet request.
A value less than 0 indicates an unlimited size.
mimeMappingFile: string

Default Value: ./config/mimemappings.properties

Returns the name of the file containing mime-mappings for the domain.
The Format of the file should be: extension=mime-type
For 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, set it to blank.
name: string
Read Only: true
The user-specified name of this MBean instance.
This name is included as one of the key properties in the MBean's javax.management.ObjectName
Name=user-specified-name
Constraints
- legal null
notes: string

Optional information that you can include to describe this configuration.
WebLogic Server saves this note in the domain's configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the xml entity <. Carriage returns/line feeds are preserved.
Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.


            
            
            optimisticSerialization: 
            boolean
            
                
                


















Default Value: false







 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. 




                
            
            
            
            
            overloadProtectionEnabled: 
            boolean
            
                
                


















Default Value: false







This parameter is used to enable overload protection in the web application 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. 




                
            
            
            
            
            p3PHeaderValue: 
            string
            
                
                
























 Returns the P3P header value that will be sent with all responses for HTTP requests (if non-null). The value of this header points to the location of the policy reference file for the website.
Alternatively, a servlet filter can be used to set the P3P header.




                
            
            
            
            
            postTimeoutSecs: 
            integer(int32)
            
                
                




Minimum Value: 0





Maximum Value: 120











Default Value: 30







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.)




                
            
            
            
            
            rejectMaliciousPathParameters: 
            boolean
            
                
                


















Default Value: true







The WebApp Container configuration for rejection of URIs with malicious path parameters.
The WebApp Container configuration specifies whether URIs with malicious path parameters will be rejected.
By default, the WebApp Container will reject URIs with malicious path parameters.




                
            
            
            
            
            reloginEnabled: 
            boolean
            
                
                


















Default Value: false







Beginning with the 9.0 release, the FORM/BASIC authentication behavior has been modified to conform strictly to the Java EE 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.




                
            
            
            
            
            retainOriginalURL: 
            boolean
            
                
                


















Default Value: false







 The retain-original-url property is used in FORM based authentication scenarios. When this property is set to true, after a successful authentication, WebLogic Server will redirect back to the web resource (page/servlet) retaining the protocol (http/https) used to access the protected resource in the original request. If set to false (which is the default value), WebLogic Server will redirect back to the protected resource using the current protocol. The retain-original-url value can also be specified at per web application level in weblogic.xml. The value in weblogic.xml, if specified, overrides the domain level value.




                
            
            
            
            
            rtexprvalueJspParamName: 
            boolean
            
                
                


















Default Value: false







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 specification. This property exists for backward compatibility.




                
            
            
            
            
            sameSiteFilterCookieSettings: 
            array  Items
            
            
                
                
Title: Items





















The HTTP Cookie configuration for the WebLogic HTTP SameSite Java EE Servlet Filter.
The Cookie configuration specifies a String array of settings. Each setting specifies a match for the Cookie name using a regular expression, a value for the SameSite attribute and optionally, a secure setting for the Cookie. The regular expression follows the Java Pattern syntax specification.
For example: ["match=JSESSIONID; value=Strict", "match=MYAPP.*; value=None; secure=true"]
By default, there are no cookie settings, thus the WebLogic HTTP SameSite filter will not be used. Once settings are configured, any newly deployed applications will use the WebLogic HTTP SameSite filter. Running applications must be re-started or re-deployed for the filter to be applied.
When the WebLogic HTTP SameSite filter runs and the HTTP response has already been committed, then no update to the Cookies in the HTTP response can be performed.


                
            
            
            
            
            sameSiteFilterSecureChannelRequired: 
            boolean
            
                
                


















Default Value: false







The Secure Channel configuration for the WebLogic SameSite Java EE Servlet Filter.
The Secure Channel configuration specifies if a secure channel is required when setting the SameSite Cookie attribute where the Secure attribute is also set to true for the specific Cookie.
By default, the Secure attribute setting will be applied for any channel as the user agent may reside in front of a proxy or load balancer when accessing resources.




                
            
            
            
            
            sameSiteFilterUserAgentRegEx: 
            array  Items
            
            
                
                
Title: Items





















The User Agent configuration for the WebLogic HTTP SameSite Java EE Servlet Filter.
The User Agent configuration specifies a String array of regular expressions. When the WebLogic HTTP SameSite filter matches any of these expressions with the HTTP User-Agent header value, then the Cookie settings will be applied for the HTTP request. The regular expression follows the Java Pattern syntax specification.
For example: [".*Chrom(e|ium).*"]
By default, there are no expressions, thus the SameSite Cookie settings are applied for all requests.
Note that if the HTTP response has been committed when the WebLogic HTTP SameSite filter runs, then no update to the Cookies in the HTTP response can be performed.


                
            
            
            
            
            servletAuthenticationFormURL: 
            boolean
            
                
                


















Default Value: true







 ServletAuthenticationFormURL is used for backward compatibility with previous releases of Weblogic Server. If ServletAuthenticationFormURL is set to true (default), then ServletAuthentication.getTargetURLForFormAuthentication() and HttpSession.getAttribute(AuthFilter.TARGET_URL) will return the URL of the protected target resource. If set to false, the above APIs will return the URI of the protected target resource. By default, the value is set to true.(new method added in 9.0.0.1) 




                
            
            
            
            
            servletReloadCheckSecs: 
            integer(int32)
            
                
                


















Default Value: 1







Constraints
production mode default : -1




                
            
            
            
            
            showArchivedRealPathEnabled: 
            boolean
            
                
                


















Default Value: false







Global property to determine the behavior of getRealPath() for archived web applications. When this property is set to "true", getRealPath() will return the canonical path of the resource files. 




                
            
            
            
            
            synchronizedSessionTimeoutEnabled: 
            boolean
            
                
                


















Default Value: false







Indicates whether to also invalidate all the other sessions when one of the sessions that share the same ID expires.




                
            
            
            
            
            tags: 
            array  Items
            
            
                
                
Title: Items





















Return all tags on this Configuration MBean


                
            
            
            
            
            type: 
            string
            
                
                


Read Only: true























Returns the type of the MBean.
Constraints
unharvestable




                
            
            
            
            
            WAPEnabled: 
            boolean
            
                
                


















Default Value: false







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.




                
            
            
            
            
            weblogicPluginEnabled: 
            boolean
            
                
                


















Default Value: false







Specifies whether or not the proprietary WL-Proxy-Client-IP header should be honored. (This is needed only when WebLogic Server plug-ins are configured.)




                
            
            
            
            
            workContextPropagationEnabled: 
            boolean
            
                
                


















Default Value: true







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 want WorkContext propagation, turn this value off in production environments. 




                
            
            
            
            
            XPoweredByHeaderLevel: 
            string
            
                
                


















Default Value: NONE



Allowed Values: [
    "NONE",
    "SHORT",
    "MEDIUM",
    "FULL"
]





 WebLogic Server uses the X-Powered-By HTTP header, as recommended by the Servlet 3.1 specification, to publish its implementation information.
 Following are the options: 
"NONE" (default):  X-Powered-By header will not be sent 
"SHORT":           "Servlet/3.1 JSP/2.3"  
"MEDIUM":          "Servlet/3.1 JSP/2.3 (WebLogic/12.2)" 
"FULL":            "Servlet/3.1 JSP/2.3 (WebLogic/12.2 JDK/1.8)"


        {
    "type":"object",
    "properties":{
        "JSPCompilerBackwardsCompatible":{
            "default":false,
            "type":"boolean",
            "description":"<p>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.</p>"
        },
        "WAPEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>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.</p>"
        },
        "XPoweredByHeaderLevel":{
            "default":"NONE",
            "enum":[
                "NONE",
                "SHORT",
                "MEDIUM",
                "FULL"
            ],
            "type":"string",
            "description":"<p> WebLogic Server uses the X-Powered-By HTTP header, as recommended by the Servlet 3.1 specification, to publish its implementation information.</p><p></p><p> Following are the options: </p><ul><li><p>\"NONE\" (default):  X-Powered-By header will not be sent </p></li><li><p>\"SHORT\":           \"Servlet/3.1 JSP/2.3\"  </p></li><li><p>\"MEDIUM\":          \"Servlet/3.1 JSP/2.3 (WebLogic/12.2)\" </p></li><li><p>\"FULL\":            \"Servlet/3.1 JSP/2.3 (WebLogic/12.2 JDK/1.8)\" </p></li></ul>"
        },
        "allowAllRoles":{
            "default":false,
            "type":"boolean",
            "description":"<p>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.</p><p>This parameter is a backward-compatibility switch to restore old behavior. Default behavior is one required by the specification, meaning all roles defined in the web application.</p><p>If set, the value defined in weblogic.xml (container-descriptor -> allow-all-roles) takes precedence (if set) over this value. </p>"
        },
        "authCookieEnabled":{
            "default":true,
            "type":"boolean",
            "description":"<p>Specifies whether the AuthCookie feature is enabled or not.</p>"
        },
        "changeSessionIDOnAuthentication":{
            "default":true,
            "type":"boolean",
            "description":"<p>Global property to determine if we need to generate a new SessionID after authentication. When this property is set to \"false\", the previous sessionID will be retained even after authorization. </p>"
        },
        "clientCertProxyEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Specifies whether or not to honor the WL-Proxy-Client-Cert header coming with the request. </p>"
        },
        "dynamicallyCreated":{
            "readOnly":true,
            "default":false,
            "type":"boolean",
            "description":"<p>Return whether the MBean was created dynamically or is persisted to config.xml</p>"
        },
        "filterDispatchedRequestsEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p> 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 compliant with the Java EE 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 plug-in automatically sets this flag to true. </p>"
        },
        "formAuthXFrameOptionsHeaderValue":{
            "type":"string",
            "description":"<p> Returns the X-Frame-Options header value (DENY, SAMEORIGIN, or ALLOW-FROM uri) that will be set in the responses for all requests to the \"j_security_check\" endpoint when using FORM authentication. </p><p> A system property has been added and is used for the same purpose: weblogic.web.servlet.FormAuth.X-Frame-Options.</p><p> The FormAuthXFrameOptionsHeaderValue is decided by both the MBean attribute and the system property. The valid values are: DENY, SAMEORIGIN or ALLOW-FROM uri: </p><ol><li><p>If the MBean attribute is set and valid, then use the MBean attribute value.</p></li><li><p>If not, then check the system property.</p></li><li><p>If it is set and valid, then use the system property value.</p></li><li><p>If neither is set and valid, then use default value: DENY.</p></li></ol>"
        },
        "httpTraceSupportEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p> Returns the value of HttpTraceSupportEnabled. </p>"
        },
        "id":{
            "readOnly":true,
            "type":"integer",
            "format":"int64",
            "description":"<p>Return the unique id of this MBean instance</p>"
        },
        "jaxRsMonitoringDefaultBehavior":{
            "default":true,
            "type":"boolean",
            "description":"<p> Global property to determine the behavior of monitoring in JAX-RS applications. When the property is set to <code>true</code> (or not set) the monitoring is turned on (if not overridden by properties set directly in application). If the property is set to <code>false</code> the monitoring for all JAX-RS applications is disabled. </p>"
        },
        "maxPostSize":{
            "default":"-1",
            "type":"integer",
            "format":"int32",
            "description":"<p>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.</p>"
        },
        "maxPostTimeSecs":{
            "default":"-1",
            "type":"integer",
            "format":"int32",
            "description":"<p>Maximum post time (in seconds) for reading HTTP POST data in a servlet request. MaxPostTime < 0 means unlimited</p>"
        },
        "maxRequestParameterCount":{
            "default":"10000",
            "type":"integer",
            "format":"int32",
            "description":"<p>The maximum request parameter count this server allows for reading maximum HTTP POST parameters count in a servlet request.</p><p></p><p>Gets the maxRequestParameterCount attribute of the WebServerMBean object.</p>"
        },
        "maxSingleHeaderSize":{
            "default":"-1",
            "type":"integer",
            "format":"int32",
            "description":"<p>The maximum size of a single header (name and value) this server allows in a servlet request.</p><p>A value less than 0 indicates an unlimited size.</p>"
        },
        "maxTotalHeadersSize":{
            "default":"131072",
            "type":"integer",
            "format":"int32",
            "description":"<p>The maximum total headers size this server allows for reading HTTP headers in a servlet request.</p><p>A value less than 0 indicates an unlimited size.</p>"
        },
        "mimeMappingFile":{
            "default":"./config/mimemappings.properties",
            "type":"string",
            "description":"<p>Returns the name of the file containing mime-mappings for the domain.</p><p>The Format of the file should be: extension=mime-type </p><p> For Example:</p><p>htm=text/html</p><p>gif=image/gif</p><p>jpg=image/jpeg</p><p></p><p>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, set it to blank. </p>"
        },
        "name":{
            "readOnly":true,
            "x-weblogic-legalNull":true,
            "type":"string",
            "description":"<p>The user-specified name of this MBean instance.</p><p>This name is included as one of the key properties in the MBean's <code>javax.management.ObjectName</code></p><p><code>Name=<i>user-specified-name</i></code></p><p><h5>Constraints</h5></p><ul><li>legal null</li></ul>"
        },
        "notes":{
            "type":"string",
            "description":"<p>Optional information that you can include to describe this configuration.</p><p>WebLogic Server saves this note in the domain's configuration file (<code>config.xml</code>) as XML PCDATA. All left angle brackets (<) are converted to the XML entity <code>&lt;</code>. Carriage returns/line feeds are preserved.</p><p>Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.</p>"
        },
        "optimisticSerialization":{
            "default":false,
            "type":"boolean",
            "description":"<p> 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. </p>"
        },
        "overloadProtectionEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>This parameter is used to enable overload protection in the web application 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. </p>"
        },
        "p3PHeaderValue":{
            "type":"string",
            "description":"<p> Returns the P3P header value that will be sent with all responses for HTTP requests (if non-null). The value of this header points to the location of the policy reference file for the website.</p><p></p><p>Alternatively, a servlet filter can be used to set the P3P header.</p>"
        },
        "postTimeoutSecs":{
            "default":"30",
            "minimum":"0",
            "maximum":"120",
            "type":"integer",
            "format":"int32",
            "description":"<p>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.)</p>"
        },
        "rejectMaliciousPathParameters":{
            "default":true,
            "type":"boolean",
            "description":"<p>The WebApp Container configuration for rejection of URIs with malicious path parameters.</p><p></p><p>The WebApp Container configuration specifies whether URIs with malicious path parameters will be rejected.</p><p></p><p>By default, the WebApp Container will reject URIs with malicious path parameters.</p>"
        },
        "reloginEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Beginning with the 9.0 release, the FORM/BASIC authentication behavior has been modified to conform strictly to the Java EE 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.</p>"
        },
        "retainOriginalURL":{
            "default":false,
            "type":"boolean",
            "description":"<p> The retain-original-url property is used in FORM based authentication scenarios. When this property is set to true, after a successful authentication, WebLogic Server will redirect back to the web resource (page/servlet) retaining the protocol (http/https) used to access the protected resource in the original request. If set to false (which is the default value), WebLogic Server will redirect back to the protected resource using the current protocol. The retain-original-url value can also be specified at per web application level in weblogic.xml. The value in weblogic.xml, if specified, overrides the domain level value.</p>"
        },
        "rtexprvalueJspParamName":{
            "default":false,
            "type":"boolean",
            "description":"<p>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 specification. This property exists for backward compatibility.</p>"
        },
        "sameSiteFilterCookieSettings":{
            "default":null,
            "title":"Items",
            "type":"array",
            "items":{
                "type":"string",
                "description":""
            },
            "description":"<p>The HTTP Cookie configuration for the WebLogic HTTP SameSite Java EE Servlet Filter.</p><p></p><p>The Cookie configuration specifies a String array of settings. Each setting specifies a match for the Cookie name using a regular expression, a value for the SameSite attribute and optionally, a secure setting for the Cookie. The regular expression follows the Java <code>Pattern</code> syntax specification.</p><p></p><p>For example: [\"match=JSESSIONID; value=Strict\", \"match=MYAPP.*; value=None; secure=true\"]</p><p></p><p>By default, there are no cookie settings, thus the WebLogic HTTP SameSite filter will not be used. Once settings are configured, any newly deployed applications will use the WebLogic HTTP SameSite filter. Running applications must be re-started or re-deployed for the filter to be applied.</p><p></p><p>When the WebLogic HTTP SameSite filter runs and the HTTP response has already been committed, then no update to the Cookies in the HTTP response can be performed.</p>"
        },
        "sameSiteFilterSecureChannelRequired":{
            "default":false,
            "type":"boolean",
            "description":"<p>The Secure Channel configuration for the WebLogic SameSite Java EE Servlet Filter.</p><p></p><p>The Secure Channel configuration specifies if a secure channel is required when setting the SameSite Cookie attribute where the Secure attribute is also set to true for the specific Cookie.</p><p></p><p>By default, the Secure attribute setting will be applied for any channel as the user agent may reside in front of a proxy or load balancer when accessing resources.</p>"
        },
        "sameSiteFilterUserAgentRegEx":{
            "default":null,
            "title":"Items",
            "type":"array",
            "items":{
                "type":"string",
                "description":""
            },
            "description":"<p>The User Agent configuration for the WebLogic HTTP SameSite Java EE Servlet Filter.</p><p></p><p>The User Agent configuration specifies a String array of regular expressions. When the WebLogic HTTP SameSite filter matches any of these expressions with the HTTP User-Agent header value, then the Cookie settings will be applied for the HTTP request. The regular expression follows the Java <code>Pattern</code> syntax specification.</p><p></p><p>For example: [\".*Chrom(e|ium).*\"]</p><p></p><p>By default, there are no expressions, thus the SameSite Cookie settings are applied for all requests.</p><p></p><p>Note that if the HTTP response has been committed when the WebLogic HTTP SameSite filter runs, then no update to the Cookies in the HTTP response can be performed.</p>"
        },
        "servletAuthenticationFormURL":{
            "default":true,
            "type":"boolean",
            "description":"<p> ServletAuthenticationFormURL is used for backward compatibility with previous releases of Weblogic Server. If ServletAuthenticationFormURL is set to true (default), then ServletAuthentication.getTargetURLForFormAuthentication() and HttpSession.getAttribute(AuthFilter.TARGET_URL) will return the URL of the protected target resource. If set to false, the above APIs will return the URI of the protected target resource. By default, the value is set to true.(new method added in 9.0.0.1) </p>"
        },
        "servletReloadCheckSecs":{
            "default":"1",
            "x-weblogic-productionDefault":"-1",
            "type":"integer",
            "format":"int32",
            "description":"<p><h5>Constraints</h5></p><ul><li>production mode default : -1</li></ul>"
        },
        "showArchivedRealPathEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Global property to determine the behavior of getRealPath() for archived web applications. When this property is set to \"true\", getRealPath() will return the canonical path of the resource files. </p>"
        },
        "synchronizedSessionTimeoutEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Indicates whether to also invalidate all the other sessions when one of the sessions that share the same ID expires.</p>"
        },
        "tags":{
            "title":"Items",
            "type":"array",
            "items":{
                "type":"string",
                "description":""
            },
            "description":"<p>Return all tags on this Configuration MBean</p>"
        },
        "type":{
            "readOnly":true,
            "x-weblogic-unharvestable":true,
            "type":"string",
            "description":"<p>Returns the type of the MBean.</p><p><h5>Constraints</h5></p><ul><li>unharvestable</li></ul>"
        },
        "weblogicPluginEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Specifies whether or not the proprietary <code>WL-Proxy-Client-IP</code> header should be honored. (This is needed only when WebLogic Server plug-ins are configured.)</p>"
        },
        "workContextPropagationEnabled":{
            "default":true,
            "type":"boolean",
            "description":"<p>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 want WorkContext propagation, turn this value off in production environments. </p>"
        }
    },
    "description":""
}



                    
                    
    Nested Schema : Items
    
      
      Type: array
    

    

    
    Title: Items
    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    
    The HTTP Cookie configuration for the WebLogic HTTP SameSite Java EE Servlet Filter.
The Cookie configuration specifies a String array of settings. Each setting specifies a match for the Cookie name using a regular expression, a value for the SameSite attribute and optionally, a secure setting for the Cookie. The regular expression follows the Java Pattern syntax specification.
For example: ["match=JSESSIONID; value=Strict", "match=MYAPP.*; value=None; secure=true"]
By default, there are no cookie settings, thus the WebLogic HTTP SameSite filter will not be used. Once settings are configured, any newly deployed applications will use the WebLogic HTTP SameSite filter. Running applications must be re-started or re-deployed for the filter to be applied.
When the WebLogic HTTP SameSite filter runs and the HTTP response has already been committed, then no update to the Cookies in the HTTP response can be performed.
    

    
    Default Value: oracle.doceng.json.BetterJsonNull@55a3119a
    

    

    

    
        Show Source
        
            
            
            Array of: 
                string
            
            
                
                





























                
            
            
            
        
        {
    "default":null,
    "title":"Items",
    "type":"array",
    "items":{
        "type":"string",
        "description":""
    },
    "description":"<p>The HTTP Cookie configuration for the WebLogic HTTP SameSite Java EE Servlet Filter.</p><p></p><p>The Cookie configuration specifies a String array of settings. Each setting specifies a match for the Cookie name using a regular expression, a value for the SameSite attribute and optionally, a secure setting for the Cookie. The regular expression follows the Java <code>Pattern</code> syntax specification.</p><p></p><p>For example: [\"match=JSESSIONID; value=Strict\", \"match=MYAPP.*; value=None; secure=true\"]</p><p></p><p>By default, there are no cookie settings, thus the WebLogic HTTP SameSite filter will not be used. Once settings are configured, any newly deployed applications will use the WebLogic HTTP SameSite filter. Running applications must be re-started or re-deployed for the filter to be applied.</p><p></p><p>When the WebLogic HTTP SameSite filter runs and the HTTP response has already been committed, then no update to the Cookies in the HTTP response can be performed.</p>"
}
    

    

    

    

    

    




                    
                    
    Nested Schema : Items
    
      
      Type: array
    

    

    
    Title: Items
    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    
    The User Agent configuration for the WebLogic HTTP SameSite Java EE Servlet Filter.
The User Agent configuration specifies a String array of regular expressions. When the WebLogic HTTP SameSite filter matches any of these expressions with the HTTP User-Agent header value, then the Cookie settings will be applied for the HTTP request. The regular expression follows the Java Pattern syntax specification.
For example: [".*Chrom(e|ium).*"]
By default, there are no expressions, thus the SameSite Cookie settings are applied for all requests.
Note that if the HTTP response has been committed when the WebLogic HTTP SameSite filter runs, then no update to the Cookies in the HTTP response can be performed.
    

    
    Default Value: oracle.doceng.json.BetterJsonNull@3a24f397
    

    

    

    
        Show Source
        
            
            
            Array of: 
                string
            
            
                
                





























                
            
            
            
        
        {
    "default":null,
    "title":"Items",
    "type":"array",
    "items":{
        "type":"string",
        "description":""
    },
    "description":"<p>The User Agent configuration for the WebLogic HTTP SameSite Java EE Servlet Filter.</p><p></p><p>The User Agent configuration specifies a String array of regular expressions. When the WebLogic HTTP SameSite filter matches any of these expressions with the HTTP User-Agent header value, then the Cookie settings will be applied for the HTTP request. The regular expression follows the Java <code>Pattern</code> syntax specification.</p><p></p><p>For example: [\".*Chrom(e|ium).*\"]</p><p></p><p>By default, there are no expressions, thus the SameSite Cookie settings are applied for all requests.</p><p></p><p>Note that if the HTTP response has been committed when the WebLogic HTTP SameSite filter runs, then no update to the Cookies in the HTTP response can be performed.</p>"
}
    

    

    

    

    

    




                    
                    
    Nested Schema : Items
    
      
      Type: array
    

    

    
    Title: Items
    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    
    Return all tags on this Configuration MBean
    

    

    

    

    
        Show Source
        
            
            
            Array of: 
                string
            
            
                
                





























                
            
            
            
        
        {
    "title":"Items",
    "type":"array",
    "items":{
        "type":"string",
        "description":""
    },
    "description":"<p>Return all tags on this Configuration MBean</p>"
}


                

				Back to Top