Closed (duplicate)
Project:
Feeds
Version:
7.x-2.x-dev
Component:
Code
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
12 Oct 2010 at 19:01 UTC
Updated:
27 Nov 2017 at 08:06 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedI second this. My feed source has neither of those headers because it returns "must-revalidate" in the "Cache-Control" header.
Comment #2
alex_b commented#1 is actually a different issue. cheekdotcom asks for a global kill switch for caching. But 'must-revalidate' should be implemented properly by http_request no matter what.
Comment #3
Anonymous (not verified) commentedNew issue created in http://drupal.org/node/945378 for checking "must-revalidate" in "Cache-Control" header.
Comment #4
alex_b commentedfunkonaut: Thank you and - I am sorry, I should have pointed you to this existing issue right away: #922102: http_request does not respect Cache-Control - only found it again now.
Comment #5
twistor commentedThis is still a valid feature request, but I would like to qualify something. As things currently exist, "must-revalidate" is properly supported. "must-revalidate" only means that we should validate, or recalculate, the correctness of the cached data every time we load it. Feeds always does this.
Moving to 7.x
Comment #6
megachrizI think this feature request is already completely covered in #1360910: Don't cache_set full feed result in http_request.inc (or make optional), so closing this as a duplicate.