Versions Compared

Old Version 9

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Name

FORCE_SC_ACCEPTED

Possible Values

"true", "false"

Default Behavior

false

Scope

axis2

Description

When set to true, this property forces a 202 HTTP response to the client immediately after the ESB profile receives the message so that the client stops waiting for a response.

Example

Code Block
<property name="FORCE_SC_ACCEPTED" value="true" scope="axis2"/>

Anchor
DISABLE_CHUNKING
DISABLE_CHUNKING
DISABLE_CHUNKING

Name

DISABLE_CHUNKING

Possible Values

"true", "false"

Default Behavior

false

Scope

axis2

Description

Disables the HTTP chunking for outgoing messaging

If you set this to true, it disables HTTP chunking for outgoing messages. Instead, the ESB profile builds the message to calculate the content length and then sends the particular message to the backend with the content length (e.g., Content-Length: 25).

You can use this parameter if the client sends the request with HTTP chunking (i.e., with Transfer Encoding:chunked) although you need to send the message without HTTP chunking to the backend, or if you need to modify the message payload, which the client receives before sending it to the backend.

Warning

This property might decrease performance since the messages get built per each invocation. Also, this property does not affect Callout mediators, whose chunking must be disabled separately.

Example

Code Block
<property name="DISABLE_CHUNKING" value="true" scope="axis2"/>

...

Name

NO_ENTITY_BODY

Possible Values

"true", "false"none

Default Behavior

In case of GET and DELETE requests this property is set to true.

Scope

Axis2axis2

Description

Set this This property if you want to do the following:

  • check if an incoming request to the ESB mediation flow has an entity body or not
    • tcheck if an outgoing request/response generated from the ESB mediation flow has an entity body or not

    should be set if a user wants to generate a response from the ESB profile to a request without an entity body, for example, GET request.

    Info

    If using the PayloadFactory mediator, this property does not need to be manually set since it is done automatically by the mediator.

    Example

    Code Block
    <property name="NO_ENTITY_BODY" action="remove" scope="axis2"/>

    ...

    Name

    FORCE_POST_PUT_NOBODY

    Possible Values

    "true", "false"

    Default Behavior

    false

    Scope

    axis2

    Description

    This property allows to send a request without a body for POST and PUT HTTP methods.

    Applicable only for HTTP Passthrough transport.

    Example

    Code Block
    <property name="FORCE_POST_PUT_NOBODY" value="true" scope="axis2" type="BOOLEAN"/>


    Anchor
    force-content-length
    force-content-length
    FORCE_HTTP_CONTENT_LENGTH

    Name

    FORCE_HTTP_CONTENT_LENGTH

    Possible Values

    "true", "false"

    Default Behavior

    false

    Scope

    axis2

    Description

    This If the request sent by the client contains the ‘Content-Length’ header, this property allows the content length to be sent when the ESB profile sends a request to a back end server. When HTTP 1.1 is used, this property disables chunking and sends the content length. When HTTP 1.0 is used, the property only sends the content length.This property should be set ESB profile to send the request with the content length (without HTTP chunking) to the back end server.

    You should set this to true in scenarios where the backend server is not able to accept chunked content. For example, in a scenario where a pass-through proxy is defined and the backend does not accept chunked content, this property should be used together with the COPY_CONTENT_LENGTH_FROM_INCOMING property, to simply add the content length without chunking.

    When HTTP 1.1 is used, this property disables chunking and sends the content length. When HTTP 1.0 is used, the property only sends the content length.

    Warning

    This property can cause performance degradation. It , and thereby, you should only be used with message relayuse it with message relay. If you set this to true, the ESB profile forwards the content length coming from the client request to the backend without building the message and calculating the content length. Since the message doesn’t get build, using these properties will perform better than using DISABLE_CHUNKING. However, if you change the receiving payload before sending it to the backend, then having this property will result in an error due to a content length mismatch.

    Example

    Code Block
    languagexml
    <property name="FORCE_HTTP_CONTENT_LENGTH" scope="axis2" value="true"></property>

    ...

    Name

    COPY_CONTENT_LENGTH_FROM_INCOMING

    Possible Values

    "true", "false"

    Default Behavior

    false

    Scope

    axis2

    Description

    This property allows the HTTP content length to be copied from an incoming message. It is only valid when the FORCE_HTTP_CONTENT_LENGTH property is used. The COPY_CONTENT_LENGTH_FROM_INCOMING avoids buffering the message in memory for calculating the content length, thus reducing the risk of performance degradation.

    Example

    Code Block
    languagexml
    <property name="COPY_CONTENT_LENGTH_FROM_INCOMING" value="true" scope="axis2"/>