You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Oliver Lockwood (Jira)" <ji...@apache.org> on 2020/03/26 14:42:00 UTC
[jira] [Closed] (VFS-767) Default HTTP VFS provider should support
use of an up-to-date version of Apache Commons HTTPClient
[ https://issues.apache.org/jira/browse/VFS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Lockwood closed VFS-767.
-------------------------------
Resolution: Not A Problem
> Default HTTP VFS provider should support use of an up-to-date version of Apache Commons HTTPClient
> --------------------------------------------------------------------------------------------------
>
> Key: VFS-767
> URL: https://issues.apache.org/jira/browse/VFS-767
> Project: Commons VFS
> Issue Type: Improvement
> Affects Versions: 2.6.0, 2.7.0
> Reporter: Oliver Lockwood
> Priority: Minor
>
> As per the following line of code:
> [https://github.com/apache/commons-vfs/blob/master/commons-vfs2/src/main/resources/org/apache/commons/vfs2/impl/providers.xml#L63]
> the default HTTP VFS provider is only made available if theĀ {{org.apache.commons.httpclient.HttpClient}} class is on the classpath.
> This class belongs to the {{commons-httpclient:commons-httpclient}} JAR, which since 2007 (almost 13 years ago!) was deprecated in favour of {{org.apache.httpcomponents:httpclient}}.
> It would seem reasonable to add support for the newer Apache Commons HttpClient library - and if desired, by creating a sibling implementation of HttpFileProvider, it seems that this could easily be done without removing the support for the legacy implementation.
> I am happy to submit a PR to this effect if that would be considered.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)