[#151098169] Use HTTPS when communicating with usasearch

[nickmarden]

No description provided.

[coveralls]

Coverage remained the same at 100.0% when pulling 7562f38 on nathan/usasearch_https into 82d732a on master.

[nickmarden]

Marking this as do-not-merge because it's currently not possible to request the /api/v2/agencies endpoint from search.usa.gov whether over HTTP or HTTPS.

HTTP requests redirect to HTTPS:

[nick@npv-23319-l ~]$ curl -s -v -H 'Host: search.usa.gov' 'http://search.usa.gov/api/v2/agencies/search?query=temporary' 2>&1 | grep Location
< Location: https://search.usa.gov/api/v2/agencies/search?query=temporary

and HTTPS requests redirect to HTTP:

[nick@npv-23319-l ~]$ curl -s -v -H 'Host: search.usa.gov' 'https://search.usa.gov/api/v2/agencies/search?query=temporary' 2>&1 | grep Location
< Location: http://search.usa.gov/api/v2/agencies/search?query=temporary

[nickmarden]

It looks as though the root cause of the problem described above is the folllowing:

• HTTP requests from the outside world to the /api/v2/agencies endpoint are being redirected to HTTPS because of Apache-level redirect rules in the search.usa.gov web site
• HTTPS request from anywhere to the /api/v2/agencies endpoint are being redirected to HTTP because the search.usa.gov code base does not have ssl_allowed :all or something similar for the /api/v2/agencies endpoint.

[coveralls]

Coverage remained the same at 100.0% when pulling 82c7300 on nathan/usasearch_https into a1a61f9 on master.