When we introduced checking ESI includes for status 200 or 204, we would only (potentially, depending on the onerror attribute and esi_onerror_continue parameter) abort ESI processing for includes with a non-zero length.
This patch makes behavior consistent to not depend on whether or not an include is empty.
When we introduced checking ESI includes for status 200 or 204, we would only (potentially, depending on the
onerror
attribute andesi_onerror_continue
parameter) abort ESI processing for includes with a non-zero length.This patch makes behavior consistent to not depend on whether or not an include is empty.
Fixes #4070