commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd Eckenfels (JIRA)" <>
Subject [jira] [Commented] (VFS-560) File can't be downloaded if HTTP HEAD on base url fails
Date Wed, 04 Feb 2015 11:17:35 GMT


Bernd Eckenfels commented on VFS-560:

Can you please include the exception stack trace? Are you using URL, http or webdav provider
(are you using the default configured VFS.getManager()?)

It looks like the HTTP Provider does an initial head request when the filesystem is initialized
to check basic connectivity. It looks like this cant be turned off (and you can also not disable
redirect chasing). I guess a quick fix for you might be to use the URLFileProvider instead.

I am not sure what would be better, making this configurable or just plain removing it.

> File can't be downloaded if HTTP HEAD on base url fails
> -------------------------------------------------------
>                 Key: VFS-560
>                 URL:
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Patrick GH
> When i try to download a File via HTTP a HEAD-Request on the base url is executed before
the actual download. In my case the result is a redirect (HTTP 302) to another server. This
server is not available due to firewall restrictions and so the following HEAD request fails.
The actual GET request to retrieve the file is never performed.
> Example:
> Url:
> 1. commons-vfs sends HEAD request to (not
> 2. Server returns HTTP 302 with redirect to
> 3. commons-vfs sends HEAD request to
> 4. Request fails because is not available (firewall)
> 5. image.jpg is not downloaded 
> Why is this HEAD request on the base url necessary? The file can be downloaded directly
without problems.

This message was sent by Atlassian JIRA

View raw message