Dont preload from link headers if the response came from MemoryCache

third_party/WebKit/Source/core/loader/LinkLoader.cpp

Index: third_party/WebKit/Source/core/loader/LinkLoader.cpp
diff --git a/third_party/WebKit/Source/core/loader/LinkLoader.cpp b/third_party/WebKit/Source/core/loader/LinkLoader.cpp
index fb6549e54502baa420190857417aa49970623f6a..eb58c35ce12e76d34fc70a3266582634b811175b 100644
--- a/third_party/WebKit/Source/core/loader/LinkLoader.cpp
+++ b/third_party/WebKit/Source/core/loader/LinkLoader.cpp
@@ -313,6 +313,9 @@ void LinkLoader::loadLinksFromHeader(const String& headerValue, const KURL& base
 
         LinkRelAttribute relAttribute(header.rel());
         KURL url(baseURL, header.url());
+        // Sanity check to avoid re-entrancy here.
+        if (url == baseURL)
+            continue;

[Yoav Weiss, 2016/07/19 21:14:22]

Is this specific to MemoryCache? Seems like if I'm serving a response with a
link preload for the same URL, this would protect me from that as well
(regardless of MemoryCache)

[Charlie Harrison, 2016/07/19 21:23:52]

Ah no this isn't specific to memory cache. I added this as a sanity check to
make sure that this kind of problem doesn't come back in a slightly different
form. Happy to remove it but I feel like we might as well abort early and avoid
looking up the resource in memory cache, etc.

[Yoav Weiss, 2016/07/19 21:29:48]

I don't think you should remove it. I'm probably missing something, but I guess
my main trouble with this CL is to figure out which parts of the code do what
the title says it does. (so "Dont preload from link headers if the response came
from MemoryCache")

Is there code in the CL that's doing something MemoryCache specific? If not,
maybe a title change is appropriate

         if (canLoadResources != OnlyLoadResources) {
             if (RuntimeEnabledFeatures::linkHeaderEnabled())
                 dnsPrefetchIfNeeded(relAttribute, url, *document, networkHintsInterface, LinkCalledFromHeader);