<?xml version="1.0"  encoding="UTF-8"?>
	<rss version="2.0">
		<channel>
			<title>Comments to Google Analytics&#039; Security Warnings</title>
			<link>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/</link>
			<description>User submitted comments to Practical Ecommerce's article entitled Google Analytics&#039; Security Warnings</description>
			<language>en-us</language>
			<copyright>Copyright 2007 Confluence Publishing</copyright>
			<lastBuildDate>Tue, 03 Jun 2008 09:51:58 -0600</lastBuildDate>
			<docs>http://www.practicalecommerce.com/rss/</docs>
			<generator>Practical Ecommerce v2.0.1</generator>
			<category>Ecommerce</category>
			<managingEditor>kmurdock@practicalecommerce.com</managingEditor>
			<webMaster>bgetting@practicalecommerce.com</webMaster>
			<ttl>60</ttl>
			<item>
			<title>hatch</title>
			<link>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment12500</link>
			<description>If you have a common footer for all your pages, you can use javascript to dynamically sense the protocol (http: or https:) and switch to the proper include file:


var gaJsHost = ((&quot;https:&quot; == document.location.protocol) ? &quot;https://ssl.&quot; : &quot;http://www.&quot;);
document.write(unescape(&quot;%3Cscript src=&#039;&quot; + gaJsHost + &quot;google-analytics.com/ga.js&#039; type=&#039;text/javascript&#039;%3E%3C/script%3E&quot;));

</description>
			<pubDate>Tue, 03 Jun 2008 09:51:58 -0600</pubDate>
			<guid>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment12500</guid>
			</item>
			
				<item>
			<title>Sergiy Lavryk</title>
			<link>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment8355</link>
			<description>http://www.google.com/support/analytics/bin/answer.py?hl=en&amp;answer=55483</description>
			<pubDate>Wed, 02 Apr 2008 21:14:07 -0600</pubDate>
			<guid>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment8355</guid>
			</item>
			
				<item>
			<title>John</title>
			<link>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment4322</link>
			<description>Mel&#039;s response above worked!!!

Change the reference to the javascript include from &quot;http://www.&quot; to &quot;https://ssl.&quot;

</description>
			<pubDate>Fri, 07 Dec 2007 15:46:51 -0700</pubDate>
			<guid>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment4322</guid>
			</item>
			
				<item>
			<title>Lalit Mehta</title>
			<link>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment3468</link>
			<description>I don&#039;t know if this is new, but when you add the website for Google Analytics, you can select whether your website is http:// or https://

You get the correct js code to add depending on what you select.</description>
			<pubDate>Thu, 16 Aug 2007 14:22:21 -0600</pubDate>
			<guid>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment3468</guid>
			</item>
			
				<item>
			<title>rod</title>
			<link>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment3399</link>
			<description>After I changed my website url to https and got the ssl script... Do I have to change it into original form (http://) or leave it as it is?

</description>
			<pubDate>Tue, 31 Jul 2007 10:54:24 -0600</pubDate>
			<guid>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment3399</guid>
			</item>
			
				<item>
			<title>Pete</title>
			<link>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment2992</link>
			<description>Once you have signed into google analytics go to the  http://www.google.com/support/analytics/bin/answer.py?answer=31846&amp;topic=7175 page</description>
			<pubDate>Tue, 05 Jun 2007 02:08:45 -0600</pubDate>
			<guid>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment2992</guid>
			</item>
			
				<item>
			<title>Mel</title>
			<link>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment1100</link>
			<description>From the Analytics support page, this is the proper solution:

change &quot;http://www&quot; to &quot;https://ssl&quot;</description>
			<pubDate>Thu, 05 Apr 2007 15:15:59 -0600</pubDate>
			<guid>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment1100</guid>
			</item>
			
				<item>
			<title>Mel</title>
			<link>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment1099</link>
			<description>Both these solutions lead to a JavaScript error for me.</description>
			<pubDate>Thu, 05 Apr 2007 15:08:55 -0600</pubDate>
			<guid>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment1099</guid>
			</item>
			
				<item>
			<title>Ryan</title>
			<link>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment263</link>
			<description>Just change the reference to the script to &quot;//{url}&quot; instead of &quot;http://{url}&quot; and youre set for both http and https pages...</description>
			<pubDate>Thu, 08 Feb 2007 08:34:30 -0700</pubDate>
			<guid>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment263</guid>
			</item>
			
				
		</channel>
	</rss>