<div>Hi,<br></div><div><br></div><div>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.</div>
<div><br></div><div>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).</div>
<div><br></div><div>P.S. It seems that the diff format of your patch is wrong.<br></div><div><br></div><div>Regards,</div><div>Joshua</div><div><br></div><div class="gmail_quote">On Thu, Jun 9, 2011 at 12:05 PM, Ning Wang <span dir="ltr"><<a href="mailto:renren.wangning@gmail.com">renren.wangning@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">hi all,<br>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.<br>
<br>the configuration is very easy.<br>
server {<br> listen 80 mss=1440;<br>}<br><br>
<br>_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://nginx.org/mailman/listinfo/nginx" target="_blank">http://nginx.org/mailman/listinfo/nginx</a><br>
<br></blockquote></div><br><br>-- <br>Joshua Zhu<br><a href="http://www.zhuzhaoyuan.com">http://www.zhuzhaoyuan.com</a><br>