digitalpoint
Well-known member
Ya that’s normal… sounds like it working.
![[DigitalPoint] App for Cloudflare®](/community/data/resource_icons/8/8750.jpg?1692633961){kind=icon}
[DigitalPoint] App for Cloudflare® 1.9.1.1
- Thread starter digitalpoint
- Start date
quimerics
Member
done. How can I be sure it's working on R2?
My images are broken before, but now it's shows fine
ohh thank you
bzcomputers
Well-known member
For those using Brotli compression on your server...
Be aware to take advantage of higher end to end compression rates available through Brotli the following Cloudflare proxy features need to be disabled (all option settings are available within this app).
If you have these proxy features turned off it can pass Brotli 0-11 Compression write through to the end user.
developers.cloudflare.com
blog.cloudflare.com
Be aware to take advantage of higher end to end compression rates available through Brotli the following Cloudflare proxy features need to be disabled (all option settings are available within this app).
- Email Obfuscation
- Rocket Loader
- Server Side Excludes (SSE)
- Mirage
- HTML Minification - JavaScript and CSS can be left enabled.
- Automatic HTTPS Rewrites
If you have these proxy features turned off it can pass Brotli 0-11 Compression write through to the end user.
Content compression
Learn how Cloudflare compresses content for faster web performance.
developers.cloudflare.com
All the way up to 11: Serve Brotli from origin and Introducing Compression Rules
Today, we're enhancing our support for Brotli compression, enabling end-to-end Brotli compression for web content. Compression plays a vital role in reducing bytes during transfers, ensuring quicker downloads and seamless browsing.
blog.cloudflare.com
Mouth
Well-known member
Thanks heaps for sharing
Have now turned off Email Obfuscation, HTML Minification, and Automatic HTTPS Rewrites on my site
Chromaniac
Well-known member
All of these are part of this addon settings page.
Claudio
Well-known member
How is Email Obfuscation supposed to be related to Brotli?For those using Brotli compression on your server...
Be aware to take advantage of higher end to end compression rates available through Brotli the following Cloudflare proxy features need to be disabled (all option settings are available within this app).
You are going to want to disable the proxy features above within this app to be able to pass through your Brotli compressed content without it being decompressed and recompressed. If one of these proxy features is turned on it will require Cloudflare to decompress the HMTL, apply the Cloudflare proxy feature, and then recompress using Cloudflare’s default Brotli level 4 or Gzip level 8 depending on the user's accept-encoding header.
- Email Obfuscation
- Rocket Loader
- Server Side Excludes (SSE)
- Mirage
- HTML Minification - JavaScript and CSS can be left enabled.
- Automatic HTTPS Rewrites
If you have these proxy features turned off it can pass Brotli 0-11 Compression write through to the end user.
View attachment 296985
Content compression
Learn how Cloudflare compresses content for faster web performance.All the way up to 11: Serve Brotli from origin and Introducing Compression Rules
Today, we're enhancing our support for Brotli compression, enabling end-to-end Brotli compression for web content. Compression plays a vital role in reducing bytes during transfers, ensuring quicker downloads and seamless browsing.
Chromaniac
Well-known member
all the settings are modifying the core html served to the end user. email obfuscation is doing the same. from the cloudflare blog post.
This is due to Cloudflare needing to decompress and access the body to apply the requested settings.
This is due to Cloudflare needing to decompress and access the body to apply the requested settings.
bzcomputers
Well-known member
Cloudflare has to decompress the html to "obfuscate" email addresses then recompress the html.
bzcomputers
Well-known member
Default Brotli compression in Cloudflare is set at 4.
Off the top of my head... I would set your server's Brotli compression 4 and check any compressible mime content to see the returned speed and size through a browser. Then set your server's Brotli compression to 11. Test the same content for speed and size. The speed may not be much different (and there are a lot of factors that can affect this), but the content should be slightly smaller. If any content is smaller, then you know it's your originally server compression on that file, since Cloudflare defaults to a Brotli compression of 4.
bzcomputers
Well-known member
I should also mention if any of those same 6 Cloudflare proxy settings listed above, if turned on, will also require the decompression and recompression of any gzip text/html content also.
Without Cloudflare Proxy the served images from R2 will leak the origin ip address which is bad.
digitalpoint
Well-known member
Does anyone actually have Brotli enabled at their origin (that’s what you guys are talking about, not via Cloudflare)? Brotli support at your origin is usually is a lot more work and requires custom compiled versions of your web server.
bzcomputers
Well-known member
We are talking about these settings only...
- Email Obfuscation
- Rocket Loader
- Server Side Excludes (SSE)
- Mirage
- HTML Minification - JavaScript and CSS can be left enabled.
- Automatic HTTPS Rewrites
bzcomputers
Well-known member
Apache 2.4 supports Brotli compression with mod_brotli out of the box. NGINX also with ngx_brotli module.
Last edited:
Ivancas
Well-known member
Litespeed has enabled it as default: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:brotli:start
digitalpoint
Well-known member
Ya, the issue more is compiling the module itself. If you have the module, great... it's simple to enable.
It's been awhile since I went down the road of compiling the Brotli module (about 2 years ago is when I last mucked with it), so maybe it's been simplified now. I ended up in dependency hell and was just over it.
The downside of end to end Brotli compression (for XenForo anyway) didn't really make it so amazing... This page for example has 36,311 tabs/carriage returns in the source (which works out to 13.4% of the page source)... which now you have to keep because you lose the ability to do HTML compression (which more or less negates the higher compression ratio). Making your page 13.4% larger so you can use end to end compression isn't super amazing.
If you were doing server-side HTML compression it would make more sense.
bzcomputers
Well-known member
For Apache the mod_brotli module is quite easy to use now. Install is simple with no settings to mess with and implementation is now just a few small changes from mod_deflate (gzip) if you are already using that and the modules can run side by side without issue.
From:
To:
From:
Code:
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/css text/html text/javascript text/plain text/xml
</IfModule>To:
Code:
<IfModule mod_brotli.c>
AddOutputFilterByType BROTLI_COMPRESS text/css text/html text/javascript text/plain text/xml
</IfModule>I'm using this now on the origin server for HTML minification:
Ngx_http_trim_filter
The ngx_http_trim_filter module is a filter that modifies a response by removing unnecessary whitespaces (spaces, tabs, newlines) and comments from HTML (including inline javascript and css). Trim mod
tengine.taobao.org
