[jira] [Updated] (VFS-199) Http/Https listChildren browse support

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (VFS-199) Http/Https listChildren browse support

ASF GitHub Bot (Jira)

     [ https://issues.apache.org/jira/browse/VFS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ibrahim Hasbini updated VFS-199:
--------------------------------

    Attachment: VFS-199_updated.patch

Hello,

I attached an updated patch (VFS-199_updated.patch) generated against the HEAD (revision 1436223) of the VFS trunk.

I made the following modifications:

- Used a HashSet to collect the child urls, in order to avoid duplicates.
- Added a check to handle the case where the links in the returned html index are absolute. The older patch assumes the links are always relative.
- moved the version of the jsoup dependency to the dependency management section of the parent pom.
               

> Http/Https listChildren browse support
> --------------------------------------
>
>                 Key: VFS-199
>                 URL: https://issues.apache.org/jira/browse/VFS-199
>             Project: Commons VFS
>          Issue Type: New Feature
>    Affects Versions: 1.1
>            Reporter: Andrew Franklin
>         Attachments: HttpGetList.txt, VFS-199.patch, VFS-199_updated.patch
>
>
> I think this was lodged at some time ago as VFS-79: http://www.mail-archive.com/commons-dev@.../msg83701.html.
> Essentially the ability to browse http via the directory listing structure is reasonably important for a number of use cases.
> Mario noted in that previous bug that the parsing of the html isn't necessarily trivial but I've submitted a patch that meets my requirements. The patch uses java regular expressions which has the requirement of JVM > 1.4. Submitting in the hope that other users will find it useful and maybe we'll be able to tidy it to the point where it can be integrated into the vfs mainline.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira