I'd reword the last sentence. My thinking is that the 'delayed_delete' bit only matters on Essex:
Folsom/Grizzly deployments that expose the v1 API are affected by this vulnerability. Essex deployments that use delayed_delete are also affected.
I'd reword the last sentence. My thinking is that the 'delayed_delete' bit only matters on Essex:
Folsom/Grizzly deployments that expose the v1 API are affected by this vulnerability. Essex deployments that use delayed_delete are also affected.