Hello SZ!
You must parse the HTML for this. We use a Delphi HTML parser which I
downloaded from sourceforge for this but sometimes it raises an exception.
Search for that and if you cannot find it I will do my best to search it for
you in our projects...
Actually I'm trying to extend Angus'
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,
Hello Anton,
You must parse the HTML for this. We use a Delphi HTML parser which I
downloaded from sourceforge for this but sometimes it raises an exception.
Search for that and if you cannot find it I will do my best to search it for
you in our projects...
Regards,
SZ
On Wed, Sep 8, 2010 at
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
Currently I'm starting some research on HTTP downloads with ICS THttpCli.
I want to add recursive download functionality but faced with
impossibility to distinguish file of directory.
In HTTP world, there is no real directory concept. There are only documents.
It happens that some webservers,
Then I noticed that requests to folder without trailing slash (GET
/somepath/foo/bar)
are redirected to locations with slash (/somepath/foo/bar/) so it's easy
to tell it's a directory.
this depends how server is configured to treat trailing slash. In most
cases it will treat it as access to
