Re: Inlined image format
montulli@stat1.cc.ukans.edu (Lou Montulli)
From: montulli@stat1.cc.ukans.edu (Lou Montulli)
Message-id: <9401260017.AA21162@stat1.cc.ukans.edu>
Subject: Re: Inlined image format
To: sanders@BSDI.COM (Tony Sanders)
Date: Tue, 25 Jan 94 18:17:01 CST
Cc: phillips@cs.ubc.ca, www-talk@www0.cern.ch
In-reply-to: <199401252353.RAA02740@austin.BSDI.COM>; from "Tony Sanders" at Jan 25, 94 5:53 pm
X-Mailer: ELM [version 2.3 PL2]
Content-Length: 1472
>
> > In spite of the danger of upsetting the Mosaic people, there is something
> > that really should be done to their in-line image support. It should
> > stop lying to the servers -- when the browser sends out a HTTP request to
> > get an in-line image it says it will accept anything (including text/html).
> > If it only listed the formats it really supported, the server writers
> > could do something about all this.
>
> I agree. Of course, if the URL doesn't return a GIF then it isn't going
> to work so this isn't much of an issue right now. I do think Mosaic
> should restrict the Accept: headers in this situation.
>
> --sanders
>
How about adding a new header or a new form of the existing
header to specify what kinds of image types can be "inlined"
The server may want to differentiate between a get that is
coming for an image that will be inlined and one that will
be spawned in an external viewer.
:lou
--
**************************************************************************
* T H E U N I V E R S I T Y O F K A N S A S *
* Lou MONTULLI @ Ukanaix.cc.ukans.edu *
* Kuhub.cc.ukans.edu ACS Computing Services *
* 913/864-0436 Ukanvax.bitnet Lawrence, KS 66044 *
* UNIX! Cool! I know that! Jurassic Park - The Movie *
**************************************************************************