This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

viewing, saving, and deleting cookies

  • 1 reply
  • 0 have this problem
  • 19 views
  • Last reply by cor-el

more options

This is just a complaint . . . Settings>Cookies and Site Data>Manage Data does not show the server that set a cookie, it only shows the domain -- e.g. domain.com, not https://www.domain.com or even www.domain.com However, Settings>Cookies and Site Data>Manage Exceptions requires the complete server name. If I don't include "https://" or "http://" it adds them. This makes it difficult or impossible to actually manage exceptions; I can't specify which cookie(s) I want to allow, block, or save if I can't see the data that's stored.

Why can't I choose a domain in Manage Data and get a Manage Exceptions pop-up?

This is just a complaint . . . Settings>Cookies and Site Data>Manage Data does not show the server that set a cookie, it only shows the domain -- e.g. domain.com, not https://www.domain.com or even www.domain.com However, Settings>Cookies and Site Data>Manage Exceptions requires the complete server name. If I don't include "https://" or "http://" it adds them. This makes it difficult or impossible to actually manage exceptions; I can't specify which cookie(s) I want to allow, block, or save if I can't see the data that's stored. Why can't I choose a domain in Manage Data and get a Manage Exceptions pop-up?

All Replies (1)

more options

"Cookies and Site Data" -> "Manage Data" shows info about all cookies used on a specific domain. You can use the Storage Inspector for more detail about individual cookies.

Exceptions work by origin (protocol and hostname) and can be more precise (i.e. you can specify a sub domain like .www) but you can't include a path. If you specify a domain then sub domains are included and this might be necessary if webpages use various sub domains like login pages do in a lot of cases like for Google you may need an allow exception for https://google.com.