I am working on v8 site and am using cloudflare to cache everything. I have code from umbracoflare project running to invalidate caches of urls when page is published and when images are saved etc.
One problem though is i am using umbraco forms, the forms can be added on any page. I know in cloudflare you can use page rules to ignore pages however in my case i will not know which pages will have forms.
Has anyone come across this issue before when working with cloudflare?
The issue is when using umbraco forms we have anti forgery token and this causes issues when page is cached. Anyhow for now i will just ignore those pages in cloudflare
Hi Ismail, I am not a developer but we are using Umbraco and Cloudflare. Can I check what you mean by "anyhow for now i will just ignore those pages in in Cloudflare."
Are you creating a page rule for each umbraco page with a form and setting it to bypass the cache?
Our forms appear to have been working ok but I see in the log this message
An unhandled exception occurred System.Web.Mvc.HttpAntiForgeryException (0x80004005): The anti-forgery cookie token and form field token do not match. at System.Web.Helpers.AntiXsrf.TokenValidator. which I guess is bad
I think anti forgery token can be controlled by machine key. the same key should work for any servers. the post operation in any case is excluded from cache.
another solution is control cache header by server and "respect" this headers
by CDN, in this scenario you can control header from code.
Umbraco with cloudflare and form pages
I am working on v8 site and am using cloudflare to cache everything. I have code from umbracoflare project running to invalidate caches of urls when page is published and when images are saved etc.
One problem though is i am using umbraco forms, the forms can be added on any page. I know in cloudflare you can use page rules to ignore pages however in my case i will not know which pages will have forms.
Has anyone come across this issue before when working with cloudflare?
Regards
Ismail
for forms we have 2 situation: Get - to show form Post - to submit form
In most cases get can work from cache, post alwaws works without cache. I think by deafult post is not cached in any CDN.
Yakov,
The issue is when using umbraco forms we have anti forgery token and this causes issues when page is cached. Anyhow for now i will just ignore those pages in cloudflare
Hi Ismail, I am not a developer but we are using Umbraco and Cloudflare. Can I check what you mean by "anyhow for now i will just ignore those pages in in Cloudflare."
Are you creating a page rule for each umbraco page with a form and setting it to bypass the cache?
Our forms appear to have been working ok but I see in the log this message An unhandled exception occurred System.Web.Mvc.HttpAntiForgeryException (0x80004005): The anti-forgery cookie token and form field token do not match. at System.Web.Helpers.AntiXsrf.TokenValidator. which I guess is bad
Regards Chris
I think anti forgery token can be controlled by machine key. the same key should work for any servers. the post operation in any case is excluded from cache.
another solution is control cache header by server and "respect" this headers by CDN, in this scenario you can control header from code.
the best solution in my opinion is dynamic, partial cache like this https://www.cloudflare.com/learning/cdn/caching-static-and-dynamic-content/ or just load unreachable parts via ajax
is working on a reply...