I wish you could edit the original post.

> Did this work before? Yes

kris.selden@ Thanks for the issue.

Tested this issue on Mac OS 10.12.6, Windows 10 and Ubuntu 14.04 on the latest Canary 66.0.3358.0 and latest Beta 65.0.3325.106 and able to reproduce the issue by following the steps mentioned above.

Bisect Information:
===================
Good Build: 65.0.3295.0 (Revision - 524284)
Bad Build : 65.0.3296.0 (Revision - 524554)

On executing the per-revision bisect script, below is the Changelog URL:

https://chromium.googlesource.com/chromium/src/+log/6b6934dae35ce8c54ace157f0892079908d88175..a09615be2b58d4b1a0fe1f4c6eabb782ea640b3d

From the above Changelog, suspecting the below change:
Reviewed-on: https://chromium-review.googlesource.com/826710

pfeldman@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner.

Adding ReleaseBlock-Stable as this is a recent regression. Please feel free to remove it if it is not applicable.

Thanks.

Seems like original bug is reported on M64. Does this repro on M64? 

Unfortunately yes it is in 64, I noticed it while it was in Canary and meant to report it, but lost track of it, then when it was released, my benchmarking work flow involves taking HAR recordings in the DevTools I was bummed I forgot to report it earlier.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9d2e70dbef548b2d6bff1952c75b56e6419300fd

commit 9d2e70dbef548b2d6bff1952c75b56e6419300fd
Author: Eugene Ostroukhov <eostroukhov@chromium.org>
Date: Tue Mar 06 21:29:07 2018

DevTools: Parse date passed to Cookie::expiresDate

Bug:  817970 
Change-Id: Ia7f3ccacf3231011e7955cee4766035e481b72be
Reviewed-on: https://chromium-review.googlesource.com/947255
Commit-Queue: Eugene Ostroukhov <eostroukhov@chromium.org>
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541196}
[modify] https://crrev.com/9d2e70dbef548b2d6bff1952c75b56e6419300fd/third_party/WebKit/Source/devtools/front_end/browser_sdk/HAREntry.js

Thank you!

 Issue 827192  has been merged into this issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/5564c2dd5b32a8d34a6017f736c02738d4f7feaa

commit 5564c2dd5b32a8d34a6017f736c02738d4f7feaa
Author: Eugene Ostroukhov <eostroukhov@chromium.org>
Date: Mon Apr 02 17:56:14 2018

DevTools: Parse date passed to Cookie::expiresDate

TBR=eostroukhov@chromium.org

(cherry picked from commit 9d2e70dbef548b2d6bff1952c75b56e6419300fd)

Bug:  817970 
Change-Id: Ia7f3ccacf3231011e7955cee4766035e481b72be
Reviewed-on: https://chromium-review.googlesource.com/947255
Commit-Queue: Eugene Ostroukhov <eostroukhov@chromium.org>
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#541196}
Reviewed-on: https://chromium-review.googlesource.com/990197
Reviewed-by: Eugene Ostroukhov <eostroukhov@chromium.org>
Cr-Commit-Position: refs/branch-heads/3359@{#528}
Cr-Branched-From: 66afc5e5d10127546cc4b98b9117aff588b5e66b-refs/heads/master@{#540276}
[modify] https://crrev.com/5564c2dd5b32a8d34a6017f736c02738d4f7feaa/third_party/WebKit/Source/devtools/front_end/browser_sdk/HAREntry.js

 Issue 823253  has been merged into this issue.

 Issue 826250  has been merged into this issue.

Verified the fix on Mac 10.13.1, Windows-10 and Ubuntu 14.04 using Chrome version #66.0.3359.81 as per the comment #0.
Attaching screen shot for reference.
Observed the HAR file saved with content.
Hence, the fix is working as expected. 
Adding the verified labels.
Note: Able to reproduce the issue on chrome version with out fix.

Thanks...!!

Deleted: CL Verif LinkedIn.png 1.3 MB

	CL Verif LinkedIn.png 1.3 MB View Download

 Issue 801306  has been merged into this issue.