Is it possible to define how many concurrent persistent connections does K-Meleon keep to the remote end? It seems that it is using at least two concurrent connections.

Also, is is possible to enable pipelining support on persistent connections?

this looks to be the pref:

pref("network.http.max-persistent-connections-per-server", 2);

there are others in the k-meleon\defaults\prefs\all.js file you might want to look at.

Okay, I found the preferences I'm interested in from all.js. But when moving the e.g. pref("network.http.max-persistent-connections-per-server", 2); line into my Prefs.js, and restarted K-Meleon, my newly added prefs will get removed.

How to make it work?

I have tried to define all these preferences in my Prefs.js file, but the lines get silently removed when I start K-Meleon.

user_pref("network.http.pipelining", true);
user_pref("network.http.proxy.pipelining", true);
user_pref("network.http.max-persistent-connections-per-server", 4);
user_pref("network.http.max-connections-per-server", 8);
user_pref("network.http.max-connections", 24);

Have I done any mistakes here?

there's information around these forums about the problems involved with adding things directly to the prefs.js... to sum up: you MUST do so when k-meleon is COMPLETELY closed down, or they'll be overwritten, OR you can just add the lines to a file named user.js in the same directory as prefs.js, and they'll be added every time you start k-meleon. note that any pref set to it's default value will generally not show up in prefs.js... only the ones set to non-default values.

hope that helps.