Configure the Maximum HTML Response Size in QCDR

Maximum HTML response size is a request-level Runtime Safety limit. If the completed frontend response is larger than this value, QCDR skips Rule and Token transformation for that request and preserves Joomla's original rendered output.

The QCDR 1.1.05 default is 5,242,880 bytes (5 MB).

Where to Change the Limit

  1. Open Components > QC Dynamic Replacer > Settings.
  2. Find the Runtime Safety card.
  3. Change Maximum HTML response size.
  4. Save Settings.
  5. Test representative large frontend pages after the change.

Allowed Range

QCDR clamps the saved value to:

  • Minimum: 65,536 bytes (64 KB)
  • Default: 5,242,880 bytes (5 MB)
  • Maximum: 52,428,800 bytes (50 MB)

The setting is stored and evaluated in bytes. The UI uses a 1,024-byte input step.

What Happens When a Page Is Too Large

The check occurs before normal Rule/Token transformation. When the rendered body exceeds the configured limit, QCDR marks the request as skipped and returns the marker-free original Joomla output. It does not process the first part of the page and then stop halfway.

That behavior is intentional: a size limit should protect the request without leaving a partially transformed document.

When to Raise the Limit

Raise it only when legitimate frontend pages regularly exceed the current limit and you actually need QCDR on those pages. Examples can include very large catalog/listing pages or pages containing unusually large inline markup.

Before increasing it, inspect why the HTML is so large. A page that unexpectedly grows from hundreds of kilobytes to several megabytes may have a template, module, debug-output, or content problem that should be fixed instead of hidden by a higher QCDR ceiling.

When to Lower the Limit

A lower ceiling can deliberately keep QCDR away from unusually heavy responses. Remember that any page over the limit will receive no normal QCDR Rules or standalone Token replacements for that request.

Verify the Result

Test one page below the limit and one representative large page. If the large page is skipped, its original Joomla content should remain intact. If you need exact runtime diagnostics, temporarily use a controlled test page rather than raising the production limit blindly.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.