These calls were added in error when trying to fix #22797 and #23775. They are not needed in 304 scenarios. Those have no response content and are skipped by ShallowETagHeaderFilter based on the status. This leaves disableContentCaching invoked only in streaming scenarios, which was the original intent and should be the only reason for that method. See gh-24635