Thanks @gkalyan for the help! Updates on the fix:1. This is not cache poisoning.2. The error was happening when the site was being called with a manipulated header as "Handle: somestring"3. While "Handle" is not a standard header and a custom one, we verified that default output instead of a 403 is...