Verify and Update any Tools using NCBI resources that are not using HTTPS

...before the September 30, 2016 cutoff.

From: http://www.ncbi.nlm.nih.gov/home/develop/https-guidance.shtml

> After September 30, 2016, NCBI HTTP servers will redirect or reject all HTTP requests
>
> Most Web traffic to NCBI servers is currently (July 2016) still using HTTP. To ease the transition, NCBI intends to redirect most HTTP requests to HTTPS, starting on the switchover date.
>
> If you do not update your application before the switchover date, these redirects from NCBI HTTP servers may buy you time to make the updates later.
>
> After September 30, 2016, all traffic from NCBI HTTP servers, including Web services, will:
>
> respond with a server-side redirect (HTTP 301 Moved permanently) to the corresponding URL on HTTPS, only for HTTP GET and HEAD requests;
> respond with HTTP 403 Forbidden and an error message, to all requests other than GET and HEAD (including and especially HTTP POST);
> include in every response an HTTP Strict Transport Security (HSTS) header, which instructs browsers to automatically communicate thereafter only with HTTPS on that domain. (HSTS applies only to browsers, though other Web clients like scripts are free to implement it.)

Start by searching the repository for tool references to NCBI HTTP URLs and identify every affected tool. Verify each resource endpoint against the linked NCBI HTTPS guidance, update the affected references, and confirm that all NCBI requests use HTTPS.

Written by the indexing model from the issue text.