Francois wrote: >In HTTP world, there is no real directory concept. There are only documents. >It happens that some webservers, if configured so could display a directory >content if the default document is missing. That directory content is a HTML >page built automatically by the webserver. Yes, I've realized it already
>This is not always the case. >I would not rely on that behaviour. Zvone wrote: >So you cannot really know how folders are structured on the server is >just by looking at the URL. Sad :( That's what I was afraid of... Well, then I have a question: maybe you have some ideas of how to organize recursive download: for example, if user started to download www.example.com/path/index.html, we should also accept www.example.com/path/logo.jpg and so on, but not www.example.com/index.php. If user started www.example.com/path/foo, we should accept www.example.com/path/foo/index.php but NOT www.example.com/path/bar.jpg. Applications like Wget do support this behavior but the question is how they do it. -- Anton -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
