netwerk/cookie - mozsearch

firefox-main/netwerk/cookie

	Name	Description	Size	Coverage
	components.conf		936	-
	Cookie.cpp	Cookie: creation helper ****************************************************************************	10055	0 %
	Cookie.h	The Cookie class is the main cookie storage medium for use within cookie code.	6711	38 %
	CookieCommons.cpp		36372	0 %
	CookieCommons.h		7831	-
	CookieDBWriteQueue.cpp		5431	0 %
	CookieDBWriteQueue.h		2530	0 %
	CookieDummyStorage.h		1537	0 %
	CookieJarSettings.cpp	shouldResistFingerprinting	24112	0 %
	CookieJarSettings.h	CookieJarSettings ~~~~~~~~~~~~~~ CookieJarSettings is a snapshot of the cookie jar's configurations in a precise moment of time, such as the cookie policy and cookie permissions. This object is used by top-level documents to have a consistent cookie jar configuration also in case the user changes it. New configurations will apply only to new top-level documents. CookieJarSettings creation ~~~~~~~~~~~~~~~~~~~~~~~ CookieJarSettings is created when the top-level document's nsIChannel's nsILoadInfo is constructed. Any sub-resource and any sub-document inherits it from that nsILoadInfo. Also dedicated workers and their resources inherit it from the parent document. SharedWorkers and ServiceWorkers have their own CookieJarSettings because they don't have a single parent document (SharedWorkers could have more than one, ServiceWorkers have none). In Chrome code, we have a new CookieJarSettings when we download resources via 'Save-as...' and we also have a new CookieJarSettings for favicon downloading. Content-scripts WebExtensions also have their own CookieJarSettings because they don't have a direct access to the document they are running into. Anything else will have a special CookieJarSettings which blocks everything (CookieJarSettings::GetBlockingAll()) by forcing BEHAVIOR_REJECT as policy. When this happens, that context will not have access to the cookie jar and no cookies are sent or received. Propagation of CookieJarSettings ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CookieJarSettings are shared inside the same top-level document via its nsIChannel's nsILoadInfo. This is done automatically if you pass a nsINode to NS_NewChannel(), and it must be done manually if you use a different channel constructor. For instance, this happens for any worker networking operation. We use the same CookieJarSettings for any resource belonging to the top-level document even if cross-origin. This makes the browser behave consistently a scenario where A loads B which loads A again, and cookie policy/permission changes in the meantime. Cookie Permissions propagation ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CookieJarSettings populates the known cookie permissions only when required. Initially the list is empty, but when CookieJarSettings::CookiePermission() is called, the requested permission is stored in the internal list if it doesn't exist yet. This is actually nice because it relies on the permission propagation from parent to content process. No extra IPC is required. Note that we store permissions with UNKNOWN_ACTION values too because they can be set after the loading of the top-level document and we don't want to return a different value when this happens. Use of CookieJarSettings ~~~~~~~~~~~~~~~~~~~~~ In theory, there should not be direct access to cookie permissions or cookieBehavior pref. Everything should pass through CookieJarSettings. A reference to CookieJarSettings can be obtained from nsILoadInfo::GetCookieJarSettings(), from Document::CookieJarSettings() and from the WorkerPrivate::CookieJarSettings(). CookieJarSettings is thread-safe, but the permission list must be touched only on the main-thread. Testing ~~~~~~~ If you need to test the changing of cookie policy or a cookie permission, you need to workaround CookieJarSettings. This can be done opening a new window and running the test into that new global.	12126	100 %
	CookieKey.h		1642	56 %
	CookieLogging.cpp		6771	0 %
	CookieLogging.h		1989	-
	CookieNotification.cpp		1811	0 %
	CookieNotification.h		1723	0 %
	CookieParser.cpp		26617	0 %
	CookieParser.h		3429	0 %
	CookiePersistentStorage.cpp		93103	0 %
	CookiePersistentStorage.h		5382	0 %
	CookiePrefixes.cpp		3720	0 %
	CookiePrefixes.h		1061	-
	CookiePrivateStorage.cpp		1346	0 %
	CookiePrivateStorage.h		1579	0 %
	CookieService.cpp	Enables sanitizeOnShutdown cleaning prefs and disables the network.cookie.lifetimePolicy	64936	0 %
	CookieService.h	CookieService: class declaration ****************************************************************************	6092	67 %
	CookieServiceChild.cpp		20191	0 %
	CookieServiceChild.h		2887	0 %
	CookieServiceParent.cpp		15288	0 %
	CookieServiceParent.h		4212	87 %
	CookieStorage.cpp		46324	0 %
	CookieStorage.h		10249	67 %
	CookieValidation.cpp		17874	0 %
	CookieValidation.h		3506	38 %
	CookieXPCShellUtils.sys.mjs		1670	-
	moz.build		2244	-
	nsICookie.idl	Main cookie object interface.	4835	-
	nsICookieJarSettings.idl	Cookie jar settings for top-level documents. Please see CookieJarSettings.h for more details.	2921	-
	nsICookieManager.idl	An optional interface for accessing or removing the cookies that are in the cookie list. Expired cookies are never exposed by the getters of this interface, even if they have not been purged yet.	13716	-
	nsICookieNotification.idl	Meta object dispatched by cookie change notifications.	2666	-
	nsICookiePermission.idl	An interface to test for cookie permissions	1102	-
	nsICookieService.idl	nsICookieService Provides methods for setting and getting cookies in the context of a page load. See nsICookieManager for methods to manipulate the cookie database directly. This separation of interface is mainly historical. This service broadcasts the notifications detailed below when the cookie list is changed, or a cookie is rejected. NOTE: observers of these notifications must not attempt to change profile or switch into or out of private browsing mode from within the observer. Doing so will cause undefined behavior. Mutating the cookie list (e.g. by calling methods on nsICookieService and friends) is allowed, but beware that there may be pending notifications you haven't seen yet -- for instance, a COOKIES_BATCH_DELETED notification will likely be immediately followed by COOKIE_ADDED. You may check the state of the cookie list to determine if this is the case. topic : "cookie-changed" broadcast whenever the cookie list changes in some way. see explanation of data strings below. subject: The cookie notification. See nsICookieNotification for details. data : none. For possible actions see nsICookieNotification_Action. topic : "cookie-rejected" broadcast whenever a cookie was rejected from being set as a result of user prefs. subject: an nsIURI interface pointer representing the URI that attempted to set the cookie. data : none.	6493	-
	nsICookieValidation.idl		1059	-
	nsIThirdPartyCookieBlockingExceptionListService.idl	Helper for syncing remote exception lists for third-party cookie blocking.	1302	-
	PCookieService.ipdl	PCookieService Provides IPDL methods for setting and getting cookies. These are stored on and managed by the parent; the child process goes through the parent for all cookie operations. Lower-level programmatic operations (i.e. those provided by the nsICookieManager interface) are not currently implemented and requesting these interfaces in the child will fail. @see nsICookieService @see nsICookiePermission	2480	-
	PrefetchCookieCopier.cpp		969	0 %
	PrefetchCookieCopier.h		1384	-
<1%	test			-
	ThirdPartyCookieBlockingExceptionListService.sys.mjs	Manages the list of (first-party site, third-party site) pairs that are exempt from third-party cookie blocking, sourced from both Remote Settings and a user pref.	7396	87 %
	ThirdPartyCookieBlockingExceptions.cpp		6224	0 %
	ThirdPartyCookieBlockingExceptions.h		2469	0 %

Revision control

Other Tools