Sometimes it may be required to disable chunking in the API requests done via WSO2 API Cloud. Some back-end servers does not accept chunked content and therefore you may need to disable chunking.
In a Standalone WSO2 APIM, this can be done by editing the velocity template as described in this blog post. However in WSO2 API Cloud it is not possible to edit the velocity template.
This can be done with the use of a custom mediation extension which will disable chunking, as described below.
The corresponding sequence would be like;
You can find a sample sequence (disable-chunking.xml) which you can upload to the Governance registry of the API Cloud using the management console UI of Gateway (https://gateway.api.cloud.wso2.com/carbon).
You can get the user name from the top right corner of the Publisher and then enter your password and log in. Once you are logged in select Resources (left hand side of the Management console) and click on Browse and then navigate to /_system/governance/apimgt/customsequences registry location. Since this sequence need to be invoked in the In direction (or the request path) navigate to the in collection. Click Add Resource and upload the XML file of the sequence configuration and add it. (Note: Once you add the sequence it might take up-to 15 minutes until it is deployed into the publisher)
In Publisher select the required API and go to edit wizard by clicking edit and then navigate into Manage section. Click on Sequences check box and select the sequence which disable chunking, from the In Flow. After that Save and Publish the API.
Now invoke the API. If you investigate your requests, you will notice that chunking is disabled.
Chunking Enabled
Chunking Disabled
In a Standalone WSO2 APIM, this can be done by editing the velocity template as described in this blog post. However in WSO2 API Cloud it is not possible to edit the velocity template.
This can be done with the use of a custom mediation extension which will disable chunking, as described below.
The corresponding sequence would be like;
<?xml version="1.0" encoding="UTF-8"?> <sequence xmlns="http://ws.apache.org/ns/synapse" name="disable-chunking"> <property name="DISABLE_CHUNKING" value="true" scope="axis2" /> </sequence>
You can find a sample sequence (disable-chunking.xml) which you can upload to the Governance registry of the API Cloud using the management console UI of Gateway (https://gateway.api.cloud.wso2.com/carbon).
You can get the user name from the top right corner of the Publisher and then enter your password and log in. Once you are logged in select Resources (left hand side of the Management console) and click on Browse and then navigate to /_system/governance/apimgt/customsequences registry location. Since this sequence need to be invoked in the In direction (or the request path) navigate to the in collection. Click Add Resource and upload the XML file of the sequence configuration and add it. (Note: Once you add the sequence it might take up-to 15 minutes until it is deployed into the publisher)
In Publisher select the required API and go to edit wizard by clicking edit and then navigate into Manage section. Click on Sequences check box and select the sequence which disable chunking, from the In Flow. After that Save and Publish the API.
Now invoke the API. If you investigate your requests, you will notice that chunking is disabled.
Chunking Enabled
POST customerservice/customers HTTP/1.1 Content-Type: text/xml; charset=ISO-8859-1 Accept: text/xml Transfer-Encoding: chunked Host: 192.168.77.1:8080 Connection: Keep-Alive User-Agent: Synapse-PT-HttpComponents-NIO
Chunking Disabled
POST customerservice/customers HTTP/1.1 Content-Type: text/xml; charset=ISO-8859-1 Accept: text/xml Content-Length: 42 Host: 192.168.77.1:8080 Connection: Keep-Alive User-Agent: Synapse-PT-HttpComponents-NIO
No comments:
Post a Comment