SJ77 Posted March 14, 2017 Share Posted March 14, 2017 Cloud Flare is great, but I had to turn it off because it has a 100MB single file upload limit. I am using IPS downloads app and files need to be allowed larger than 100MB My idea is that I could use CloudFlare on all pages of my site except the market place page. Cloudflare allows dns records to setup such that a sub domain can be bypassed while other pages are cached. But I don't know how to setup IPS downloads so that my market place is on a sub domain. Any ideas at all how I can still use cloudflare? Link to comment Share on other sites More sharing options...
SJ77 Posted March 14, 2017 Author Share Posted March 14, 2017 oh gezz.. how did this double post? Link to comment Share on other sites More sharing options...
Jeffrey Spriegel Posted March 14, 2017 Share Posted March 14, 2017 That would defeat some of the purpose of cloudflare. As if you are trying to prevent ddos attacks they can just go to that page and get your IP and cloudflare is thereby negated. However if you really want to do this, I believe it can be done using the page rules in cloudflare. Link to comment Share on other sites More sharing options...
SJ77 Posted March 14, 2017 Author Share Posted March 14, 2017 Right, but for now I can't use cloudflare on any page of my site. (Or files can't be uploaded) i will look into page rules. Link to comment Share on other sites More sharing options...
SJ77 Posted March 15, 2017 Author Share Posted March 15, 2017 so turns out page rules won't work. Any other ideas? Link to comment Share on other sites More sharing options...
Numbered Posted March 15, 2017 Share Posted March 15, 2017 I think you may try to create little hack: Create some domain, which will free of cf, but see same document root folder. Write nginx rule with detect POST type with params commentform_.. and/or other params from form inputs. Write rewrite to second free domain if nginx detect download. IPS might this post from other domain clear (because you rewrite correct csrf and other params) and return answer with correct domain (because base domain not changed in the settings). It's theory, but I dont' see any problems for working. csrf - ok, cookies - rewrited with other form params and other headers. If some part of forum detect incorrect incoming domain - then you simply can change this param in fastcgi setting, when free domain pass request to nginx backend. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.