[6399] in www-talk@info.cern.ch

home help back first fref pref prev next nref lref last post

Re: Versioning HTML at the server and Accept-inline

daemon@ATHENA.MIT.EDU (Tony Sanders)
Fri Oct 28 01:06:51 1994

Date: Fri, 28 Oct 1994 05:53:19 +0100
Errors-To: listmaster@www0.cern.ch
Errors-To: listmaster@www0.cern.ch
Reply-To: sanders@bsdi.com
From: Tony Sanders <sanders@bsdi.com>
To: Multiple recipients of list <www-talk@www0.cern.ch>

cwilson@spry.com writes:
> >> Tony Sanders writes:
> >> >No need.  The browser should simply send the appropriate standard Accept:
> >> >headers when it requests the inline data.
..
> No, you don't need to send a bug report to Spry.  AIR Mosaic does indeed only
> send Accept: headers for the inline image types (currently only image/gif and
> image/xbm) that it knows how to handle.  :^)  However, this does NOT solve
> the problem in the long run.  What happens when we move to a system that
> requests the document _AND_ its components (e.g. inline images) via either an
> MGET or a smart server with multipart MIME handling?  At that point, we are

Whatever scheme people use better support having different Accept: headers
(and other headers as well) associated with different parts of the request
or else they will have broken the entire system.  This goes far beyond
just inline images.

--sanders

home help back first fref pref prev next nref lref last post