<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>W3 EDGE &#187; wordpress</title>
	<atom:link href="http://www.w3-edge.com/weblog/tag/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.w3-edge.com</link>
	<description>Innovation Redefined</description>
	<lastBuildDate>Sun, 06 May 2012 18:13:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/><xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>How to configure W3 Total Cache to work with HTTPS and SSL</title>
		<link>http://www.w3-edge.com/weblog/2011/11/how-to-w3tc-https-ssl/</link>
		<comments>http://www.w3-edge.com/weblog/2011/11/how-to-w3tc-https-ssl/#comments</comments>
		<pubDate>Fri, 11 Nov 2011 21:42:47 +0000</pubDate>
		<dc:creator>Anthony Somerset</dc:creator>
				<category><![CDATA[CSS / Markup / Code]]></category>
		<category><![CDATA[caching]]></category>
		<category><![CDATA[http transactions]]></category>
		<category><![CDATA[production]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[w3 total cache]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.w3-edge.com/?p=1321</guid>
		<description><![CDATA[We&#8217;ve worked with a few sites recently that use HTTPS to secure certain parts of there site. Some of the pages are SSL protected due to the data captured (pages processing registration or financial information, for example). When using a CDN in conjunction with HTTPS / SSL, customers often find that the CDN product they [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve worked with a few sites recently that use <abbr title="Hypertext Transfer Protocol Secure">HTTPS</abbr> to secure  certain parts of there site. Some of the pages are <abbr title="Secure Sockets Layer">SSL</abbr> protected due to the data captured (pages processing registration or financial information, for example).</p>
<p>When using a <abbr title="Content Delivery Network">CDN</abbr> in conjunction with <abbr title="Hypertext Transfer Protocol Secure">HTTPS</abbr> / <abbr title="Secure Sockets Layer">SSL</abbr>, customers often find that the <abbr title="Content Delivery Network">CDN</abbr> product they use  lacks an <abbr title="Hypertext Transfer Protocol Secure">HTTPS</abbr> endpoint, or the one provided is different from the standard, non-<abbr title="Hypertext Transfer Protocol Secure">HTTPS</abbr> one.</p>
<p>One simple solution to this would be to force the loading of your <abbr title="Content Delivery Network">CDN</abbr> assets via <abbr title="Hypertext Transfer Protocol">HTTP</abbr> like so:</p>
<p><img class="alignnone size-full wp-image-1322" src="http://w3e.fredericktest.netdna-cdn.com/wp-content/uploads/2011/11/Screen-Shot-2011-11-11-at-19.50.27.jpg?7983b6" alt="" width="649" height="198" /></p>
<p>This leads to one other issue, however&#8230;</p>
<h2>Why dont I see the Blue/Green Bar?</h2>
<p><img src="http://w3e.fredericktest.netdna-cdn.com/wp-content/uploads/2011/11/https.jpg?7983b6" alt="" title="https" width="310" height="35" class="alignnone size-full wp-image-1340" /><br />
When a page and all of its assets are served over HTTPS, modern web browsers provide a visual indicator—usually in green or blue. This is designed to provide visitors with the confidence to shop or register on your site.</p>
<p>When your HTTPS pages are served with &#8220;mixed content&#8221; (as it sounds, this is a situation in which HTTPS and HTTP assets are both being loaded on a single page, this indicator does not appear. This could happen for any number of reasons — all beyond the scope of this article — but there&#8217;s a simple solution for addressing this with only a few short lines of code.</p>
<h2>Disabling CDN on HTTPS pages only</h2>
<p>W3 Total Cache ships with documentation (Performance > FAQ) that provides instructions on disabling each of the caching types. Combined with a simple PHP function and WordPress hook, we&#8217;re able to conditionally disable the CDN for pages that utilize HTTPS.</p>
<p>Add the following code snippet to your theme&#8217;s functions.php file:</p>
<pre class="brush: plain; title: ; notranslate">add_action('wp_head','nocdn_on_ssl_page');
function nocdn_on_ssl_page() {
if ($_SERVER['HTTPS'] == &quot;on&quot;) {
define('DONOTCDN', true);
}
}</pre>
<p>This of course assumes that you have W3 Total Cache active and that the only assets being served over HTTP are originating from your CDN (otherwise, you might need something like <a href="http://wordpress.org/extend/plugins/wordpress-https/">this</a>). When you reload a page being served over HTTPS, you should notice that the familiar green / blue indicator appears in your address bar. </p>
<p><em>Note: we&#8217;ve found that <a href="http://tracking.maxcdn.com/c/15753/3982/378">MaxCDN</a>&#8216;s SSL support and easy integration with W3 Total Cache provides a solid solution for many customers.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.w3-edge.com/weblog/2011/11/how-to-w3tc-https-ssl/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PressThis on WebmasterRadio.fm</title>
		<link>http://www.w3-edge.com/weblog/2009/08/pressthis-on-webmasterradio-fm/</link>
		<comments>http://www.w3-edge.com/weblog/2009/08/pressthis-on-webmasterradio-fm/#comments</comments>
		<pubDate>Tue, 18 Aug 2009 21:09:09 +0000</pubDate>
		<dc:creator>Frederick Townes</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[joost de valk]]></category>
		<category><![CDATA[mashable]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[wordpress plugins]]></category>

		<guid isPermaLink="false">http://www.w3-edge.com/?p=306</guid>
		<description><![CDATA[I was fortunate enough to discuss WordPress usability with one of the industries most well-recognized personalities Joost de Valk.]]></description>
			<content:encoded><![CDATA[<p><a href="http://twitter.com/yoast" rel="nofollow external twitter">Joost de Valk</a> is a well known blogger, WordPress developer, speaker and marketer and has started a great show on Webmaster Radio focused on WordPress tips and the like. I was fortunate enough to be invited to share in the discussion as Mashable&#8217;s CTO discussing usability from various perspectives including design, WordPress optimization as well as a few upcoming plugins. The podcast is available on Joost&#8217;s site <a href="http://yoast.com/press-this/wordpress-usability/" rel="nofollow external">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.w3-edge.com/weblog/2009/08/pressthis-on-webmasterradio-fm/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Database Caching 6/10 queries in 0.014 seconds using apc
Object Caching 631/634 objects using apc
Content Delivery Network via w3e.fredericktest.netdna-cdn.com

Served from: www.w3-edge.com @ 2012-05-16 08:12:52 -->
