Follow-up Comment #3, bug #33826 (project wget):
Hello,
maybe the following change will make it clear for a user and is acceptable for
inclusion:
--- wget.texi.orig 2013-11-08 10:27:43.000000000 +0100
+++ wget.texi 2013-11-08 10:28:18.000000000 +0100
@@ -1295,12 +1295,19 @@
@item Netscape 4.x.
The cookies are in @file{~/.netscape/cookies.txt}.
-@item Mozilla and Netscape 6.x.
+@item Mozilla < 4.x and Netscape 6.x.
Mozilla's cookie file is also named @file{cookies.txt}, located
somewhere under @file{~/.mozilla}, in the directory of your profile.
The full path usually ends up looking somewhat like
@file{~/.mozilla/default/@var{some-weird-string}/cookies.txt}.
+@item Mozilla > 4.x.
+Mozilla's cookie file is named @file{cookies.sqlite}, located
+somewhere under @file{~/.mozilla}, in the directory of your profile.
+The full path usually ends up looking somewhat like
+@file{~/.mozilla/default/@var{some-weird-string}/cookies.txt}.
+The SQLite file is not useable with the @samp{--load-cookies} option.
+
@item Internet Explorer.
You can produce a cookie file Wget can use by using the File menu,
Import and Export, Export Cookies. This has been tested with Internet
(file #29569)
_______________________________________________________
Additional Item Attachment:
File name: wget-doc-cookie_description.patch Size:1 KB
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?33826>
_______________________________________________
Nachricht gesendet von/durch Savannah
http://savannah.gnu.org/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
