nginx mss patch

[Ning Wang]

MTU discovery mechanisms does not work very well for ADSL users with PPPoE
link, especially when they use wireless home router. client users may failed
to upload picture or music or any other big post requests. here is a post
regarding to this problem.
http://hi.baidu.com/ybbmdf/blog/item/287d878b498e04d6fc1f1079.html( i am
sorry it is in Chinese). so we have to decrease the tcp package size.

BTW, thanks for your advice for the patch, its very nice.

On Thu, Jun 9, 2011 at 1:10 PM, Joshua Zhu <zhuzhaoyuan at gmail.com> wrote:

> 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
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://nginx.org/mailman/listinfo/nginx
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20110609/ccd045b7/attachment.html>