[ServiceWorker] Propagates ServiceWorker fetched response's URL and wasFetchedViaServiceWorker flag.

net/http/http_response_info.h

Index: net/http/http_response_info.h
diff --git a/net/http/http_response_info.h b/net/http/http_response_info.h
index efd76fe7b517e98d9fcca9242a51a4f792d758a4..40d707e8a62efb5e5d3ed6fa17441b38af080d8b 100644
--- a/net/http/http_response_info.h
+++ b/net/http/http_response_info.h
@@ -13,6 +13,7 @@
 #include "net/http/http_vary_data.h"
 #include "net/socket/next_proto.h"
 #include "net/ssl/ssl_info.h"
+#include "url/gurl.h"
 
 class Pickle;
 
@@ -93,6 +94,12 @@ class NET_EXPORT HttpResponseInfo {
   // Whether the request use http proxy or server authentication.
   bool did_use_http_auth;
 
+  // True if the request was fetched by a ServiceWorker.
+  bool was_fetched_via_service_worker;
+  // The original URL of the repsponse which was fetched by the ServiceWorker.
+  // This may be empty if the repsponse was created inside the ServiceWorker.
+  GURL original_url_via_service_worker;

[michaeln, 2014/07/15 23:16:38]

These service_worker specific data members probably don't belong in the lower
level networking library.

The content library associates extra data with each URLRequest, that extra data
is an instance of ServiceWorkerRequestHandler. These values could be added to
that set of extra data and retrieved from there when sending a ResourceResponse
back to a renderer.

Some pointers...

See ServiceWorkerRequestHandler::GetHandler(request).

See PopulateResourceResponse(...) in resource_loader.cc and notice how
AppCacheInterceptor::GetExtraResponseInfo() is used in that function.

I think we could similarly use a method like
ServiceWorkerRequestHandler::GetHandler()->GetExtraResponseInfo(...) for the
serviceworker's extra data.

+
   // Remote address of the socket which fetched this resource.
   //
   // NOTE: If the response was served from the cache (was_cached is true),