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

On 04/12/2009, at 18:22, "sameer" <nginx-forum@nginx.us> wrote:

> 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: http://forum.nginx.org/read.php?2,27897,27897#msg-27897
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx