ServiceWorker: support Request.{url,method,origin,headers} [chromium] (2/3)

content/test/data/service_worker/fetch_event.js

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
+function getSortedHeaderString(headers) {
+    var requestHeaders = [];
+    headers.forEach(function(value, key) {
+        requestHeaders.push(key + ': ' + value + '\n');
+    });
+    requestHeaders.sort();
+    var requestHeaderString = '';
+    requestHeaders.forEach(function(header) {
+        requestHeaderString += header;
+    });
+    return requestHeaderString;
+}
+
 this.onfetch = function(event) {
     var headers = new HeaderMap;
     headers.set('Content-Language', 'fi');
     headers.set('Content-Type', 'text/html; charset=UTF-8');
+    headers.set('X-ServiceWorker-Test-RequestURL', event.request.url);
+    headers.set('X-ServiceWorker-Test-RequestMethod', event.request.method);
+    headers.set('X-ServiceWorker-Test-RequestOrigin', event.request.origin);
+    headers.set('X-ServiceWorker-Test-RequestHeaders',
+                getSortedHeaderString(event.request.headers));

[falken, 2014/05/30 03:39:17]

I'm not sure I understand this. Why do we add request headers to the response?

[horo, 2014/05/30 04:55:18]

It was intended to make it possible to check the value of event.request in the
browser test.
But I reverted the changes for browser tests.

+
     var response = new Response({
         status: 301,
         statusText: 'Moved Permanently',
         headers: headers
     });
 
     event.respondWith(new Promise(function(r) {
         setTimeout(function() { r(response); }, 5);
     }));
 };