Hi Senthill,
the bug 1167080 is fixed and the patch landed in Firefox Nightly build
There is also another patch (in Nightly) that allows manual export
of Network panel data (as HAR).

So, there are two options now.

1) you can manually export HAR data from the Network panel using
the panel’s context menu and “Copy all as HAR” (to the clipboard)
or “Save all as HAR” (to a file)

2) you can also set a preference to export content of the 
panel automatically (after the page has been loaded)

Enable automation:
devtools.netmonitor.har.enableAutoExportToFil

Include response bodies in the HAR File (can make it significantly bigger):
devtools.netmonitor.har.includeResponseBodies


There are no API exposed to the content (security issues), but
standard Firefox extensions are able to access the existing
platform (DevTools) API and trigger the export at any custom time.

Let me know if you are interested in building such custom extension
I can help you with that.

Honza


> On 23 Jun 2015, at 02:22, Senthil <[email protected]> wrote:
> 
> Hi Honza,
> What is the status of the "HAR Export Automation" with Firefox NetPanel?
> 
> I was looking at the bug https://bugzilla.mozilla.org/show_bug.cgi?id=1167080 
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1167080> and the conversation 
> centered around the security of exposing JS calls to content. Without JS 
> calls exposed to user, is there anyother way of exporting har?
> 
> Is this feature getting into Firefox network panel? Will we be able to export 
> the HAR via automation or only manual "save as har" is available? Please 
> clarify.
> 
> Thanks
> Senthil.
> 
> On Thursday, May 28, 2015 at 6:09:27 PM UTC+5:30, Jan Honza Odvarko wrote:
> 
> 
> On Thursday, May 28, 2015 at 12:58:44 PM UTC+2, Senthil wrote:
> Getting HAR data as a string works for me - I think having it minimal is the 
> best case scenario for everyone - it just does what it is supposed to do 
> (clear and trigger).
> 
> It also gives me the flexibility to store har with all the additional info 
> that I may want to add.
> Great!
> 
> What do you think about the suggested "HARPageLoaded" event? (fired when all 
> requests executed during the page load are finished)
> 
> I still feel like this is needed - in order to know when to trigger the 
> export. But, looks like it is isn't?
> (you might want to read the discussion above)
> 
> Honza
>  
> 
> Hoping to get my hands on it soon - let us know when it is in nightly. 
> Will check it out and get back.
> 
> Thanks.
> 
> On Wednesday, May 27, 2015 at 3:19:36 PM UTC+5:30, Jan Honza Odvarko wrote:
> 
> 
> On Wednesday, May 27, 2015 at 10:31:01 AM UTC+2, Senthil wrote:
> Now I read the Firefox bug, I understand that Har export is becoming part of 
> Firefox.
> 
> Since it is going to be lightweight, do we have options for sending beacons - 
> if not, can you spin out the code that you've written in FBug 3.0 to a new 
> extension which can publish the har to a URL on "HARPageLoaded" or Manual 
> trigger.
> 
> My earlier request to add headers will fall here - it should not be part of 
> the firefox browser.
> 
> Thanks
> Senthil.
> 
> On Wednesday, May 27, 2015 at 12:31:37 PM UTC+5:30, Senthil wrote:
> 1. What do you mean by saying "extensions not needed anymore" ->  "Har 
> Export" is part of Firebug 3.0 or Firefox network panel??
> 
> 2. I have been using Netexport with Selenium and I find "triggerExport" and 
> "clear" events good enough to automate the page.
> Yes, precisely, I also think that having HAR API available in the content is 
> enough for the automation. It's relatively simple to provide them and it's 
> quite flexible at the same time.
>  
> 
> 2.5  I would REQUEST ability to add headers to the beacon URL when export is 
> triggered (***important***) - I would want to send info about buildid, runid 
> as part of the header while keeping the beacon url intact
> The current API design allows to get just the HAR source (without storing it 
> into a local file). See an example:
> 
> var options = { getData: true };
> HAR.triggerExport(options).then(function(result) {
>   var har = result.data;
> 
>   // The har variable contains a HAR string (JSON) with
>   // all Network panel data included. An automated tool can
>   // parse/process the string, append any additional information
>   // and eventually sent/store anywhere where the tool has access to.
> });
> 
> So, the automation tool can get the HAR data, customize them and sent 
> anywhere you want.
> Would this work for you?
> 
>  
> 
> 3. "HARPageLoaded" would be a nice addition - WILL user be allowed to 
> configure the time period (1000 ms or 5000) after which the event will be 
> fired??
> See the thread above. Ahmad is suggesting that the event is unnecessary and 
> it's up to the automation tool to trigger the export at the right time. It 
> make sense to me, the actual logic that says when to trigger the export can 
> vary from case to case and it looks like responsibility of the tool.
>  
> 
> And thanks for HAR and HAR Export - It is helping me a lot with my work.
> Excellent!
> 
> Honza 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Firebug" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> To post to this group, send email to [email protected] 
> <mailto:[email protected]>.
> Visit this group at http://groups.google.com/group/firebug 
> <http://groups.google.com/group/firebug>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/firebug/dd88bc69-80eb-4de0-ae41-f8b64a6f640d%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/firebug/dd88bc69-80eb-4de0-ae41-f8b64a6f640d%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups 
"Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/firebug.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/firebug/3B00F854-79D8-449E-9496-0B5C95122B5E%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to