Browse Source

fix User header and character set issue

Bill Gianopoulos 3 months ago
parent
commit
3bd08a89b6
1 changed files with 3 additions and 2 deletions
  1. 3 2
      mozilla-release/patches/1423495-4no5-61a1.patch

+ 3 - 2
mozilla-release/patches/1423495-4no5-61a1.patch

@@ -1,13 +1,14 @@
 # HG changeset patch
 # HG changeset patch
-# User Kershaw Chang <kechang@mozilla.com>, Valentin Gosu <valentin.gosu@gmail.com>
+# User Kershaw Chang <kechang@mozilla.com>
 # Date 1515723180 -3600
 # Date 1515723180 -3600
 #      Fri Jan 12 03:13:00 2018 +0100
 #      Fri Jan 12 03:13:00 2018 +0100
 # Node ID 11804549931f5e8e2e71c5bcdd3221b41e8d54d8
 # Node ID 11804549931f5e8e2e71c5bcdd3221b41e8d54d8
 # Parent  5d9495a52eb69317db7add55a510f53b3a2de8fa
 # Parent  5d9495a52eb69317db7add55a510f53b3a2de8fa
 Bug 1423495 - Part4: Create doc entry form http channel if server timing headers are found for a document load r=baku
 Bug 1423495 - Part4: Create doc entry form http channel if server timing headers are found for a document load r=baku
 
 
+ALos credit to Valentin Gosu <valentin.gosu@gmail.com>
 Currently, the document entry is created at the first time when some JS code tries to access it. But for the case when server timing headers exist for a document loading channel, we need to create the document entry and save the server timing data in the document entry.
 Currently, the document entry is created at the first time when some JS code tries to access it. But for the case when server timing headers exist for a document loading channel, we need to create the document entry and save the server timing data in the document entry.
-If we dont do this, the server timing data would be lost since the http channel will be deleted.
+If we don't do this, the server timing data would be lost since the http channel will be deleted.
 
 
 MozReview-Commit-ID: B5ksAZvZACq
 MozReview-Commit-ID: B5ksAZvZACq