[Plugin: W3 Total Cache] Apache as CDN

I’m not sure on the W3 Total Cache – specific questions, but for the poor man’s CDN, you should point the root domain somewhere that’s not serving cookies.

Anyone who’s visited the top-level domain, assuming GoDaddy’s sending cookies out on it, will pass cookies with every resource that’s pulled from the domain and all of its subdomains (if my understanding of cookies is correct).

Clear your cookies and your cache, then run PageSpeed on your site again – I believe you’ll see the cookies warning go away. I just tried it and there’s no cookies warning for me. Long term, you need to point the TLD at somewhere that’s not serving cookies.

1) The new version of the plugin does not have a .htaccess for the apache CDN anymore, are we to still use one?

If so, where can I get a copy?

A copy of what? Apache (the web server) is irrelevant in terms of what the you are trying to achieve. Simply select that method and configure the browser cache settings you need (like compression) and the .htaccess file will be uploaded for you.

2) The google page speed plugin is still complaining about setting a cookie for my CDN domain even though its a completely different domain.

Any idea what I am doing wrong? (www.gamerslifeline.com)

You need to find the code setting those cookies and make sure they are limited to https://www.gamerslifeline.com.

3) The CDN module allows for multiple hostnames, is it better to use more or less?

There can be diminishing returns, just test your site for yourself, there is no rule of thumb.

4) Any other suggestions when using apache on the CDN to improve performance?

No.

Hi Frederick,

In regards to question #1, I am sorry if I was unclear, but in the earlier versions of the plugin there was an additional .htaccess file provided that was to be used on the CDN.

When I speak of the CDN, I am setting up a whole new hosting account using apache as the web server engine.

With the new version of the plugin I am not seeing a new .htaccess file to use on the CDN specifically and there isn’t one being uploaded to it at anytime.

Thanks!

In regards to question #1, I am sorry if I was unclear, but in the earlier versions of the plugin there was an additional .htaccess file provided that was to be used on the CDN.

That is handled automatically now.

When I speak of the CDN, I am setting up a whole new hosting account using apache as the web server engine.

You don’t need a new account, just a subdomain.

What do you mean by automatically?

Meaning you have to take no action.

Hi,

Right now I am using the old .htaccess from the older version, without it using Google Speed test it fails some of the compression tests.

Also, I am showing that the javascript is not being compressed either.

Is there something additional that needs done?

Stop using the old file and modify browser cache settings and re-save. Check your unsuccessful transfers and make sure that it is empty, if it is not, re-export files to try to recreate the automatically created .htacess file.