-----BEGIN PGP SIGNED MESSAGE-----
Redfern Ian writes:
| Few web servers (and no FTP servers!) supply Content-MD5. It might be
| possible to persuade large archive sites to do so - at the moment,
| nobody uses it as it costs them MIPS for no gain. Perhaps if Apache
| could provide Content-MD5 only if requestor has a Via: line?
When I hacked the Content-MD5 support into Apache, the idea was to
come along later on and polish it up a bit. There hasn't been time
for that yet, though... I've been thinking about keeping a cache of
MD5s, in a DB[M] database keyed on the URL (or one database per
virtual server, with the key as the path component of the URL). Does
that sound reasonable ?
My impression is that something like this is needed before people
will accept Content-MD5 generation being enabled by default - so as
to avoid chewing up CPU time on WWW servers recalculating checksums
for objects which haven't changed.
Cheerio,
Martin
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv
iQCVAwUBNAQ1YtZdpXZXTSjhAQECZwP/XSZ6oaZcwv9BfxU8MXuE4DqThVxQ8KJe
chxy0WHSZ9KgEQgfkR+5Z83KMumOuh9x12aws8Y1CS455AoOJP5mz7LbniKxHJ+e
Zh1nqJwPuPl7FitxLZqTJryS/CC4BTCdULuRuHVuQnLbkW8hxxWqPGE3rCMXXokM
qGXyNZv8pPY=
=lY8r
-----END PGP SIGNATURE-----
Received on Tue Jul 29 2003 - 13:15:43 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:11:24 MST