HTTP Header Transfer-Encoding

Server NGINX
1

Hi,
I recently upgraded from nginx-0.6.36 to 0.7.62. We are setting cache
friendly headers and after the upgrade we started seeing this
Transfer-Encoding: chunked.

This has broken caching. How can I remove this from the HTTP headers?
There is a old patch from Igor but those changes are already present in
0.7.62.

Server: nginx/0.7.62

Date: Fri, 04 Dec 2009 07:14:33 GMT

Content-Type: image/gif

Last-Modified: Wed, 01 Apr 2009 08:59:50 GMT

Transfer-Encoding: chunked

Connection: close

Vary: Accept-Encoding

Expires: Thu, 31 Dec 2037 23:55:55 GMT

Cache-Control: max-age=315360000, private

Content-Encoding: gzip

Posted at Nginx Forum:

2

@ Igor

FYI I having nginx 0.7.62 on another server which is being used to serve
static content and it is using similar settings. It is not setting the
Transfer-Encoding header.

Here are the gzip settings. The files in question are between 2-50K
unzipped.

server_names_hash_bucket_size 128;
keepalive_timeout  0;
gzip on;
gzip_http_version 1.0;
gzip_comp_level 5;
gzip_proxied any;
gzip_min_length  1100;
gzip_buffers 16 8k;

@Dave - Cache-Control private is to safeguard against old caching
servers which can cause problems with older versions of IE. This
setting doesn’t affect the end user.

Posted at Nginx Forum:

3

On Fri, Dec 04, 2009 at 02:22:30AM -0500, sameer wrote:

Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Expires: Thu, 31 Dec 2037 23:55:55 GMT
Cache-Control: max-age=315360000, private
Content-Encoding: gzip

Because the file is compressed by gzip.
What are your gzip_types settings ?

–
Igor S.
http://sysoev.ru/en/

4

Your content is being content encoded gzip, this is triggering chunked
tranfer encoding.

How large is your reponse body?

Why do you think chunked encoding is breaking caching? I would be more
concerned about the cache-control: private

Cheers

Dave

Sent from my iPhone