答复: How to disable chunked transfer-encoding

Zhang,Tony tzhang at tudou.com
Thu Jun 4 22:11:11 MSD 2009


Hi

Oh, gotcha , I did enable gzip

So, for instance, If I put a squid in front of Nginx which is gzip enabled, the chunked header will be disappeared, correct?

And my question is , will the chunked header do performance impact on static content serving, that's my concern, and considering adding squid like things in front of Nginx?


Thx
Jie

-----邮件原件-----
发件人: owner-nginx at sysoev.ru [mailto:owner-nginx at sysoev.ru] 代表 Maxim Dounin
发送时间: 2009年6月5日 0:58
收件人: nginx at sysoev.ru
主题: Re: How to disable chunked transfer-encoding

Hello!

On Fri, Jun 05, 2009 at 12:23:54AM +0800, Zhang,Tony wrote:

> Hi
>
> I found that Nginx set chunked transfer-encoding as default, so how can I disable this transfer-encoding, because I am serving static content. And by the way, is it a little bit harmful to use chunked transfer encoding on serving static content?

Support for chunked encoding is required for HTTP/1.1 clients,
and nginx doesn't use it for HTTP/1.0 clients (as required by RFC
2616 too), so it should be safe.

But the question is - why chunked used in your case.  It's not
used by nginx for static content with known length.  Possible
reasons include SSI processing truned on and/or gzip enabled
(since resulting length of the response isn't known while sending
headers, and chunked transfer encoding is the only way to keep
connections alive in this case).

Maxim Dounin


No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.12.53/2154 - Release Date: 06/04/09 05:53:00

No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.12.53/2154 - Release Date: 06/04/09 05:53:00

This e-mail is confidential. It may also be legally privileged.If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error,please delete it and all copies from your system and notify the sender immediately by return e-mail.Internet communications cannot be guaranteed to be timely,secure, error or virus-free. The sender does not accept liability for any errors or omissions.


More information about the nginx mailing list