Introduce new security restrictions in FetchEvent.respondWith().

third_party/WebKit/Source/core/frame/Deprecation.cpp

Index: third_party/WebKit/Source/core/frame/Deprecation.cpp
diff --git a/third_party/WebKit/Source/core/frame/Deprecation.cpp b/third_party/WebKit/Source/core/frame/Deprecation.cpp
index 6284adb2f49a04c4558cb2123b68384e1e86d812..1f0bd83ea7edbb31e61d35b480a2a83381131da6 100644
--- a/third_party/WebKit/Source/core/frame/Deprecation.cpp
+++ b/third_party/WebKit/Source/core/frame/Deprecation.cpp
@@ -413,6 +413,12 @@ String Deprecation::deprecationMessage(UseCounter::Feature feature) {
     case UseCounter::HTMLObjectElementLegacyCall:
       return willBeRemoved("HTMLObjectElement legacy caller", M58,
                            "5715026367217664");
+    case UseCounter::
+        ServiceWorkerRespondToNavigationRequestWithRedirectedResponse:
+      return String::format(
+          "The service worker responded to the navigation request with a "
+          "redirected response. This will result in an error in %s.",
+          milestoneString(M59));
 
     // Features that aren't deprecated don't have a deprecation message.
     default: