From 4aed2c8219774f5d797760606b8489a92ddc5163 Mon Sep 17 00:00:00 2001 From: toma Date: Wed, 25 Nov 2009 17:56:58 +0000 Subject: Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. BUG:215923 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdebase@1054174 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- doc/kcontrol/cookies/Makefile.am | 2 + doc/kcontrol/cookies/index.docbook | 211 +++++++++++++++++++++++++++++++++++++ 2 files changed, 213 insertions(+) create mode 100644 doc/kcontrol/cookies/Makefile.am create mode 100644 doc/kcontrol/cookies/index.docbook (limited to 'doc/kcontrol/cookies') diff --git a/doc/kcontrol/cookies/Makefile.am b/doc/kcontrol/cookies/Makefile.am new file mode 100644 index 000000000..ed988eefc --- /dev/null +++ b/doc/kcontrol/cookies/Makefile.am @@ -0,0 +1,2 @@ +KDE_LANG = en +KDE_DOCS = kcontrol/cookies diff --git a/doc/kcontrol/cookies/index.docbook b/doc/kcontrol/cookies/index.docbook new file mode 100644 index 000000000..a1ea6fdd7 --- /dev/null +++ b/doc/kcontrol/cookies/index.docbook @@ -0,0 +1,211 @@ + + + +]> + +
+ + + +&Krishna.Tateneni; &Krishna.Tateneni.mail; +&Jost.Schenck; &Jost.Schenck.mail; + + + +2003-10-12 +3.2 + + +KDE +KControl +cookie + + + + + +Cookies + +Cookies are a mechanism used by web sites to store and retrieve +information using your browser. For example, a web site may allow you +to customize the content and layout of the pages you see, so that your +choices are persistent across different visits to that web site. + +The web site is able to remember your preferences by storing a +cookie on your computer. Then, on future visits, the web site retrieves +the information stored in the cookie to format the content of the site +according to your previously specified preferences. + +Thus, cookies play a very useful role in web browsing. +Unfortunately, web sites often store and retrieve information in cookies +without your explicit knowledge or consent. Some of this information may +be quite useful to the web site owners, for example, by allowing them to +collect summary statistics on the number of visits different areas of +the web sites get, or to customize banner advertising. + +The cookies module of the &kcontrol; allows you to set policies +for the use of cookies when you are browsing the web with the +&konqueror; web browser. + +Note that the policies that you set using this control +module will not apply to other web browsers such +as &Netscape;. + + + +Policy + +Using the Policy tab, you can configure the +&kde; applications that will handle cookies. You can do this by specifying a +general cookie policy as well as special cookie policies for certain +domains or hosts. + +The top of the policy tab has a checkbox labeled Enable +cookies. If you leave this unchecked, cookies will be +completely disabled. However, this may make browsing rather +inconvenient, especially as some web sites require the use of browsers +with cookies enabled. + +You will probably want to enable cookies and then set +specific policies on how you want them to be handled. + +The first group of options create settings that apply to all cookies. + + + +Only accept cookies from originating server + +Some pages try to set cookies from servers other than the one +you are seeing the HTML page from. For example, +they show you advertisements, and the advertisements are from another +computer, often one that belongs to a large advertising group. These +advertisements may try to set a cookie which would allow them to +track the pages you view across multiple web sites. +Enabling this option will mean only cookies that come from the +same web server as you are explicitly connecting to will be +accepted. + + + +Automatically accept session cookies + + +An increasingly common use for cookies is not to track your +movements across many visits to a web site, but to just follow what you +do during one single visit. Session cookies are saved as long as you +are looking at the site, and deleted when you leave it. + +Web sites can use this information for various things, most +commonly it is a convenience so that you do not have to keep logging in +to view pages. For example, on a webmail site, without some kind of +session ID, you would have to give your password +again for each email you want to read. There are other ways to +achieve this, but cookies are simple and very common. + +Enabling this option means that session cookies are always +accepted, even if you don't accept any other kind, and even if you +choose to reject cookies from a particular site, session cookies from +that site will be accepted. + + + + +Treat all cookies as session cookies + +If this option is enabled, all cookies are treated as session +cookies. That is, they are not kept when you leave the +web site. + +The definition of leave the web site is vague. +Some cookies may hang around for a little while after you are no +longer viewing any pages on a particular web site. This is +normal. + + + + + +The section for Default Policy sets some +further options that are mutually exclusive — you can choose only one +of these options as the default, but you are free to set a different +option for any specific web server. + + + +Ask for confirmation + +If this option is selected, you will be asked for confirmation +every time a cookie is stored or retrieved. You can selectively accept +or reject each cookie. The confirmation dialog will also allow you to +set a domain specific policy, if you do not want to confirm each +cookie for that domain. + + + +Accept all cookies + +If this option is selected, all cookies will be accepted without +asking for confirmation. + + + +Reject all cookies + +If this option is selected, all cookies will be rejected without +asking for confirmation. + + + + +In addition to the default policy for handling of cookies, which you can +set by selecting one of the three options described above, you can also set +policies for specific host domains using the controls in the Domain +Specific group. + +The Ask, Accept, or Reject policy can be applied to a specific +domain by clicking on the New... button, which +brings up a dialog. In this dialog, you can type the name of the +domain (with a leading dot), then select the policy you want to apply +to this domain. Note that entries may also get added while you are +browsing, if the default policy is to ask for confirmation, and you +choose a general policy for a specific host (for example, by selecting +Reject all cookies from this domain when asked to +confirm a cookie). + +You can also select a specific host domain from the list and click the +Change button to choose a different policy for that +domain than the one shown in the list. + +To delete a domain specific policy, choose a domain from the list, and +then click the Delete button. The default policy will +apply to domains which have been deleted from the list. + + + + +Management + +In the Management tab you can browse and selectively +delete cookies that have been set in the past. + +In the upper part of this dialog, you can see a list of domains displayed +as a tree. Click on the little + next to a domain to see all +cookies that have been set for this particular target domain. If you select one +of these cookies, you will notice that its contents will show up in the frame +Cookie Details below. + +By clicking the Delete button you can now delete the selected +cookie. Click Delete All to delete all cookies stored. + +Choose Reload List to reload the list +from your hard disk. You might want to do this if you have had the +module open and are testing web sites, or have made many changes in the +module itself. + + + + + +
-- cgit v1.2.1