Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(164)

Unified Diff: third_party/WebKit/Source/core/loader/PingLoader.cpp

Issue 2555713002: Don't use FetchRequest in FrameFetchContext (Closed)
Patch Set: Rebase Created 4 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/WebKit/Source/core/loader/PingLoader.cpp
diff --git a/third_party/WebKit/Source/core/loader/PingLoader.cpp b/third_party/WebKit/Source/core/loader/PingLoader.cpp
index 956cc975a14c432b310e98ef0777481f61f21a14..6ee6b68ea50aa6674104f1d575af24ebc29cfe10 100644
--- a/third_party/WebKit/Source/core/loader/PingLoader.cpp
+++ b/third_party/WebKit/Source/core/loader/PingLoader.cpp
@@ -397,7 +397,8 @@ void finishPingRequestInitialization(
request.setRequestContext(requestContext);
FetchContext& fetchContext = frame->document()->fetcher()->context();
fetchContext.addAdditionalRequestHeaders(request, FetchSubresource);
- fetchContext.populateRequestData(request);
+ // TODO(tyoshino): Call populateResourceRequest() if appropriate.
+ fetchContext.setFirstPartyCookieAndRequestorOrigin(request);
}
bool sendPingCommon(LocalFrame* frame,

Powered by Google App Engine
This is Rietveld 408576698