Re: [SM-DEVEL] JPEG attachment display problem

[javier w. <jav...@gm...>]

On Mon, 7 Mar 2005 08:34:14 -0700 (MST), Seth Randall
<se...@mi...> wrote:
>=20
> javier wilson said:
> > On Fri, 11 Feb 2005 15:35:04 +0200, Tatu P=E4kkil=E4
> > <tat...@mi...> wrote:
> >
> >> Hi,
> >>
> >>
> >> We're running SquirrelMail v1.4.3a and there's a strange problem with
> >> jpeg-attachments. They corrupt randomly at some point of the image
> >> (usually
> >> the browser shows 10-20% of the image and the rest is grayish scramble=
).
> >>  The odd thing is that all other attachments seem to work fine;
> >> including gif-images.
> >>
> >> We do have customized our Squirrelmail quite heavily, which might have
> >> caused some side-effects, but we haven't made any changes to
> >> download.php or to functions in mime.php that are used in download.php
> >> (such as
> >> SendDownloadHeaders()).
> >>
> >>
> >> We'd be grateful for any hints concerning this problem, because this i=
s
> >>  really hard to debug because it appears randomly (quite often though,
> >> maybe 30-40% of all cases). Another strange thing is that IE's view
> >> source -function doesn't work at all (Firefox's works fine) :-o
> >>
> >>
> >> The server software in use is Linux with Apache 2.0.52 and PHP 4.3.10.
> >> We
> >> don't think these are related to problem, though, because our older
> >> version of SquirrelMail (customized 1.2.5) works fine with the same
> >> servers.
> >
> > i can't see jpeg attachments when reading the message body on firefox
> > 1.0.1
> > either, i read bug 1001359 (Firefox 0.9.1 does not "Display Attached
> > Images")
> > apparently it's firefox fault. but it's strange that it hasn't been fix=
ed
> > in version 1.0.1
> >
> >
> > javier
>=20
> The Firefox/Mozilla team has stated that they have no plans to change
> this. They feel that since every browser short of plain text ones support
> image/jpeg and image/gif that there's no point in putting it in the
> header. They also send */* which means the browser will accept anything,
> so we should probably take it at its word and check for that too.

can we just add "attachment_common_parse('image/jpeg', $debug);" to
redirect.php and solve this or there's a better way to do it?

javier