On Wed, Sep 06, 2000 at 07:05:45PM -0700, Jason Baker wrote:
> Sam Varshavchik wrote:
> >
> > No, the problem is that MSIE is a shitty, non-standards compliant,
> > browser.
>
> No arguments here. If only it were my choice...
>
> > sqwebmail does exactly the same thing whether it's http or https, it's not
> > a factor in choosing a MIME type, or anything else.
> >
> > This will work fine with Netscape.
>
> The puzzling thing is that a MSIE client -can- deal with it, via
> http://, so long as it goes through Squid first. If I adjust the
> internal firewalls so that local clients can hit the sqwebmail server
> direct on port 80 and remove the proxy setting, they cannot view the
> attachments they just used.
>
> Would you happen to know specifically what IE is ignoring / not dealing
> with, so that I can explain this to the PHB's? Presently, they view it
> as a problem with sqwebmail "since we can download from hotmail just
> fine". Sigh...
That information can be found on MS's site. I don't have a link handy
right now, but search for IE, and MIME types. There's an article that
desribes the algorithm it uses. In few words, they rely on other methods
to determine file types rather than just MIME types (looking at the
contents, and the actual URL). One trick you can do is modify Sqwebmail
so it writes a temporary file somewhere in the document tree, then
redirects the client to that file, then remove the file (since
IE seems to be able to download any files this way). You could also
force a known-to-work MIME type on all files, but that's just nasty.
Of course, a better solution would be for MS to release a
standards-compliant product. Amusingly enough,
ASP applications have no problems uploading generated files.
