nginx mss patch

[Joshua Zhu]

Hi,

Just out of curiosity, could you please provide some context, i.e. in what
circumstance do you have to change the TCP MSS or the benefit? After all,
there're TCP path MTU discovery mechanisms already.

As for the patch itself, I don't think it's a good idea to set the default
value of mss to 1024, since it will punish those who don't want this
feature. BTW, the TCP_MAXSEG option is not supported by all OS vendors, so
you should test it first (in auto/os/features).

P.S. It seems that the diff format of your patch is wrong.

Regards,
Joshua

On Thu, Jun 9, 2011 at 12:05 PM, Ning Wang <renren.wangning at gmail.com>wrote:

> hi all,
> we made some changes to nginx in order to support tcp mss which is already
> supported by haproxy. you can see the attached patch for details. it is a
> patch against version 0.8.54.
>
> the configuration is very easy.
> server {
>     listen 80 mss=1440;
> }
>
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://nginx.org/mailman/listinfo/nginx
>
>

-- 
Joshua Zhu
http://www.zhuzhaoyuan.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20110609/e65ae60f/attachment.html>