There may be a race, by which the attribute is not set when activate()
is invoked, resulting in no pesi processing on the response. But in
fact the response does contain ESI includes, and the attribute gets set
later. With the result that unresolved ESI includes appear in the
response.

The VDP will catch this, because it checks the object attribute
again in vdp_init, and continues only if it is set.