Answers

By default konqueror does not accept cookies that originate from a site other than the one you
are currently visiting. This is done to protect your privacy. Unfortunately, the netscape mail
site requires that you accept cookies that come from sites other than their own. Hence, the
only way to make konqueror work with that site is to disable the option that activates the
feature mentioned above. To disable this option do the following:

In konqueror click on the Settings menu.

Select Configure Konqueror...

In the Configure Konqueror dialog, click on Cookies.

Make sure the option labeled Only accept cookies from originating servers
is unchecked.

Yes. By default konqueror automatically uses the settings configured when you installed your
desktop. You can manually override this behavior by adding the following settings to either
$KDEHOME/share/config/kioslaverc or $KDEHOME/share/config/kio_httprc:

If you add the settings to the first "kioslaverc", then the options are available to all KDE ioslaves that support
changing these settings. On the other hand, if you want the settings to be applicable to a specific io-slave, e.g.
kio_httprc, then you want to add them to the protocol specific config files. You can also specify these
settings on a per-site basis. To do that, instead of adding the settings to the top of the file (global section),
you need to add them to a specific site section. For example to change the settings sent to all kde.org
sites you would do the following:

[kde.org]
Languages=en
Charsets=iso-8859-1

After making these changes you need to issue the following command to make the settings
take immediate effect:

When you successfully login to a web site (using the login/password dialog, not using a form),
or to an FTP/SMB/SSH/... site, Konqueror caches the username and password in the
kdesud daemon. This information remains alive as long as kdesud runs, but isn't
saved to any file. To ask it to forget all the currently cached logins and passwords,
simply run
kdesu -s

This could be a result of a clashing symbol in both the flash plugin and the
XFree86 libGLU (OpenGL utility lib). Upon closing an embedded flash view,
the wrong function is called which heavily corrupts memory and leads to
either immediately or delayed crashes, lockups and worse.
The only solution that is currently known is either to install Qt without
OpenGL support or to not use the Flash plugin. You can't combine both
until this symbol clash is somehow solved. Unfortunately we cannot do
much about this issue, unless Macromedia is willing to help.
Another reason for Konqueror to crash on every page using a Netscape plugin
is the use of gcc3. Plugins can't work with gcc3 because they are linked to
gcc2's libstdc++, which is incompatible with gcc3's libstdc++.

Ever since version 2.2, konqueror does indeed support automatic
logins as specified in the ".netrc" file. However, there is no graphical
front end to enable this feature ; so you have to do it manually using the
following procedure:

Create $KDEHOME/share/config/kio_ftprc if it does not already exist.
Note that $KDEHOME referes to your personal kde config directory (usually
~/.kde).

Please note that the support for the "macro" keyword is very limited in the current
implementation. In fact, we only honor the "cd" command. Furthermore, eventhough
this nominal "macro" support was left ON by default for the 2.2 beta1 release, you
will have to be manually enable it in subsequent releases by adding a "EnableAutoLoginMacro="
entry following the same procedure outlined above.

Disable imwheel, at least for Konqueror (you can add this to the Exclude section in ~/.imwheelrc).
You might consider not using imwheel at all, because it causes more problems than they solve
with applications these days.

It's a word play on the other browsers' names. After the Navigator and the
Explorer comes the Conqueror; it's spelled with a K to show that it's part of
KDE. The name change also moves away from "kfm" (the KDE file manager,
Konqueror's predecessor) which represented only file management.

There's no standard that says an ALT tag should appear when you
hover over an image. Some browsers do so, but that's all.
Most of the time the ALT tag contains some useless description
like "foo.jpg (231432 bytes)" as Frontpage does by default; besides, the
specification for the ALT property calls for ALT to be displayed in place of
the image, as in text-mode-only browsers such as lynx or w3m. It is not meant
to be used as a tooltip. Tooltips for images are supposed to come from the TITLE attribute,
and this is being implemented.

There is no definite answer to this question.
The HTTP_USER_AGENT http header and the properties of the
window.navigator JavaScript object have been subject to change during
the last KDE releases. Additionally, the user can modify the UA
information on a domain-by-domain basis pretending to have any other
browser in existence.
If you are reading this because you wanted to uniquely identify
Konqueror on your website see the answer to the next question.

We are working very hard on making all the differences go away thus
making any differentiation impossible - or rather needless.
In case you experience a bug or missing feature in Konqueror (let's
say the JavaScript function document.foo() is not working as expected)
we recommend to test for features rather than the browsers brand.
Rather than writing code like

You can change the timeout settings in the system settings under "Network->Connection Preferences".
If you would rather do it by hand, the configuration file for this is $KDEHOME/share/config/kioslaverc,
where $KDEHOME is your local kde config directory (usually ~/.kde/).

Add the following entries without any HEADING, i.e outside of any [] block.
Simply adding it to the top of the file will suffice.

ReadTimeout=x // length of time to wait for arrival of requested data
ResponseTimeout=x // length of time to wait for a response after sending a request
ConnectTimeout=x // length of time to wait for response after attempting to connect
ProxyConnectTimeout=x // same a above except it is used for proxy servers.

where x is the value you need in seconds. To give you an idea, here are the default
values:

Yes. Just install Qt, kdelibs and kdebase, and from your favourite
window manager, just launch Konqueror. It should work just fine,
but if it doesn't (KDE developers don't test that case often), report it
to http://bugs.kde.org and try running "kdeinit4" before running Konqueror,
it usually helps.
This is of course the same for any other KDE application.

The "No Proxy For" field under "Settings->Configure->Proxies" accepts any
number of comma or space separated hostnames or fully qualified
addresses. You can mix and match the use of these separators as well as
have any number of them b/n the specified hostnames in the list.

Do not however use the asterisk (*) to indicate multiple matches under
a specific domain. That will not work. Instead only enter the common part of
the addresses you want to exclude. For example, to exclude all KDE sites from
using proxy enter ".kde.org" (without the quotation) rather than "*.kde.org"
in the "No Proxy For" field.
Also note that this is only supported for HTTP proxies currently, not
for FTP proxies.

Simply type ftp://user@host/ and Konqueror will prompt you for a password.
If your username contains the '@' sign, replace it with %40.
If your username contains the '#' sign, replace it with %23.
You can also type the password into the URL, using ftp://user:password@host,
using the same encoding rules for '@' and '#' in the password.

Under the Bookmarks menu, select Edit Bookmarks.
This will bring up a new window, showing the contents of the bookmarks directory.
From there, you can copy bookmarks into the Toolbar sub-directory,
and every bookmark you copy there will appear in the bookmark toolbar.
Using the "Edit toolbars" dialog for this won't work, this toolbar works differently.

Most binary distributions come from Netscape plugins support enabled, but if you compile
from sources, you need to install libXt (e.g. package libxt-dev), remove CMakeCache.txt
and re-run cmake, in kdebase (check that it compiles the contents of
kdebase/apps/nsplugins/). If the auto-detection of the plugins fails, try
running "nspluginscan" from the command line.

Most like you are using Sun's 1.3 JRE. There is a know problem that prevents KJAS from
working with that version of Java. Please use Blackdown's 1.3 release, IBM's 1.3 release,
or Sun's 1.2.2 release. Each of those is known to work. Hopefully this issue will be
resolved in a 1.3.1 release from Sun.