Issue metadata
Sign in to add a comment
|
Cannot save as HAR with content on remote debugging
Reported by
ducbuiho...@gmail.com,
Mar 19 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36 Steps to reproduce the problem: 1. Chrome on Mac version: 65.0.3325.162 2. Chrome on Android version: 65.0.3325.109 3. Open remote debugging on Android 4. Inspect a tab on Chrome on Android, URL: www.wsj.com 5. Open Network tab on DevTools 6. Reload to record the network activity (with or without "preserved log") 7. Click on "Save as HAR with content" on the DevTool What is the expected behavior? HAR file is saved What went wrong? While an empty HAR file is created, DevTools is stuck at "Collecting content..." and never finish Did this work before? N/A Chrome version: 65.0.3325.162 Channel: stable OS Version: OS X 10.13.3 Flash Version: The above steps succeed when I use Canary on Mac (67.0.3375.0) to remote debug Canary on Android (67.0.3375.0).
,
Mar 19 2018
I even cannot record to HAR files locally (no remote debugging), for cnn.com.
,
Mar 19 2018
,
Mar 19 2018
I'm seeing this as well when I try to use the network.getHar() function or the network.onRequestFinished.addListener() function. Unfortunately it's breaking my company's ad debugging plugin. It seems the NetworkLog.HARLog.pseudoWallTime() is returning a date String rather than a Date. Then the expiresDate function in SDK.Cookie calls getTime() on that string and throws an error.
,
Mar 22 2018
I cannot store HAR files locally.
,
Mar 25 2018
I see this in an extension that uses HAR. It stopped working after update to Chrome 65. I can see the same issue in the extension's console: 'targetDate.getTime is not a function TypeError: targetDate.getTime is not a function'.
Here's the call stack:
TypeError: targetDate.getTime is not a function TypeError: targetDate.getTime is not a function
at SDK.Cookie.expiresDate (inspector.js:formatted:26314)
at NetworkLog.HAREntry._buildCookie (inspector.js:formatted:39337)
at Array.map (<anonymous>)
at NetworkLog.HAREntry._buildCookies (inspector.js:formatted:39329)
at NetworkLog.HAREntry._buildResponse (inspector.js:formatted:39237)
at NetworkLog.HAREntry.build (inspector.js:formatted:39200)
at Extensions.ExtensionServer._notifyRequestFinished (inspector.js:formatted:46148)
at SDK.NetworkManager.dispatchEventToListeners (inspector.js:formatted:6543)
at SDK.NetworkDispatcher._finishNetworkRequest (inspector.js:formatted:36654)
at SDK.NetworkDispatcher.loadingFinished (inspector.js:formatted:36537)
This issue seems to be happening because the argument 'requestDate' passed to the function SDK.Cookie.expiresDate is a date string and not a date object.
,
Mar 30 2018
Am seeing this as well when using chrome.devtools.network.onRequestFinished.addListener in an extension.
,
Apr 2 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ducbuiho...@gmail.com
, Mar 19 2018