clabedan

I think thé reason is That our dns point to cotendo who handle thé Whole thing. They only request thé origin servers when the query isn’t cached by them.
Bearing this in mind if you think That we should Still optimise the relationship between cotendo and W3TC, is There somewhere guidelines i could find to show them?
I’ m not very technical but i think They act as Some sort or reverse proxy.
Thanks for your help on this Frédérick !

Hi Frederick,
The guys at Cotendo advise me against any setup through W3TC… not sure why… this is what they say.
Is there a counter argument I could give them? They don’t seem to know W3TC very well and might not be aware of improvements we could make… I guess
—-

Hi Christophe

I do not know why this person directed you to do this. There is no configuration required on your side to use Cotendo other than the cname change on the dns service. The actions described fit more with cdnetworks behavior not Cotendo.
Please don’t follow these instructions.

That’s great, thanks very much Frederick, I will try these setups!

One more thing, I am currently testing Cotendo but cannot workout out to set it up within W3TC.
The only comment regarding W3TC I had from the guys there (very professional by the way) was:
“Our CDN is based on pulling the information which is triggered by a user’s request. One thing which may be useful for better caching is usage of ETAG header try to take a look into that”

I’m not sure what this is. Would you recommend a particular setup?
Thanks again
Christophe

Hi Frederick,
Could you tell us why you would not recommend it?
and which CDN would you recommend please… bearing in mind that some of us are on a budget ??
Thanks

Thanks ever so much… This is exactly what I was looking for (pagebar), even down to the way it’s designed…

Been looking for this for a week!
Thanks again ??