Remove stale-while-revalidate from content and chrome

content/public/common/content_features.cc

Index: content/public/common/content_features.cc
diff --git a/content/public/common/content_features.cc b/content/public/common/content_features.cc
index e64750b0d09c98959b74bd55a176cd007fbc4f50..1658d60b1367cef4ca0d040e2d277bf0c12b47e2 100644
--- a/content/public/common/content_features.cc
+++ b/content/public/common/content_features.cc
@@ -202,12 +202,6 @@ const base::Feature kSlimmingPaintInvalidation{
 const base::Feature kSpeculativeLaunchServiceWorker{
     "SpeculativeLaunchServiceWorker", base::FEATURE_DISABLED_BY_DEFAULT};
 
-// Enables implementation of the Cache-Control: stale-while-revalidate directive
-// which permits servers to allow the use of stale resources while revalidation
-// proceeds in the background. See http://crbug.com/348877
-const base::Feature kStaleWhileRevalidate{"StaleWhileRevalidate2",
-                                          base::FEATURE_DISABLED_BY_DEFAULT};
-
 // Throttle Blink timers in out-of-view cross origin frames.
 const base::Feature kTimerThrottlingForHiddenFrames{
     "TimerThrottlingForHiddenFrames", base::FEATURE_ENABLED_BY_DEFAULT};