[Webkit-unassigned] [Bug 16531] Show cookie data in the request headers in network pane

Mon May 17 22:34:33 PDT 2010

https://bugs.webkit.org/show_bug.cgi?id=16531

Tauren Mills <tauren at groovee.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tauren at groovee.com

--- Comment #6 from Tauren Mills <tauren at groovee.com>  2010-05-17 22:34:33 PST ---

(In reply to comment #2)
> Now that we have a Cookie storage view, is this enough to have here, or should there be more?

I was told that my post on the Chromium group relates to this issue.
http://groups.google.com/a/chromium.org/group/chromium-discuss/browse_thread/thread/c44361ebe6e03184#

Personally, I think that showing cookie information in the Resource tab is very important, and that it shouldn't only be available in the Cookie storage view. I'm not familiar with WebKit besides using Chrome, but I'm assuming this is referring to the "Cookies and Other Data" dialog.

I don't understand why cookies would not be included with the Request Headers and Response Headers in Developer Tools so that developers can get a very clear picture of everything related to a request. When debugging a cookie related problem, it is extremely cumbersome to have to go into a separate location to view cookie details. Having an indicator showing when a new cookie is set would be nice (perhaps bold it or something).

Also, the separate cookie storage view simply shows the state of cookies at a certain point in time - when you look at it. It doesn't give you an easy way to see which request received a cookie, or which ones sent a cookie. For instance, if there are a series of ajax requests, one of which receives a cookie, and the following ones send the cookie, it would be hard to determine which ones used cookies and which didn't.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.