The response was too large
The document exceeded the size limit for a single analysis.
What it means
The response exceeded the byte cap we apply to any single fetch, so reading stopped before the whole document arrived and analysis could not proceed.
Why it matters
The cap stops one request exhausting server memory. A manifest this large is also a problem in its own right: every client downloads it, and a very large playlist means slow start-up for everyone.
How to fix it
- For a huge XMLTV guide, split it by date range or channel group.
- For a huge playlist, consider whether the live window is longer than it needs to be.
- Serve gzip-encoded where you can; it makes an enormous difference to XMLTV in particular.
Check your own stream
The free stream tester runs this check on every analysis and links each finding straight back here.
Open the stream tester →Frequently asked questions
- What does "The response was too large" mean?
- The response exceeded the byte cap we apply to any single fetch, so reading stopped before the whole document arrived and analysis could not proceed.
- Why does it matter?
- The cap stops one request exhausting server memory. A manifest this large is also a problem in its own right: every client downloads it, and a very large playlist means slow start-up for everyone.
- How do I fix it?
- 1. For a huge XMLTV guide, split it by date range or channel group. 2. For a huge playlist, consider whether the live window is longer than it needs to be. 3. Serve gzip-encoded where you can; it makes an enormous difference to XMLTV in particular.
- How do I confirm this is the origin and not the player?
- Run the URL through the stream tester, which reports the response the origin actually returned — status, headers, redirects and size — so you can separate a delivery fault from a manifest fault.
- What is the first thing to try?
- For a huge XMLTV guide, split it by date range or channel group.
Related Fetching and delivery checks
- The browser blocked the request (CORS)Your browser refused to read the response because the origin did not send an Access-Control-Allow-Origin header.
- The origin returned an error statusThe server answered with a 4xx or 5xx status instead of the manifest, so there was nothing to analyze.
- That address cannot be reached from our serversThe URL resolves to a private or reserved address, so we will not connect to it from the server. Local mode tests it from your own browser instead.
- That is not a valid URLThe address could not be parsed, so no request was attempted.
- That URL scheme is not supportedOnly http and https can be fetched; schemes such as rtmp, rtsp and file cannot.
- The URL redirected too many timesWe follow up to three redirects; this URL exceeded that.