[BUG] ImageReadWriter vs. HTTPSocket

Bijan Parsia bparsia at email.unc.edu
Wed Feb 6 20:11:38 UTC 2002


On Wed, 6 Feb 2002 Torsten.Bergmann at phaidros.com wrote:

> HTTPSocket httpGif:
> 'http://www.povray.org/ftp/pub/povray/Hall-Of-Fame/sundae.gif'
> 
> returns the correct form, while 
> 
> |url|
> url := 'http://www.povray.org/ftp/pub/povray/Hall-Of-Fame/sundae.gif'.
> ImageReadWriter formFromServerFile: url.
> 
> was not able to find the gif header. (see GIFReadWriter>>readHeader, 
> the stream is different than in the first expression).

Hmm. I don't have a squeak in front of me, but this might well be the
"accept" header problem, i.e., faux content restrictions.

I don't know if Flow does anything about this, but it strikes me that
registering all the mimetypes squeak can handle and sending out *that*
set, instead of various hardcoded, oft not the best chosen,
defaults. I.e., it's better to be permissive and force folks to add
restrictions, than the other way around.

This is prolly a good place to use the Registering filelist stuff...in
general, getting mimetypes smooth accessible throughout the system would
be good.

Cheers,
Bijan Parsia.




More information about the Squeak-dev mailing list