-
Type:
Work Task
-
Resolution: Done
-
Priority:
Major
-
Affects Version/s: 1.2.0, 1.3.0
-
Component/s: None
-
None
This is a place holder for feedback from recent Certificate Download Walkthru:
Walk through notes/transcript follows: Platform: Mac OSX, typical, up-to-date version:
Searched for the dataset, got "Loading, please wait", killed that, selected the dataset, got "Connection Failure..." window which went away.
Selected DownloadFiles, got file list. Selected the first two, then hit the Download button.
Authenticated, got the DownloadSelectedData page, authenticated with the MyProxyLogon (double auth action, if I recall correctly).
Downloaded (the script) and got wget-download.sh.html, renamed it to .sh only, then got into the shell and changed its permissions to be executable.
Ran wget which threw up its gnu-hands as it didn't understand certs. Turns out the default Mac version is 1.10.
Googled for "wget mac" (yeah, didn't use the ESG pointer), got some pointers for source code installs, and determined that 1.12 r2 looked like the most recent. Finally dug around and found the GNU wget page:
http://www.gnu.org/software/wget/ (ref'd by our page)
It's mostly focused on source, but had a pointer to the Wget Wiki, which was interesting:
http://wget.addictivecode.org/
But not much help, then found the FAQ:
http://wget.addictivecode.org/FrequentlyAskedQuestions?action=show&redirect=Faq
And this had references to binaries, yippee! Down in Section 2.3 there's an Apple package, went to that site, downloaded installer and ran it. Ran the wget script again but same result, had to figure out where the installer put the script, which was /usr/local/bin, modified my .tcshrc $path, and finally ran the script.
Sez it's a self-signed certificate on the TDS, and suggests using a no-certificate option on wget.
We can probably make this a bit smoother :-) Also, there appear to be standalone Windows binaries; we can maybe point people to the FAQ page.
For the wget workflow, we could recommend:
1. Get a current wget client and install it. Verify the version.
2. Get certificates via MyProxyLogon
3. Download wget script, maybe without a .html extension? Make sure permissions are ok.
4. Execute the script (should it have unique name?)
Walk through notes/transcript follows: Platform: Mac OSX, typical, up-to-date version:
Searched for the dataset, got "Loading, please wait", killed that, selected the dataset, got "Connection Failure..." window which went away.
Selected DownloadFiles, got file list. Selected the first two, then hit the Download button.
Authenticated, got the DownloadSelectedData page, authenticated with the MyProxyLogon (double auth action, if I recall correctly).
Downloaded (the script) and got wget-download.sh.html, renamed it to .sh only, then got into the shell and changed its permissions to be executable.
Ran wget which threw up its gnu-hands as it didn't understand certs. Turns out the default Mac version is 1.10.
Googled for "wget mac" (yeah, didn't use the ESG pointer), got some pointers for source code installs, and determined that 1.12 r2 looked like the most recent. Finally dug around and found the GNU wget page:
http://www.gnu.org/software/wget/ (ref'd by our page)
It's mostly focused on source, but had a pointer to the Wget Wiki, which was interesting:
http://wget.addictivecode.org/
But not much help, then found the FAQ:
http://wget.addictivecode.org/FrequentlyAskedQuestions?action=show&redirect=Faq
And this had references to binaries, yippee! Down in Section 2.3 there's an Apple package, went to that site, downloaded installer and ran it. Ran the wget script again but same result, had to figure out where the installer put the script, which was /usr/local/bin, modified my .tcshrc $path, and finally ran the script.
Sez it's a self-signed certificate on the TDS, and suggests using a no-certificate option on wget.
We can probably make this a bit smoother :-) Also, there appear to be standalone Windows binaries; we can maybe point people to the FAQ page.
For the wget workflow, we could recommend:
1. Get a current wget client and install it. Verify the version.
2. Get certificates via MyProxyLogon
3. Download wget script, maybe without a .html extension? Make sure permissions are ok.
4. Execute the script (should it have unique name?)