Wget breaks

It seems that digium has changed something on the downlod site(downloads.digium.com/pub) since yesterday. Now all my wget doesn’t work with the download site anymore. Please resolve ASAP…i need to install my zaptel driver(which use wget to download latest firmware) urgently. Please stop using the silly eloqua, it is the worst click reporting software I ever seen.

This is how Digium decided to set up their servers and I can only assume this is how it will stay. To use wget simply right click on the file that you want. Get the properties of it and get the URL out of it. It’s not rocket science.

For instance if the URL that you get from clicking properties on the url shows:
digium.com/elqNow/elqRedir.h … eLog-1.2.0

The URL that you want to use in wget is: downloads.digium.com/pub/asteris … eLog-1.2.0

Even the exact URL, the wget on my machine still fail to work properly. I have also updated wget to the latest version but still failing. If anyone else doesn’t face this problem, I am suspecting that my ISP is running some kind of proxy server which causes this problem.

try wget downloads.digium.com/pub/asteris … eLog-1.2.0 and see what happens.

To try and explain…

if you use…

then wget will return the html that is encountered when it connects to the script at digium which is www.digium.com/elqNow/elqRedir.htm. This script probably logs the users details and time of request as well as counting requests.

This script will then return a redirect to the users browser. This would normally cause the browser concerned to retry the request to the specified url. ie. downloads.digium.com/pub/asteris … eLog-1.2.0
The problem is that wget is a simple program and does not react to this redirect, it simply saves the data returned as a file which is in actual fact just a bit of html.

Is what other users have correctly advised is to skip the click logging bit yourself and go straight for the treasure by amending your request to point straight at the required item.

I hope this helps.

Mike.

[root@localhost src]# wget downloads.digium.com/pub/asterisk/releases/Cha ngeLog-1.2.0
–10:34:39-- downloads.digium.com/pub/asteris … eLog-1.2.0
Resolving downloads.digium.com… 216.27.40.102
Connecting to downloads.digium.com|216.27.40.102|:80… connected.
HTTP request sent, awaiting response…

(then wget would stuck here forever)

Seems you have an issue on your end. Try something real simple like wget google.com and see what happens.

[root@localhost src]# wget http://www.google.com
--17:47:16--  http://www.google.com/
Resolving www.google.com... 64.233.189.99, 64.233.189.104, 64.233.189.147
Connecting to www.google.com|64.233.189.99|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.google.com.my/ [following]
--17:47:16--  http://www.google.com.my/
Resolving www.google.com.my... 64.233.189.99, 64.233.189.104, 64.233.189.147
Reusing existing connection to www.google.com:80.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html'

    [  <=>                                                                                                                ] 6,291       19.4K/s   in 0.3s

17:47:17 (19.4 KB/s) - `index.html' saved [6291]

I dont think that it is network problem, because it works fine if I try to wget the index page at downloads.digium.com/

[root@localhost src]# wget http://downloads.digium.com/
--17:48:57--  http://downloads.digium.com/
Resolving downloads.digium.com... 216.27.40.102
Connecting to downloads.digium.com|216.27.40.102|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 934 [text/html]
Saving to: `index.html'

100%[====================================================================================================================>] 934         --.-K/s   in 0s

17:48:59 (20.1 MB/s) - `index.html' saved [934/934]