_______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginxby renenglish - Nginx Mailing List - English
_______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginxby renenglish - Nginx Mailing List - English
Hi all: I developed a nginx module and I am glad to share with others . How to submit this module to wiki.nginx.org ? I tried to create an account at wiki.nginx.org but failed. _______________________________________________ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-develby renenglish - Nginx Development
Hi : I want to submit my modules to nginx as a third party module. How to make it ? I googled and someone suggested to just edit the wiki . I tried to create an account of wiki but failed , nginx sent me an email to confirm the register, but I can not login after confirmed , why? I needs your help , thank you in advance ~by renenglish - How to...
Anyone will be interested in this ?by renenglish - Nginx Mailing List - English
OK. Thank you very much . I will do an experiment to find out this 2014/1/16 itpp2012 <nginx-forum@nginx.us> > renenglish Wrote: > ------------------------------------------------------- > > Sorry I can’t get it . > > > > If host A has added the counter and failed to response, the request > > would be failed over to host B with successful response, so the &by renenglish - Nginx Mailing List - English
Sorry I can’t get it . If host A has added the counter and failed to response, the request would be failed over to host B with successful response, so the counter would be added twines. Wouldn’t it ? 在 2014年1月14日,下午5:48,itpp2012 <nginx-forum@nginx.us> 写道: > Unless the request is getting que'd while there is a short wait for host A > to get online AND fail-ovby renenglish - Nginx Mailing List - English
Hi all: The directive "proxy_next_upstream error timeout" takes effect on three network actions: connection, send and recieve. In practice ,we realy want to try next upstream according to in which actions we are. For example, I do not want to try next upstream if some error occurs or timed out when recieving response from upstream, otherwise it maybe duplicate my request . The proxy_neby renenglish - Nginx Mailing List - English
Can any one help ? 2014/1/3 任勇全 <renenglish@gmail.com> > Hi all: > I am wondering if I set: > proxy_next_upstream error timeout; > Fox example , if the requested service is a counter , I issue the request > use the interface http://example.com/incr . The request is failed on my > first host A, then it is passed to the second host B , is the counter > likelyby renenglish - Nginx Mailing List - English
Hi all: I am wondering if I set: proxy_next_upstream error timeout; Fox example , if the requested service is a counter , I issue the request use the interface http://example.com/incr . The request is failed on my first host A, then it is passed to the second host B , is the counter likely be added twice ? thanks . _______________________________________________ nginx mailing list nginx@nginby renenglish - Nginx Mailing List - English