Closed nitriques closed 10 years ago
@brendo Can I merge this in ? Anybody (@michael-e) tested it ?
Nope, I haven't. I have never used CacheLite, so in this case I can't help with breaking it. :-)
@michael-e oh ok thanks. Do you know who should I ping ?
Hmmm, no idea, sorry.
Well, thanks anyway!
Sorry, in a similar boat to Michael. I haven't used Cachelite before. Ask on the forums perhaps? On 18 Nov 2014 04:53, "Nicolas Brassard" notifications@github.com wrote:
Well, thanks anyway!
— Reply to this email directly or view it on GitHub https://github.com/symphonists/cachelite/pull/24#issuecomment-63354720.
Maybe @creativedutchmen uses it ?
We'll see, but I don't think so. AFAIK, he uses datasource caching (Cacheable Datasource) and more "advanced" frontend caching (i.e. Varnish).
more "advanced" frontend caching (i.e. Varnish)
I wish I could use that...
Michael is right, Varnish it is for me. Sorry:)
On Tue, Nov 18, 2014 at 12:22 AM, Nicolas Brassard notifications@github.com wrote:
more "advanced" frontend caching (i.e. Varnish)
I wish I could use that...
Reply to this email directly or view it on GitHub: https://github.com/symphonists/cachelite/pull/24#issuecomment-63395802
@creativedutchmen Thanks anyhow! @andrewminton told me he might test it...
@nitriques do you have a series of test criteria you want me to cover at all?
Thanks !
Ok, on it.
cache still exists if I don't use ?flush=site or ?flush
I think this always been like that, am I right ?
Yes it is.. all good from my point of view.
Great ! Thanks a lot Andrew!
This PR is for review and tests.
It should fix issues #9, #20 and #22.
I've also added a better 'GET' detection (6fd0f5e1b502a13b7db1e8e8af1a5c8641b38b5c) and added Added X-Frame-Options and Access-Control-Allow-Origin headers (155659171535eda872c62c79ebdfb3cedc96d56e). I've tested it and everything seems to be working well.