Properly store cookies in internal Net panel data structure
Categories
(DevTools :: Netmonitor, task, P3)
Tracking
(Not tracked)
People
(Reporter: Honza, Unassigned, Mentored)
Details
Attachments
(2 files)
6.94 KB,
patch
|
Details | Diff | Splinter Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
Reporter | ||
Updated•7 years ago
|
Reporter | ||
Updated•7 years ago
|
Reporter | ||
Comment 2•7 years ago
|
||
Updated•7 years ago
|
Reporter | ||
Updated•7 years ago
|
Comment 3•7 years ago
|
||
Reporter | ||
Comment 4•7 years ago
|
||
Comment 5•7 years ago
|
||
Comment 6•6 years ago
|
||
Hi I would like to work on it , can I take this up?
Updated•6 years ago
|
Comment 7•6 years ago
|
||
Hi Shivam
Thanks for your interest! I'm in the midst of helping to resolve this bug as it might seem more involved than expected. There are a few other good bugs to work on :)
Comment 8•6 years ago
|
||
It looks like the problem is related to how fetched cookies (from the backend) are initially stored in the FirefoxDataProvider. This should be investigated first.
Hi Honza
So I did some investigation on how fetched cookies are initially stored in FirefoxDataProvider. Here are my findings so far.
-
Panels like
CookiesPanel
,RequestListColumnCookies
andRequestListColumnSetCookies
would call the requestData method inFirefoxDataProvider
to get the request/response cookies. -
The internal helper _requestData method is called to fetch HTTP details from the backend.
-
The initial
response
is stored here. This function is responsible for fetching the initialresponse
. An example function that it triggers is here. -
From then on, this
response
variable returned would be used throughout the network request. For example, theresponse
is passed into the callback method likeonRequestCookies
to process.
Judging from step 3, this problem looks like it escalates out of the scope of the netmonitor. Would like your input on this.
Reporter | ||
Comment 9•6 years ago
|
||
I don't have enough cycles to work on this, so removing the current assignee and hoping that we can get back to this soon.
Honza
Reporter | ||
Updated•4 years ago
|
Comment 10•4 years ago
|
||
(In reply to Jan Honza Odvarko [:Honza] (always need-info? me) from comment #9)
Hello< can I work on this?
Reporter | ||
Comment 11•4 years ago
|
||
Bomsy, I am unsure whether this is a good first bug (and also whether we still have the original problem)
Comment 12•4 years ago
|
||
Bomsy, I am unsure whether this is a good first bug (and also whether we still have the original problem)
Having a quick look,
I think this is nice to cleanup and not have one consistent way for cookies
Here are a couple of places this might be set wrong
https://searchfox.org/mozilla-central/rev/46ff2252568db36e811109fa4026c8e3c12e9ee1/devtools/client/netmonitor/src/har/har-importer.js#78-79
https://searchfox.org/mozilla-central/rev/46ff2252568db36e811109fa4026c8e3c12e9ee1/devtools/client/netmonitor/src/connector/firefox-data-provider.js#234,259
This seems delicate, and is more involved and I'm not sure how much test coverage we have on this to make sure we do not regress any thing.
Might be more of a good mentored bug.
Some one with a bit of knowledge of the codebase could take a stab at it.
Comment 13•3 years ago
|
||
Depends on D128670
Updated•3 years ago
|
Updated•3 years ago
|
Comment 14•3 years ago
|
||
This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit auto_nag documentation.
Comment 15•3 years ago
|
||
Hi Jan
I would like to take-up this issue. Could you please assign it to me?
Reporter | ||
Comment 16•3 years ago
|
||
Let me first ask Bomsy, whether this bug is still valid. We've made a lot of changes in the code base to make it Fission compatible and I am not sure whether this report still makes sense.
Bomsy, WDYT?
Updated•3 years ago
|
Comment 18•3 years ago
|
||
Hi Abhinav,
Sorry for the late reply. This involves a little bit more investigation and there's already a patch provided that need's review.
i think we can find you some other issue for you to look at.
Thanks
Updated•3 years ago
|
Comment 19•3 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Reporter | ||
Updated•3 years ago
|
Description
•