- From: ONIME EHIMIKA OHIREIME <onime@ictp.trieste.it>
- Date: Thu, 26 Aug 1999 11:35:00 +0200 (MET DST)
- To: "Dietmar P. Schindler" <schd@mra.man.de>
- cc: www4mail-comments@w3.org, gerald@w3.org
Well, It is difficult say exactly what caused the system to use application/binary. My own request to www4mail@wm.ictp.trieste.it has image/gif So, I would like to have a copy of your request to the www4mail server. So I can try to recreate the state exactly... On Thu, 26 Aug 1999, Dietmar P. Schindler wrote: > Dear Clement, > > my problem with the extra CR/LF in a GIF file was indeed due to the > inappropriate automatic generation of the tsource in my request. > > When I requested the image without any command keyword, just the URL, > I received the correct image data. But now there's another problem. > The attachment starts with the following lines: > > Content-Type: application/binary; name="winner_mitmach.gif" > Content-Transfer-Encoding: base64 > Content-Disposition: attachment; filename="winner_mitmach.gif" > Content-Description: GIF image data, version 89a, 460 x 57, > > Although the Content-Description tells that it's a GIF image, this isn't > the case with the Content-Type. The "application/binary" causes my > browser to not display the image, as it should, but to ask me as what > file I wished to save it. How comes that the Content-Type isn't right? > > Best regards > Dietmar >
Received on Thursday, 26 August 1999 05:40:18 UTC