#533271 konqueror: Separate important cookies from the junk ones

Package:
konqueror
Source:
konqueror
Description:
advanced file manager, web browser and document viewer
Submitter:
Greg Kochanski
Date:
2010-02-19 19:00:10 UTC
Severity:
wishlist
#533271#5
Date:
2009-06-16 06:26:42 UTC
From:
To:
It would be good if konqueror had a way to keep cookies that
you really care about separate from the usual collection of
trash cookies that one collects while surfing.  That way,
you could have a separate expiration policy (trash expires
in 24 hours, *my* cookies never expire).    Or, if you clear
private data, it wouldn't clear your important cookies.

Why?   Because cookies can represent subscriptions and
logins.   They can represent money you have paid to access
a web site.    They can represent the effort you spent to
rummage under your keyboard to find the password for a site :).
You don't want to throw that kind of stuff
away, at least not without explicit manual confirmation.

On the other hand, most (99%) of cookies are either
(a) advertising/tracking cookies which have no value to
the user, or (b) represent the current state of one's progress
through a website (which rarely has value beyond a day).

The world has given us two types of cookies, so the browser
should help us handle each group appropriately.

I would suggest this:
*If a cookie is in the "important" class, it will *only* be accepted
on positive manual confirmation.   So, a website would (somehow)
ask that certain cookies be given the manual treatment.
*Then, these cookies would have a separate expiration policy and
would not be affected by the default "clear private data" operation.

#533271#10
Date:
2009-06-16 16:14:47 UTC
From:
To:
tags 533271 upstream
kthxbye

Hello,

the bug you reported is a KDE bug. Please report it via
Help -> Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following instructions
to report a new bug.

Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs and therefore it is unlikely that
your bug will be solved if you do not report it to KDE developers
directly (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one on the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
control@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)
------------[ copy this ]------------ forwarded 533271 KDE-BUG-URL thanks ------------[ copy this ]------------ Greetings, Armin Berres