Not that it is a request but i found a very good way of speeding up k-meleon
here it goes!
1.Type “about:config” into the address bar and hit return. Scroll down and look for the following entries:

network.http.pipelining network.http.proxy.pipelining network.http.pipelining.maxrequests

Normally the browser will make one request to a web page at a time. When you enable pipelining it will make several at once, which really speeds up page loading.

2. Alter the entries as follows:

Set “network.http.pipelining” to “true”

Set “network.http.proxy.pipelining” to “true”

Set “network.http.pipelining.maxrequests” to some number like 30. This means it will make 30 requests at once.

3. Lastly right-click anywhere and select New-> Integer. Name it “nglayout.initialpaint.delay” and set its value to “0”. This value is the amount of time the browser waits before it acts on information it receives.

it only works on broadband connections!

Here's a question to the builders. Why isn't the pipelining enabled by default in the new builds?

I think I saw some reports that it isn't RFC-compliant, it is causing (not necessarily necessesary aka selfish) loads on servers anyway. Probably that's why there's a hard-coded limit on maxrequests - it is set to 8, so there's no sense in values above 8.

There might be servers that have problems dealing with pipelining, especially if the first request is pipelined, too. For the MoFo that's (and perhaps some additional things) were enough for a reason. But to make K-M load pages a tiny bit quicker this switch could be used ...

IMHO not enabled;
maxes are from w3 possibly - old servers can not do all - so that is my naive guess.
but that is much along ra´s lines. greetings

Hmm. Well, I don't know how to put this. It seems that you are "pipelining" the web browser to open upwards of 8 (max) requests to one single page at a time to save yourself probably 1 second or so. Hmmm.

Did anyone else out there think about the implication of this? This could be considered a traditional DoS attack to the server! Yes, I am currently working on stopping such attacks on web/content servers, and this type of web page viewing seems that it might be a little too close for comfort to what a DoS attack is! Simply because of the _same_ data being requested mutliple times instantaneously.

Albeit, this could be avoided if a standard "pipeline" max requests is established, whereby (say) 4-6 max pipeline connects. Then this could avoid an accidental banning for an "attampted DoS attack." However, this probably won't be an issue for years until a marketable version of such attack detection is available. =)

Pipelining henders rather than helps on a lot of sites.
It causes missing images because some requests timeout.
This is especially true if your using a dialup connection.

On the other hand, I don't think there's any possibility of pipedline requests being mistaken for a DoS attack, it simple doesn't work that way.

@Mindless
... to save yourself probably 1 second or so.
That's not quite true.  On sites with a lot of images or files, pipelining can help save you many seconds and makes the site loads faster.  I won't provide statistics because they are useless.  They differ from server to server and from time to time, mainly because of the Internet traffic.

Also, traditional DoS attacks sends requests to the server, but tells the server to send the response/data to the wrong IP address.  Therefore, browsers would never behave like a traditional DoS attack, because it will never receive any data.

Furthermore, a proper browser or a proxy server should not resend the same data to the server.  This is even if they are using pipelining, except with the possible exception that they are told not to cache anything.  It may be more worth your time to identify which browsers and proxy servers are misbehaving in this case and consider how to treat them.

@CaptnBlack
You have a point there.  Pipelining doesn't really work if your main problem is bandwidth.  There's no point queuing a bunch of files to be downloaded when you can only download a small amount at a time.  I could generalise and say that pipelining helps to make a website load faster only when you have the bandwidth to spare, or at least download all the files before timing out.

I have just downloaded k-ninja and tried the suggested instructions above and it has speeded things up quite a bit. I am running a slow machine P400 II 98 ram I think Windows 98se its old but it works.However it seems to work a bit better then the proper version of k-meleon, any one fancy trying this? However I do have 1Mb broadband and have used DrTcp to tweak my settings, This i know has made a difference to my machine as well.
Whos up for a challenge?

P.s can we please please have a form filler plugin to k-meleon I trying to find a job and sick of filling out my details soooo many times.

http://kmeleon.sourceforge.net/wiki/index.php?id=PageSpeed&PHPSESSID=c55e89d8279b9a390b29683beba55283

I heard about this, but i did not put 30, i put 100000. I want speed.