Re: Curious ftp problem with squid 1.1.3

     The problem with text/plain as a mime type is that sometimes means only 7
     bit code so obit octets can cause real problems. THis may be what is
     happening here where something like control-Z (ascii code 26) is
     interpreted as end of file before all file is displayed.
     
     ___________________________________________________________________________
     
     from Duane Wessles
     
     tjfs@tadpole.co.uk writes:
     
>Scenario: Client is Windows 3.1 Internet Explorer 3.0 (version 3.0.1152)
>
>Client clicks on a link in a Web page to
     ftp://somehost.com/path/to/foobar.gqa
>
>Internet Explorer reports "The attempt to load 'ftp://.../foobar.gqa
     failed"
>
>The problem can be fixed by:
>
>* turning off proxy access (hence squid is implicated)
>
>-OR-
>
>* renaming the file to foobar.bin
     
     Interesting. Leads to the conclusion that this is caused by ftpget's
     choice of Content-Type.
     
     When ftpget encounters an extension it does not know about ('gqa'),
     then it must use some kind of default Content-Type. Over the course of
     the software we have switched back and forth between two:
     
         text/plain
         application/octet-stream
     
     When we default to 'text' the file is displayed in the browser. When
     we default to 'octet-stream' the browser usually opens up a save-file
     dialog box.
     
     So it would be interesting to try changing DEFAULT_MIME_TYPE in
     ftpget.c and see if that fixes this problem. Meanwhile, everyone can
     argue about which content type should be the default.
     
     Duane W.
Received on Tue Jan 14 1997 - 14:09:50 MST