You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Bernd Eckenfels (JIRA)" <ji...@apache.org> on 2015/05/12 22:52:00 UTC

[jira] [Resolved] (VFS-560) File can't be downloaded if HTTP HEAD on base url fails

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

Bernd Eckenfels resolved VFS-560.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1
         Assignee: Bernd Eckenfels

http://svn.apache.org/r1679095

Fixed it by removing the head request (less is more), alternative would be `HeadMethod head = new HeadMethod(); head.setFollowRedirect(false); client.executeMethod(head);` but that could fail in other situations, too.

> File can't be downloaded if HTTP HEAD on base url fails
> -------------------------------------------------------
>
>                 Key: VFS-560
>                 URL: https://issues.apache.org/jira/browse/VFS-560
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Patrick GH
>            Assignee: Bernd Eckenfels
>             Fix For: 2.1
>
>
> 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: http://server1.com/files/2015/image.jpg
> 1. commons-vfs sends HEAD request to http://server1.com/ (not http://server1.com/files/2015/image.jpg)
> 2. Server returns HTTP 302 with redirect to http://server2.com/
> 3. commons-vfs sends HEAD request to http://server2.com/
> 4. Request fails because server2.com 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
(v6.3.4#6332)