Versions Compared

Old Version 2

changes.mady.by.user Former user

Saved on

compared with

New Version 3

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reviewed

Some legacy back ends might not support chunked messagesWhen processing large messages, message chunking facilitates sending the message as multiple independant chunks. Message chunking is set using the Transfer-Encoding: chunked header. To However, some legacy backends might not support chunked messages. To disable sending chunked messages to the backend for a specific API, follow the steps below:

  1. Create an xml XML file with the following content:

    Code Block
    languagexml
    titledisable chunking
    <?xml version="1.0" encoding="UTF-8"?>
<sequence xmlns="http://ws.apache.org/ns/synapse" name="disableChunkingSeq">
   <property name="DISABLE_CHUNKING" value="true" scope="axis2"/>
</sequence>

  2. Use the same sequence and apply it as a mediation extension for to the inflow of this particular API, to the inflow. For more details, see Creating per-API extensions. Once the API is published, the chunking will be is disabled for the message that is sent to the backend.

    Info

    You To stop chunked messages from being sent to the client, you can apply the same mediation extenstion extension to the out sequence as well, to stop chunked messages being sent to the client.