Avatar for Username

Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

Bu başlık arşivlendi. Yardıma ihtiyacınız varsa lütfen yeni bir soru sorun.

viewing, saving, and deleting cookies

  • 1 yanıt
  • 0 kişi bu sorunu yaşıyor
  • 19 gösterim
  • Son yanıtı yazan: cor-el

whatsit1
whatsit1
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?

Tüm Yanıtlar (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
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.