Expose receive header end time for URLRequestRedirectJob

net/url_request/url_request_redirect_job.cc

Index: net/url_request/url_request_redirect_job.cc
diff --git a/net/url_request/url_request_redirect_job.cc b/net/url_request/url_request_redirect_job.cc
index a4b0dfba82748f8965279d1880ced30d23d6e2c0..2b2e90d4766aefd3581902927bae72d33f696bbb 100644
--- a/net/url_request/url_request_redirect_job.cc
+++ b/net/url_request/url_request_redirect_job.cc
@@ -7,6 +7,7 @@
 #include "base/bind.h"
 #include "base/compiler_specific.h"
 #include "base/message_loop.h"
+#include "net/base/load_timing_info.h"
 
 namespace net {
 
@@ -36,7 +37,13 @@ bool URLRequestRedirectJob::IsRedirectResponse(GURL* location,
 URLRequestRedirectJob::~URLRequestRedirectJob() {}
 
 void URLRequestRedirectJob::StartAsync() {
+  receive_headers_end_ = base::TimeTicks::Now();
   NotifyHeadersComplete();
 }
 
+void URLRequestRedirectJob::GetLoadTimingInfo(
+    LoadTimingInfo* load_timing_info) const {
+  load_timing_info->receive_headers_end = receive_headers_end_;

[mmenke, 2013/06/24 13:58:19]

Hmm...  Would it be more consistent with the spec to also set send start and
send stop times to be this time as well?  Seems like that would more closely
mirror cache behavior, though perhaps they should technically be when we
started/stopped checking the HSTS list.

+}
+
 }  // namespace net