Returning Large Payload with apigee Proxy

Question

We're migrating our services to apigee and we're running into an issue. We have a service that returns large payloads (>55MB) and when I pass it through a defined apigee proxy, it would return:

{ 
  "fault": { 
    "faultstring" : "Body buffer overflow",
    "detail": {
      "errorcode": "protocol.http.TooBigBody"
    }
  }
}

Is there an apigee policy and/or proxy setting I can use to avoid this?

And, no, streaming is not an option. We need to duplicate the behavior as we want the migration to apigee transparent to our clients.

Mike Dunker · Accepted Answer · 2014-02-15T19:05:58.880

7

You should try the TargetEndpoint property response.streaming.enabled . That property passes the response through to the caller untouched without loading the payload into the message buffer. It does not require you to use any kind of HTTP streaming. You will not be able to edit the payload in any way, but it should pass through fine.

Loading a very large payload into memory in the message processor is forbidden because it could result in memory issues for Apigee Edge.

edited Feb 15 '14 at 19:05

answered Feb 14 '14 at 17:34

Mike Dunker

1,950
15
17

this worked. i was using that setting but i added the proxy to HttpProxyConnection instead of TargetEndpoint. Thank you! – Dexter Legaspi Feb 15 '14 at 06:31
This is working – Kushan Menake Jan 25 '22 at 11:25

Returning Large Payload with apigee Proxy

1 Answers1