For some more insight how the permission api operates these days:
https://bugzilla.mozilla.org/show_bug.cgi?id=1479347
FRG
EE wrote:
xxyyz wrote:
On 2018-08-08 2:01 PM, EE wrote:
xxyyz wrote:
On 2018-08-04 2:32 PM, David E. Ross wrote:
On 8/4/2018 10:09 AM, xxyyz wrote:
If I block all cookies (Preferences/Privacy & Security\Cookies/
Block cookies), then allow session cookies from https://aaa.bbb
(in chrome://communicator/content/permissions/cookieViewer.xul),
are session cookies allowed from https://xxx.aaa.bbb?
I use the following strategy. I do not block all cookies. Instead, I
allow cookies only from the domain of the Web site I requested. I
have
also blocked cookies from selected Web sites, primarily advertising
sites that might have cookies set by my select Web sites.
The key is that I located the file cookies.sqlite in my profile and
marked it as read-only. All the cookies that get set as I surf the
Web
are lost as soon as I terminate SeaMonkey. That is, all of those
cookies are treated as session-only.
Sometimes, however, I want to keep a cookie. Fortunately, that
does not
often happen because the process is somewhat cumbersome. To see my
process, go to <http://www.rossde.com/internet/cookies.html#doabout>.
Thank you for the response - but I'm asking a very basic question:
Does allowing cookies from a specific site allow cookies from
"subsidiary" sites? Same question when blocking cookies.
If you allow cookies from the second level domain, then they would be
allowed from one of its specific third level domains as well.
Thank you. Does the reverse apply - i.e. if I allow cookies from a
specific third level domain, are they allowed from the second level
domain?
No, not normally, unless you use a cookie handling extension that
specifically allows that. For my part, there is no way I want that to
happen with a big domain.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
