--DaTEgnRu5pEC8TLg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 06, 2005 at 03:21:13PM -0700, Herb Peyerl wrote:
> I'm wondering what, in the world, changed in the last month to cause=20
> this to suddenly start happening, on a machine that's been happily=20
> chugging away, doing this same job, for 4 years?   Did a new http=20
> standard come out and now all new browsers are starting to use it?

Unless its some kind of worm, my guess might involve the words firefox
and pipelining, and the number 1.0.  Except I'd kind of expect that to
have the opposite effect, and plus your webserver would have to
support it too.

You haven't updated or changed the NAT/firewall, but has someone
updated the website?  Perhaps scattered lots more small images on it
or something?

--
Dan.

--DaTEgnRu5pEC8TLg
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iD8DBQFB3b0HEAVxvV4N66cRAlfPAKDGgKw376l+cyX8nV6uOaSeYyVoGgCfTL/J
8zNuI92/9qaIl9VYTVh+kpc=
=bDZB
-----END PGP SIGNATURE-----

--DaTEgnRu5pEC8TLg--