This is quite easy and can be done with one of the next releases.
As a workaround, got to line 224
echo $strTrackingCode;
and add this line BEFORE:
$strTrackingCode = str_replace('(("https:" == document.location.protocol) ? "https" : "http")','"https"',$strTrackingCode);
But just to understand your request: does it make sense to deliver the tracking code secured while the page itself isn’t?
Sounds good!
I just want to enable force_ssl=1 on my Piwik install.
http://piwik.org/faq/how-to/faq_91/
It’s easiest to run everything under HTTPS. (You don’t need to setup multiple vhosts for example.)
The demand for this feature will probably increase as people adapt SPDY where SSL is forced.
Ah, ok, I understand the benefit – thank you. 🙂
The feature will be part of 1.0. A first release candidate is scheduled for the end of July.
