Yes that seems much better than taking over the u->headers_in.content_length_n field. Didn't realize just how similar memcache was :) Thanks. On Thu, Nov 28, 2013 at 8:10 PM, Maxim Dounin <mdounin@mdounin.ru> wrote: > Hello! > > On Thu, Nov 28, 2013 at 07:39:32PM +1030, SplitIce wrote: > > > I am aware atleast 2 others are considering developing patches with one >by splitice - Nginx Development
I am aware atleast 2 others are considering developing patches with one the module maintainer. I wanted to improve so have attempted this upgrade myself. Its only a small patch, from my understanding its the upstream length field that has changed between 1.4.x and 1.5.x. I would like to know if I have done something I shoudnt etc so as to improve my nginx knowledge. The commits - https://githubby splitice - Nginx Development
An IPv6 based fallback is not the only solution we want to support, ultimately we would like to be able to load-balance between them as well. An error_page based solution would not assist. I also get the feeling that such a hack would have large implications, while either an additional parameter or another directive would be a simple & clean solution to a real identified deficiency. This kinby splitice - Nginx Development
Ruslan, its funny you should mention this, I am testing a patch to do just that at the moment. Once I am certain that its not leaking memory and I have reviewed it in regards to the nginx code standards Ill post it in this email thread in case it is of use for others. On Fri, Nov 22, 2013 at 11:56 PM, Ruslan Ermilov <ru@nginx.com> wrote: > On Tue, Nov 19, 2013 at 09:09:34PM +1030, Splby splitice - Nginx Development
Attached is the patch, This is the first time I have created a variable or really done anything inside the http request processing flow so feel free to let me know if there is a better way to do something or if I have any edge cases. This patch provides a $upstream_connecting variable which contains the IP address and port of the upstream being connected. If there is no upstream, it will returnby splitice - Nginx Development
Hi, We use proxy_bind to ensure traffic always goes out via the same address as the incoming request i.e the bound address where a server has many addresses. This is a hard restriction in our use case. We are looking to add support for IPv6 backends, we would like to allocate a single IPv6 outgoing address per client although this is not a fixed restriction at this stage. IPv6 backends may be usby splitice - Nginx Development
Looking at the documentation it seems there is no way to specify a proxy bind address for both IPv4 and IPv6. You can specify one or the other, but never both. This is a particular issue when a configuration is setup to allow for a failure in IPv6 transit / routing. Is it possible to get a proxy_bind_v6 directive? Regards, Mathew _______________________________________________ nginx-devel mailiby splitice - Nginx Development
Thank you agentz, that looks amazing. I will be including that in the next server software push. And also Maxim, thank you for you for taking the time to prepare those figures. I am going to my own testing and presuming that holds with our usecase / modules I will be deploying --with-debug myself. Its definitely worth it for <5% any day. Regards, Mathew On Sat, Sep 28, 2013 at 5:01 AM, Yichby splitice - Nginx Mailing List - English
Maxim, it happened during a flood so that is likely. The flood has ceased now, and I didn't have time to find the cause during the incident. I am not sure what the conditions are for replicating, it doesn't appear to be limit_req related. I fixed the issue for us by adding a guard to the access log to not log such cases (since our problems where related to the sheer amount of log entries being wby splitice - Nginx Development
I know this patch was made for 1.5.x however I patched our 1.4.x build (internal modules are in the process of being upgraded currently). However I am still getting 000 in the logs. I am currently crawling the change logs for similar patches. Any chance you can remember any similar issue being resolved in the 1.5.x branch? Thanks, Mathew On Thu, Jul 25, 2013 at 9:28 PM, Maxim Dounin <mdouniby splitice - Nginx Development
My bad I missed that sentence in the docco. Thanks, Ill be using map. That blog lead me down the wrong track. On Wed, Sep 18, 2013 at 11:26 PM, Maxim Dounin <mdounin@mdounin.ru> wrote: > Hello! > > On Wed, Sep 18, 2013 at 11:15:54PM +0930, SplitIce wrote: > > > I also think I found that 0 length keys wont be stored. This isn't in the > > documentation but if I undby splitice - Nginx Mailing List - English
I also think I found that 0 length keys wont be stored. This isn't in the documentation but if I understand the code correctly they aren't, is this correct? I could use a map then and get considerable flexibility. On Wed, Sep 18, 2013 at 11:06 PM, SplitIce <mat999@gmail.com> wrote: > Does anyone know if there is any truth to this blog post: > http://gadelkareem.com/2012/03/25/limitby splitice - Nginx Mailing List - English
Does anyone know if there is any truth to this blog post: http://gadelkareem.com/2012/03/25/limit-requests-per-ip-on-nginx-using-httplimitzonemodule-and-httplimitreqmodule-except-whitelist/ And if so where about in the code its implemented? I was trying to find out if its possible to use a map to control limit req/s limits but I still cant find the code that does what that article says is possiblby splitice - Nginx Mailing List - English
Is the patch on this mailing list (forgive me I cant see it)? Ill happily test it for you, although for me to get any personal benefit there would need to be a size restriction since 99.9% of requests are just small HTML documents and would not benifit. Also the standard caching (headers that result in a cache miss e.g cookies, cache-control) would have to be correct. At the very least Ill readby splitice - Nginx Development
This is an interesting idea, while I don't see it being all that useful for most applications there are some that could really benefit (large file proxying first comes to mind). If it could be achieved without introducing too much of a CPU overhead in keeping track of the requests & available parts it would be quite interesting. I would like to see an option to supply a minimum size to restriby splitice - Nginx Development
I agree, I view dead code at run-time as a liability. Something that can go wrong. At compile time, you know everything about the sytem, the config script makes assumptions and the binaries shouldnt work if moved to a different OS etc anyway. I am not a nginx developer just a C++ developer. On Mon, Aug 5, 2013 at 4:28 PM, Serguei I. Ivantsov < manowar@gsc-game.kiev.ua> wrote: > I thinby splitice - Nginx Development
Would it be possible to get a feature added to this module? What I would like is a variable containing the name of the zone of the rule that is responsible for the 503 error. Would be great for where there are limits on many factors. _______________________________________________ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-develby splitice - Nginx Development
As the owner of http://x4b.org/ I am probably the best person to answer this question. We use a combination of nginx, many open source nginx modules (both modified and unmodified) and lots of proprietary glue in our HTTP stack. Our TCP and UDP proxy stack is pure custom now days (expect exciting things!). Our DNS system is a combination of open source and lots of custom glue. I take from tby splitice - How to...
On a side note, a good feature for nginx would be a small SHM zone for storing SSL certificates cross reload (paired with a filemtime value) to speed up reloads. I run alot of SSL certificates myself (not using SNI but unique IPs) around 300 per node (and 7 nodes refreshed up to every minute) and have noticed the decent CPU percentage. On Sat, Feb 2, 2013 at 12:22 AM, António P. P. Almeida <by splitice - Nginx Development
Ive been working on my first nginx module (well more specifically, a fork of an existing module with permission). Pretty close to done however found one thing thats lacking in the nginx core (as far as I can tell). UDP Listening. There is support for UDP sockets, so sending of UDP data is fine. Howeaver binding and listening seems to be full of hardcoded TCP related stuff. Is this correct or amby splitice - Nginx Development
Found a segfault in the ngx_http_syslog module. I dont have the contact details for any of the ngsru team that developed it so I am posting it in the mailing list in the hope a few are members. Occurs when error_page is used, tested on a 504 error with config similar to @e504 { proxy_pass ...; } error_page 504 @e504; Backtrace: #0 0x080f2ac7 in ngx_http_syslog_error_handler (log=0x8cf4608,by splitice - Nginx Development
Just thought I would say that the files from bitbucket work on the latest 1.3.x branch without any major modification. Just copy in the modified module file and make the modifications to the other files to match the changes. On Sun, Mar 11, 2012 at 2:45 PM, Peter Halasz <list@pengo.org> wrote: > Hi Laurence Rowe, > > Thanks for the update! I'm using your newly patched version wiby splitice - Nginx Development
Just thought i would add that support for error logging over syslog would be great. Udp would be even better as we could send it straight out to the remote storage and skip the local disk (io). If you need a test for your module once you write it just let me know. Although i plan on taking a look at tengines solution since im already using some of his patches. On Jul 16, 2012 3:46 PM, "姚ä¼by splitice - Nginx Mailing List - English
And I take it that the first block is the 'default' so I should add my 'bad-site' block last like you have? Just clarification. I really like the way you did this, way more clean than the if based system I was planning to use (and less evil). On Wed, Jul 4, 2012 at 3:23 AM, Oleksandr V. Typlyns'kyi <wangsamp@gmail.com > wrote: > Tomorrow Jul 4, 2012 at 03:01 SplitIce wrote: > > &by splitice - Nginx Mailing List - English
Ok, I was reading up on the map module and it seems the right way to do this, howeaver I really couldnt think of a way to do this (without just using the if alternative way). Blocking domains is what I want to do, my server blocks are per IP accepting everything for any domain, howeaver I want to filter certain domains away by way of proxy passing or redirecting to another URL. _________________by splitice - Nginx Mailing List - English
I came up with a crude solution, proxy_max_temp_file_size. By limiting the max size in cached paths to 50mb I should make it impossible for someone to store GBs of data to the disk before the cache manager runs. On Sun, Jul 1, 2012 at 2:11 AM, Brian Akins <brian@akins.org> wrote: > > On Jun 30, 2012, at 3:20 AM, SplitIce wrote: > > > Hmm this presents a rather large issueby splitice - Nginx Mailing List - English
Hmm this presents a rather large issue for me. Is it possible to get the upstream response size in lua and set a variable to influence proxy_no_cache? If it is ill learn lua. On Fri, Jun 29, 2012 at 11:55 PM, Maxim Dounin <mdounin@mdounin.ru> wrote: > Hello! > > On Fri, Jun 29, 2012 at 11:28:08PM +1000, mat999@gmail.com wrote: > > > I have a question. If the file being wby splitice - Nginx Mailing List - English
I have a question. If the file being written to a cache exceeds max size what behavior happens? As I can think of it there are 3 possible outcomes. 1. File is written and later cleaned up by the cache manager (bad) 2. File isnt written. It is recognized that it can't be cached. 3. The file is written and truncated (bad) Thanks Sent from my iPad _______________________________________________by splitice - Nginx Mailing List - English
Haha, serves me right. Did a clean build (make clean, configure, build) and the issue was fixed. Strange but im glad it works. As always thanks for all the hard work. nginx is amazing. On Thu, Jun 28, 2012 at 5:16 PM, SplitIce <mat999@gmail.com> wrote: > Been tearing out my hair for hours today trying to get proxy_store to > work. Is there a minimum version for proxy_store with variaby splitice - Nginx Mailing List - English
Been tearing out my hair for hours today trying to get proxy_store to work. Is there a minimum version for proxy_store with variables support? My nginx refuses to work with simple stuff like set $md5 test; proxy_store /data/nginx/1/$md5;" instead trying to store to / evident by the error log 2012/06/28 17:13:24 5700#0: *1 open() "/usr/html/img/diagram.png" failed (2: No such fileby splitice - Nginx Mailing List - English