Forumlar / Cotonti / Support / gzip on nginx - buggy?

Eugene
#32558 2012-01-12 19:03

For several month time to time I was getting the same error on different sites:

- in case of switching OFF gzip - in top left corner of browser 4 digits|symbols appear (like "348a")

- in case of switching gzip ON - in attempt to edit page - browser respond about "Content Encoding Error/ The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression"

Debugging make me sure that those numbers are not from any variable of CMF, so asked hoster support to figure out. I find out that hoster using nginx for "proxying" the request (I think it's became more and more popular)

But I want you to consider their reply here:

В коде Вашей CMS используется протокол HTTP/1.1, например:
[root@]# grep -i -r "HTTP/1" *
rc.php: header('HTTP/1.1 400 Bad Request');
rc.php: header('HTTP/1.1 404 Not Found');
rc.php: header('HTTP/1.1 304 Not Modified');
system/functions.php: header('HTTP/1.1 ' . $response_code);
system/functions.php: header('HTTP/1.1 ' . $env['status']);
system/functions.php: header('HTTP/1.1 ' . $env['status']);
system/cache.php: header('HTTP/1.1 304 Not Modified');
watermark.php: header('HTTP/1.1 403 Forbidden');
watermark_users.php: header('HTTP/1.1 403 Forbidden');

nginx не может корректно обрабатывать протокола HTTP/1.1 .
В таких случаях мы рекомендуем использовать в коде сайтов протокол HTTP/1.0.
Так же возможен вариант переноса сайтов на CloudServer, где можно будет не устанавливать nginx в качестве фронтенда к apache.

They say that nginx is not working properly with HTTP/1.1 - better to use 1.0 version...

Do you think better edit headings for HTTP protocol ? How to solve gzip compression problem - I think it is big factor of perfomance?