532 Response Too Large
The HTTP 532 Response Too Large status code is an unofficial server error specific to Edgio (formerly Layer0). The Edgio platform returns this code when the origin server sends back a response body exceeding the allowed maximum size.
Usage
Edgio enforces size limits on responses passing through its serverless compute layer. Cloud Function workers on Edgio have a maximum response body size of 6 MB. When the origin or a serverless function generates a response larger than this threshold, Edgio rejects the response and returns a 532 to the client.
This limit exists because serverless compute workers buffer the full response in memory before forwarding the result to the edge. Allowing arbitrarily large responses risks memory exhaustion across the worker fleet.
Common triggers include:
- API endpoints returning large JSON payloads or data exports without pagination.
- Server-side rendered pages embedding large inline datasets or base64-encoded assets.
- File download endpoints routed through the serverless layer instead of directly from the origin or a storage backend.
Note
The 6 MB limit applies to responses generated by or passing through Edgio's serverless compute layer. Static assets served directly from the edge cache are not subject to this limit.
SEO impact
Search engines treat Edgio 532 responses as server errors. Persistent payload size errors reduce crawl rate and prevent indexing of affected URLs. Reducing response size below the limit restores normal crawling.
Example
A client requests a large data export through Edgio. The origin returns a 12 MB JSON response, exceeding the 6 MB limit, and Edgio returns a 532.
Request
GET /api/export/all-records HTTP/1.1
Host: www.example.re
Accept: application/json
Response
HTTP/1.1 532 Response Too Large
Date: Mon, 02 Mar 2026 14:15:00 GMT
Content-Type: text/html
Server: ECAcc (dce/26A1)
<html>
<head><title>532 Response Too Large</title></head>
<body>
<h1>532 Response Too Large</h1>
<p>Response exceeded the maximum allowed size</p>
</body>
</html>
How to fix
Paginate large API responses. Return a subset of records per request and include pagination metadata (total count, next page token) so clients retrieve data in manageable chunks.
Compress response bodies using gzip or Brotli at the origin. The 6 MB limit applies to the response body as received by Edgio, so Compression at the origin reduces the transferred size before the limit check.
Move large file downloads off the serverless compute path. Serve binary assets and data exports directly from the origin or a cloud storage bucket (S3, GCS) with a signed URL, bypassing the serverless layer entirely.
For server-side rendered pages embedding large inline data, extract the data into a separate API call or lazy-load the content on the client side.
Takeaway
The 532 Response Too Large is an Edgio-specific status code triggered when a response body exceeds the 6 MB limit imposed by Edgio's serverless compute layer. Pagination, compression, and routing large payloads outside the serverless path prevent this error.