Tux3 and 2.2.x

Since some time ago I'm running 2.4.23 + tux3-2.4.23-A3 + some ck 
patchset I can't remember + a really simple tux-compression patch plus 
other bits that I think that it doesn' matter.

The results, it works ok, I'm happy with it, it' stable for me, but my 
system it's a k6-2 450 + 128MB on a 300-150 kbps line, so I think it's 
pretty low on this list, but at last I will share it.

The most important thing that I forgot to patch was that simple 
compression fix, without it if you enable compression the content length 
that it's sent it's the uncompressed one, but it must be the compressed 
one. I have this patch since a long time ago, but I can't remember who 
was the author.

All I can say it's that it is stable for me (logging enabled, I never 
needed to disable it).

Now this is the compression patch I have archived, it's the only thing 
that it's left out of tux rigth now.

--- linux-2.4.20-ck2-tux2/net/tux/proto_http.c    Wed Jan  8 08:55:07 2003
+++ linux/net/tux/proto_http.c    Wed Nov 20 14:34:59 2002
@@ -1958,9 +1958,25 @@
         if (partial)
             curr += sprintf(curr, "%Ld", req->output_len);
         else {
+            /*
             // "%d" req->total_file_len
             memcpy(curr, &req->etag, req->lendigits);
             curr += req->lendigits;
+            */
+            /* The ETag was generated with an uncompressed file's
+             *  info.  I've left the ETag as it is, but the size
+             *  needs to be from req->total_file_len.  In other
+             *  words, needs to be from the compressed image if
+             *  we're sending gzip versions.
+             *  - [email protected] -- 2002-11-13
+             */
+            if (req->content_gzipped)
+                curr += sprintf(curr, "%Ld", req->total_file_len);
+            else {
+                memcpy(curr, &req->etag, req->lendigits);
+                curr += req->lendigits;
+            }
+
         }
         if (tux_generate_etags && (req->status != 404))
         {


-- 
Jorge Nerin
<[email protected]>