Hi Maxim,<div><br></div><div>Are you developing the HTTP/1.1 proxy module? Great news. </div><div><br></div><div>I'm just collecting your old patch and developing a new patch for backend keepalive(<a href="https://github.com/yaoweibin/nginx_upstream_keepalive_patch">https://github.com/yaoweibin/nginx_upstream_keepalive_patch</a> ). I don't know if there is any serious problem. My Test Set is too small. If you find any problem, shoot me. </div>
<div><br></div><div>Thanks.</div><div><br><div class="gmail_quote">2011/7/12 Maxim Dounin <span dir="ltr"><<a href="mailto:mdounin@mdounin.ru">mdounin@mdounin.ru</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello!<br>
<div class="im"><br>
On Tue, Jul 12, 2011 at 07:06:23AM +1000, SplitIce wrote:<br>
<br>
> Today I read through the code of the<br>
> <a href="http://mdounin.ru/hg/ngx_http_upstream_keepalive/" target="_blank">http://mdounin.ru/hg/ngx_http_upstream_keepalive/</a><br>
><br>
> Although my understanding of nginx internals is limited, I did C programming<br>
> back in my youth. From my understanding of the code there is very little<br>
> modification needed in order to add HTTP (backend HTTP/1.1) keep alive.<br>
><br>
> As I see it to complete this the protocol has to be updated to the version<br>
> of 1.1 and the "Connection: keep-alive" header needs to be added to<br>
> responses, this would add very basic keep alive support to nginx I would<br>
> beleive (please do correct me if I am wrong)<br>
<br>
</div>:)<br>
<br>
The fun starts somewhere near "the protocol has to be updated to<br>
the version of 1.1". My current diff is something like "7 files<br>
changed, 688 insertions(+), 29 deletions(-)" and still growing.<br>
<div class="im"><br>
> To make the modifications howeaver it would be necessary to edit the nginx<br>
> source (or make a new http backend plugin, which could be mostly copy and<br>
> paste) -- I would be more specific on this matter but <a href="http://nginx.org" target="_blank">nginx.org</a> is down<br>
> currently and im not able to get the latest version of the source to look<br>
> at.<br>
><br>
> Would it be possible for someone with a knowledge of nginx internals to take<br>
> a look at this and tell me if I am going about this the correct way? I am<br>
> going to fiddle a bit and see if I can produce a plugin once <a href="http://nginx.org" target="_blank">nginx.org</a> comes<br>
> back up.<br>
<br>
</div><a href="http://nginx.org" target="_blank">nginx.org</a> looks perfectly up from here (and <a href="http://isup.me" target="_blank">isup.me</a> says the<br>
same), probably it's just you.<br>
<br>
Maxim Dounin<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>
</blockquote></div><br></div>