I have no idea. If you have time, you should run a TCP tracing tool like WireShark to see what the data looks like over the wire. You can compare the different browsers to see what Chrome is doing that is funny here.-Darin
On Tue, Sep 9, 2008 at 10:14 PM, Wei Hu <[EMAIL PROTECTED]> wrote: > > Well, I suppose ftp.research.microsoft.com is running Windows, so the > server shouldn't be case sensitive, right? Then why didn't Chrome > download the file? > > On Sep 10, 1:03 am, Darin Fisher <[EMAIL PROTECTED]> wrote: > > Interesting. We are currently using WinInet for FTP, which is the same > code > > that Internet Explorer uses. I wonder why it doesn't work. > > -Darin > > > > On Tue, Sep 9, 2008 at 9:47 PM, Wei Hu <[EMAIL PROTECTED]> wrote: > > > > > OK, Chrome is very strict about upper cases and lower cases in the > > > file names. Chrome is happy to download > > >ftp://ftp.research.microsoft.com/pub/tr/TR-2001-50.pdf, > > > but notftp://ftp.research.microsoft.com/pub/tr/tr-2001-50.pdf. > > > Strangely enough, Chrome doesn't care about the directory names. For > > > example,ftp://ftp.research.microsoft.com/PuB/tR/TR-2001-50.pdfworks > > > just fine. I'm wondering what the FTP protocol has to say about this? > > > > > Even if Chrome is conforming to the standard in this case, IE, > > > Firefox, wget, and ncftp all seem to be able to download both > > > tr-2001-50.pdf and TR-2001-50.pdf. > > > > > On Sep 4, 9:06 pm, Wei Hu <[EMAIL PROTECTED]> wrote: > > > > E.g.,ftp://ftp.research.microsoft.com/pub/tr/tr-2001-50.pdf > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
