For those Mac OS X geeks

Posted by joy


Would there be any reason that an Mac OS X compatible FTP client, like, say cyberduck would not be able to view an .asp file within an IIS FTP virtual directory?

For some added drama, if you answer with what I think went wrong, I get to win a bet.

[tags]FTP, Mac OS X, I hate IIS, I think it is a directory settings issue [/tags]


7 Responses to “For those Mac OS X geeks”

  1. bert Says:

    you get to win a bet? but what’s in it for us?

    feh, I don’t know anyway…permissions? Um, maybe you need an IIS geek.

  2. joy Says:

    What do you get, let’s see…hmmm…a happy blogger?

    I dunno, I’d almost say a date, but although most of my readers are male, I think most are, um, otherwise committed.

    BTW, the files were later detected, but that was only after cyberduck was toggled to “active” FTP and the files are being recognized on the Mac as Adobe Go Live files.

    In my book, that still isn’t *right*.

  3. Tony Says:

    Yes, it doesn’t seem right at all. I’m no IIS geek, so let me take a stab at it. :-) My understanding is that for an FTP client to see a virtual folder there needs to be an actual folder in the directory. This folder would typically be empty since the actual files live in the virtual folder. My theory is that somehow Cyberduck is/was showing you the contents of the empty physical folder.

  4. Jason Lefkowitz Says:

    I dunno, I’d almost say a date, but although most of my readers are male, I think most are, um, otherwise committed.

    You gotta tell us how you’re finding that in your log files ;-)

  5. Bill Says:

    stubbornly correct?

  6. Arthur Says:

    You gotta tell us how you’re finding that in your log files ;-)

    There’s an Apache module for that.

  7. Matt Michie Says:

    What do you mean by view? Can you list the contents of the directory and the .asp files are just not there? #1 it sounds like you have MIME issues on the OSX side, which are seeing the .asp as Adobe files. Also, when you say you toggled to active ftp, I assume previously you were connecting “passively”?

    I would guess that there are firewall issues in play. FTP is tricky to firewall properly, particularly if you have some kind of NAT going on in the client side. If you were able to list the file but not able to download it, that would almost certainly point towards a firewall issue.

    Best solution would be to use something like SFTP, but I am a Unix geek, so I don’t know how available that is with IIS Virtual directories.

    Cheers,

    Matt

Leave a Reply