![[DigitalPoint] App for Cloudflare®](/community/data/resource_icons/8/8750.jpg?1692633961){kind=icon}
[DigitalPoint] App for Cloudflare® 1.8.8
- Thread starter digitalpoint
- Start date
digitalpoint
Well-known member
The settings are reading/writing to Cloudflare via API, so it doesn't matter... just be aware that if your dev site is on the same domain/zone (like in a directory or subdomain), any Cloudflare changes to make will also apply to the main site (they are zone/domain settings in Cloudflare).
Also... I brought it to Cloudflare's attention:
Cloudflare said:
digitalpoint
Well-known member
...and it looks like they have resolved it.
CedricV
Well-known member
It's the same server, just a different cpanel account under a subdomain. So that would reflect changes to the live website. Our main issue is that we want to enable HTTP2 and the website is still served under HTTP1.1 even though our VPS settings are HTTP2. Hence why I thought enabling these settings would reflect that and prioritize HTTP2.
CedricV
Well-known member
Indeed it has. Quick.
digitalpoint
Well-known member
Well like I said... Cloudflare settings are per domain/zone. Using the addon to adjust them doesn't somehow magically make them per subdomain. They are literally just making changes as you would in the Cloudflare dashboard.
So yes... normally (with some exceptions where Enterprise customers can adjust settings on a per subdomain in some cases), the changes will be applied to any/all subdomains for the domain/zone.
CedricV
Well-known member
Hey @digitalpoint
We've been having some CF 520's lately. We tried to find a solution but haven't been successful so far. The forum is serving HTTP1.1 even though the server is set on HTTP2 and prioritizes this too. Are we overlooking something ? Nothing is found in error logs.
Thanks in advance.
We've been having some CF 520's lately. We tried to find a solution but haven't been successful so far. The forum is serving HTTP1.1 even though the server is set on HTTP2 and prioritizes this too. Are we overlooking something ? Nothing is found in error logs.
Thanks in advance.
Alpha1
Well-known member
This would be amazing, as it would offer significant speed enhancements. While most users are using CF free plan, there is also a significant subset of users who are using the Pro plan, as the only $20 a month plan unlocks a mass of valuable features, including features that increase site speed and security. Most people I know use the pro plan.
I also think that this feature would be very appealing to WordPress users and having it in the WP version of this addon would significantly increase popularity. Because site speed is so important these days. And this feature would be a game changer for site speed.
digitalpoint
Well-known member
That wouldn’t have anything to do with this addon. 520 means your origin web server is returning something erroneous. Typically caused by a misconfiguration of your web server. You’ll want to contact Cloudflare support so they can help you track down what it is exactly.
HTTP/2 is not going to be a measurable speed (or security) increase for this particular thing, unless I’m missing something (feel free to educate me).
Presigned URLs aren’t an option on the WordPress version because WordPress media doesn’t pass through user permission checks (WordPress media via R2 is on public domain already similar to avatars in XenForo).
digitalpoint
Well-known member
Actually, I stand corrected... one area I can think of where speed would be measurably better would be if a page was displaying more than 6 attachments at once (the full attachment, not just previews). Since most browsers by default limit themselves to 6 concurrent connections to the same host, you are limited to 6 concurrent HTTP requests for presigned URLs. So in that case, multiplexing in HTTP/2 (and higher) would work well.
Still on the fence about it though... It's not an insignificant amount of work and would introduce some added complexity and issues:
- Would flat out not work on a Cloudflare Free plan. How do you handle situations where a zone was on a paid plan but then later downgraded to Free (we don't get a notification if the plan tier changed)?
- It would use a slot in the WAF firewall rules (not a huge deal, but how do you handle a situation where a site has used all their slots already for other things?).
The development time more or less becomes a waste whenever Cloudflare introduces HTTP/2 and/or HTTP/3 to the presigned URL hosts.
If the XenForo version of this addon was split into a Free/Paid version, it would definitely be on the Paid side.
Alpha1
Well-known member
The speed benefit of HTTP/2 will be significant. Without it, the benefits offered by presigned URL's will be more than undone by not having HTTP/2 HTTP/3 if there are more than a few attachments.
This is the case with many of the CF features supported by your addon.
Yes, that would become a waste around the year 2035. I'm still waiting for high value suggestions I and others requested to CF in 2018.
digitalpoint
Well-known member
Are you sure? Even the R2 stuff works fine on a Free plan. Maybe I'm misremembering, but I can't think of any feature of this addon that requires a user to be on any paid tier for it to work.
Wildcat Media
Well-known member
Anything I've used in the free tier has worked with no issues, including R2, Workers, and Zero Trust.
nodle
Well-known member
Same goes for me, the add-on has been great along with the support and updates. Thanks again @digitalpoint .
Alpha1
Well-known member
Off the top of my head, features like Polish, Webp, AMP, Mirage, Image resizing are only available for Pro users. There probably are other Pro features for which the addon provides settings. IIRC some analytics as well.
Our Plans | Pricing
Discover which Cloudflare plan is correct for your requirements. Find out more about Cloudflare plan pricing and sign up for Cloudflare here!
I see that these features are faded in the plugin settings for Free users. This is perfect. if you decide to implement custom domains for presigned URLs, then I would suggest the same approach.
Last edited:
digitalpoint
Well-known member
Right, but those are Cloudflare features and nothing that this addon does anything with. There is no code to utilize any of those features in this addon. The addon of course doesn't prevent you from controlling Cloudflare settings, but using those settings isn't something it does (for example this addon doesn't do anything to utilize image resizing which may or may not be available to your Cloudflare plan).Off the top of my head, features like Polish, AMP, Mirage, Image resizing are only available for Pro users. There probably are other Pro features for which the addon provides settings. IIRC some analytics as well.
Our Plans | Pricing
Discover which Cloudflare plan is correct for your requirements. Find out more about Cloudflare plan pricing and sign up for Cloudflare here!www.cloudflare.com
So the difference here is you are talking about the ability to turn on/off Cloudflare settings (or in the case of image resizing, I'm not sure what you are talking about because this addon doesn't even let you turn that on/off). I'm talking about code required to USE features available to certain plans. To date, this addon doesn't offer features that only work on certain Cloudflare plans (it's exactly the reason why it doesn't do anything with Cloudflare Image Resizing).
Again, we are talking about different things here... There isn't a Cloudflare setting to do what you are talking about. It would require backend code as well as presenting configuration pages to configure it. So we are talking about having something along the lines of the Edge Caching page/configuration but then it not working because they are on the wrong Cloudflare plan.
It's also the reason there isn't a Trace Route tool in the addon, because that's only available to Enterprise plans.
Wildcat Media
Well-known member
In
Can that be moved to the R2 bucket? I have something in XF config file that sends the
I have the same for
/internal_data, I have a growing directory page_cache that I presume is for the image proxy.Can that be moved to the R2 bucket? I have something in XF config file that sends the
xfmg directory to the R2 bucket, so is it safe to say that if I move the page_cache contents to R2 and configure it similarly, it could work?
PHP:
$config['fsAdapters']['internal-data/image-cache'] = function ()
{
return \DigitalPoint\Cloudflare\League\Flysystem\Adapter\R2::getAdapter('internal_data/image_cache', 'my-r2-bucket-idata');
}I have the same for
xfmg and it is working fine.
digitalpoint
Well-known member
Nope... no clue what
But ya, you can move it to R2 if you want... however, it's a pretty terrible idea to store cached things in the cloud if you ask me... But do whatever you want.
page_cache is. Probably a third-party addon (no reference to it in XenForo's source). image_cache is the directory that the image proxy uses.But ya, you can move it to R2 if you want... however, it's a pretty terrible idea to store cached things in the cloud if you ask me... But do whatever you want.
