Purge cache_key if response headers do not include content digest

[evman182]

No description provided.

[ioquatix]

Looks good to me! @olleolleolle any chance you can help me with a detailed review?

[evman182]

@olleolleolle anything else pending on this?

[olleolleolle]

@evman182 Thanks for asking!

I had to reconstruct the "why do we do this?", and my reconstitution of it is: "We purge bodies for which the response was not created with an x-content-digest, because these bodies have not been through the right way of construction."

Is that a nearly-correct way of expressing the reasoning for the change?

[evman182]

@olleolleolle it's already purigng the meta entries if the bodies don't exist for the x-content-digest values. This will additionally purge the meta entries if they don't contain an x-content-digest value in the first place, which, to your point, means the meta entry wasn't constructed correctly.

[olleolleolle]

Thanks for your helpful PR!

[evman182]

Would it be possible to cut a release?

[ioquatix]

Yes, I have been working on that.