Posted as http://code.google.com/p/fbug/issues/detail?id=3367.  Please
let me know if you need more or would like additional information.

On Aug 20, 4:33 am, "Honza (Jan Odvarko)" <[email protected]> wrote:
> Looks like a bug, could you please create a new report for it,
> so it's not forgotten here in the 
> noise?http://code.google.com/p/fbug/issues/list
>
> Thanks!
> Honza
>
> On Aug 20, 2:16 am, Aaron Kulick <[email protected]> wrote:
>
> > I apologize in advance if this is refried.
>
> > I have been using the latest release ofNetExport(0.8b4) which
> > currently is still using the 1.1 HAR Spec and I have noticed a
> > discrepancy between what the HAR file includes as cookies and what the
> > browser reports via Firecookie.  For pages that make continuous XHR
> > calls I simply manually export the HAR as the "Load" event never
> > fires.  My scenario follows below:
>
> > With a completely empty history, cache, and cookies while running the
> > NET panel I have found pages that when exported (automatically or
> > manually), the resulting HAR file consistently fails to report or even
> > allude to cookies that are otherwise exportable through Firecookie for
> > the page in question.  I am wondering what the source of the
> > discrepancy is, whether the issue would be resolved with the
> > implementation of HAR 1.2 inNetExportor if these particular calls
> > simply cannot be trapped by the NET panel and subsequently escape
> > detection.
>
> > Here is an example URL:
>
> >http://www.cnet.com/apple-iphone.html
>
> > If the page is allowed to "run" for a bit and then the HAR exported
> > manually the following cookie is never reported:__utmc=<data>; path=/;
> > domain=.widget.collecta.com
>
> > Thank you,
>
> > Aaron Kulick

-- 
You received this message because you are subscribed to the Google Groups 
"Firebug" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/firebug?hl=en.

Reply via email to