Fix some mixed content warnings when accessing extension docs

Fix some mixed content warnings when accessing extension docs
over SSL.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=113135

[Aaron Boodman, 2011-12-05 19:44:24]

Only the change to api_template.html matters.

[kathyw, 2011-12-05 19:56:20]

We could switch between http and https dynamically. Also, we might want to
switch to the asynchronous analytics code, while we're in here.

The analytics doc has sample code in
http://www.google.com/support/analytics/bin/static.py?page=guide.cs&guide=197...
and http://www.google.com/support/analytics/bin/answer.py?answer=174090.

[Aaron Boodman, 2011-12-05 20:11:31]

On Mon, Dec 5, 2011 at 11:56 AM,  <kathyw@chromium.org> wrote:
> We could switch between http and https dynamically.

Is there any benefit? It's simpler to just always include https.

> Also, we might want to
> switch to the asynchronous analytics code, while we're in here.

I know nothing about analytics. We seem to be including both ga.js and
urchin.js, which contain the same functionality.

Do you know what's up with that?

- a