So, after little bit of digging around [1], a URL of the form
http://www.apache.org/dyn/closer.cgi?filename=<filename>&action=download
will automatically download from the suggested mirror, so in Adel's example
above:

curl -O '
http://www.apache.org/dyn/closer.cgi?filename=qpid/java/6.1.1/qpid-java-6.1.1.tar.gz&action=download
'

should get the archive file correctly

-- Rob


[1] http://apache.org/dev/release-download-pages.html#closer

On 20 March 2017 at 13:43, Lorenz Quack <[email protected]> wrote:

> Hello Adel,
>
> I have problems reproducing. On both windows (IE & Chrome) and
> Linux (Firefox) the download does not start automatically.
>
> In any case, did you check the content of the thing you downloaded
> to see whether it is a html page or a binary (probably gz)?
> For example opening it in a text editor.
>
> In case it is as I suspect the html page you could try using
> cURL's -L switch to make it follow redirects.
>
> Kind regards,
> Lorenz
>
>
>
> On 20/03/17 10:24, Adel Boutros wrote:
>
>> Hello Rob, Lorenz,
>>
>>
>> When you hover on any of the links under "download" section on
>> https://qpid.apache.org/releases/qpid-java-6.1.1/index.html, you got the
>> below link which I am trying to download.
>>
>> On windows, I click on the link and it is automatically downloaded. So I
>> am not explicitly downloading an html page.
>>
>>
>> So it seems the web page has an invalid link.
>>
>> This is what I am experiencing with all artifacts listed.
>>
>>
>> Regards,
>>
>> Adel
>>
>> ________________________________
>> From: Lorenz Quack <[email protected]>
>> Sent: Monday, March 20, 2017 11:08:44 AM
>> To: [email protected]
>> Subject: Re: Corrupt artifacts on Qpid release web page
>>
>> Hello Adel,
>>
>> That is not the link to the actual file. There is one more level of
>> indirection.
>> You are downloading a html page.
>>
>> Kind regards,
>> Lorenz
>>
>>
>> On 20/03/17 09:37, Adel Boutros wrote:
>>
>>> Hello Lorenz,
>>>
>>>
>>> I tried on Windows and Linux<http://www.apache.org/dy
>>> n/closer.lua/qpid/java/6.1.1/binaries/qpid-broker-6.1.1-bin.tar.gz>
>>>
>>>
>>> Linux:
>>>
>>> curl -O http://www.apache.org/dyn/closer.lua/qpid/java/6.1.1/qpid-
>>> java-6.1.1.tar.gz
>>>
>>> tar xfz qpid-java-6.1.1.tar.gz
>>>
>>>
>>> gzip: stdin: not in gzip format
>>> tar: Child returned status 1
>>> tar: Error is not recoverable: exiting now
>>>
>>>
>>>
>>> Windows (Using B1 archiver):
>>>
>>> I can extract qpid-java-6.1.1.tar.gz to qpid-java-6.1.1.tar
>>> I cannot extract qpid-java-6.1.1.tar (Archive is broker or damaged)
>>>
>>>
>>>
>>> Regards,
>>>
>>> Adel
>>>
>>> ________________________________
>>> From: Lorenz Quack <[email protected]>
>>> Sent: Monday, March 20, 2017 10:13:59 AM
>>> To: [email protected]
>>> Subject: Re: Corrupt artifacts on Qpid release web page
>>>
>>> Hi,
>>>
>>> I just tried the source bundle of the "Qpid for Java 6.1.1," release
>>> without issues.
>>> I used the command
>>> $ tar xfz qpid-java-6.1.1.tar.gz
>>> to unpack the source bundle.
>>>
>>> With which artefacts do you experience problems specifically?
>>> What tools are you using to extract the files?
>>> Windows, Linux?
>>>
>>> Kind regards,
>>> Lorenz
>>>
>>>
>>> On 20/03/17 09:05, Adel Boutros wrote:
>>>
>>>> Hello,
>>>>
>>>>
>>>> It seems all ".tar" artifacts are corrupt when accessed from
>>>> https://qpid.apache.org/releases.
>>>>
>>>>
>>>> I can download all ".tar.gz" and unzip them. However, I cannot extract
>>>> the ".tar".
>>>>
>>>>
>>>> Are you aware of such issue?
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Adel
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to