You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2019/02/17 22:40:19 UTC

[Bug 63186] New: Error pages aren't compressed (404, 410)

https://bz.apache.org/bugzilla/show_bug.cgi?id=63186

            Bug ID: 63186
           Summary: Error pages aren't compressed (404, 410)
           Product: Apache httpd-2
           Version: 2.4.29
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: Core
          Assignee: bugs@httpd.apache.org
          Reporter: contact@zikinf.com
  Target Milestone: ---

Hi,

I've just noticed that the 404 et 410 pages of my websites aren't compressed
(no Content-Encoding header, they're sent in plain text).
I use mod_brotli and mod_gzip as a fallback.

Maybe there's something wrong in my setup, but if that's the case, a lot of big
websites have the same problem. Apparently, NGinx, Varnish and Caddy do
compress 404 and 410 responses... but Apache httpd server doesn't.

This is a shame because some websites have a lot of these, not because they're
broken, but because they have a lot of temporary content (events, classifieds,
for exemple).
Plus, it makes the users wait longer to see a broken page, which is quite
annoying.

Is there a good reason why Apache httpd doesn't compress 404 and 410 pages?
During my researches, I couldn't find anything about it, but found some quite
big 404 pages, weighting more than 100KB, which is a lot on Edge connections.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


[Bug 63186] Error pages aren't compressed (404, 410)

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63186

--- Comment #1 from Reindl Harald <h....@thelounge.net> ---
Apache Trafficserver as proxy suffers from the same problem

"content-encoding: br" for 200 responses, no content-encoding for 404 repsones
and since the backend-httpd don't support "br" and backend connections don't
send "Accept-Encoding" by intention to keep compression load from the backend
it's for sure the proxy in my case

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org