Examine traffic (from the Alliance / AGR?) coming through the GO API

[kltm]

We'd like to understand better the large volume of traffic we're getting on the GOlr aux endpoint that can occasionally be disruptive.
Looking at it, it would seem to be ribbon calls, coming in to about 200k hits/day.

To close this ticket, we'd like to have a better understanding of the traffic and a doc describing some possible practices for upstream pages with respect to their downstream widget and API providers.

[kltm]

Okay, as a temporary hack, I've started redirecting traffic to a new proxy and then passing it back to the old GO API location. After some hiccups with setting up HTTPS, etc., I now seem to be correctly proxying and capturing traffic.
Noting that I've already added a robots.txt, so this is not completely the same as what we had before. I'll collect this for a little and will use this information for the doc.

[kltm]

As part of this, it looks like we need http to be available for documentation, so no automatic https upgrade. Reported by @sierra-moxon .

[kltm]

@sierra-moxon This should now be "fixed", although there is still the issue of the GO API docs only working for HTTP (which I believe is noted elsewhere as well).