Thanks, that's what I was using. On Thu, 4 Feb 2016, 6:30 p.m. Yichun Zhang (agentzh) <agentzh@gmail.com> wrote: > Hello! > > On Wed, Feb 3, 2016 at 7:09 PM, SplitIce wrote: > > What is the appropriate way to allocate memory during the stream? The > http > > context has a pool member as part of the request structure, what is the > > equivalent in the stream moby splitice - Nginx Development
Hey All again, Quick Question regarding the Stream Module. What is the appropriate way to allocate memory during the stream? The http context has a pool member as part of the request structure, what is the equivalent in the stream module context? Thanks in Advance, Mathew _______________________________________________ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailby splitice - Nginx Development
Oh I wish I could go, bit far to fly (from Aus) unfortunately. On Thu, Feb 4, 2016 at 9:07 AM, Yichun Zhang (agentzh) <agentzh@gmail.com> wrote: > Hi folks, > > I've recently created the Bay Area OpenResty Meeup group on meetup.com: > > http://www.meetup.com/Bay-Area-OpenResty-Meetup/ > > You're welcome to join us in this group. > > We're currently planning aby splitice - Nginx Mailing List - English
The map module is also a noticeable omission tied into the lack of variables. On Thu, Feb 4, 2016 at 11:13 AM, Yichun Zhang (agentzh) <agentzh@gmail.com> wrote: > Hello! > > On Wed, Feb 3, 2016 at 3:37 PM, SplitIce wrote: > > I have been taking a look at the Stream modules for use in a particular > > application. I noticed the entire subsystem lacks any variable supporby splitice - Nginx Development
Hi All, I have been taking a look at the Stream modules for use in a particular application. I noticed the entire subsystem lacks any variable support. - Is variable support planned? - Is there a significant reason for the omission? Regards, Mathew _______________________________________________ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginby splitice - Nginx Development
Issue found. If worker_processes is set at the start of the config file the feature works fine, if it is set at the end of the config file it does not. On Wed, Nov 25, 2015 at 9:38 AM, SplitIce <mat999@gmail.com> wrote: > Ok, > > I have found it to be a configuration bug. With a fresh configuration > (default configuration from package, with reuseport added) and reuseport >by splitice - Nginx Development
Ok, I have found it to be a configuration bug. With a fresh configuration (default configuration from package, with reuseport added) and reuseport enabled the feature works (same 3.18 kernel, same nginx binary). Now I just need to identify which line of our production configuration creates this bug. I will update when I know more. On Wed, Nov 25, 2015 at 12:42 AM, Valentin V. Bartenev <vbarby splitice - Nginx Development
Note: In all cases the nginx binary deployed is the exact same, next I will be disabling the lua module and srcache in the unlikely event they are at fault and try to replicate this issue on a 100% clean binary. I dont see how either module can interact on this level myself. On Wed, Nov 25, 2015 at 12:42 AM, Valentin V. Bartenev <vbart@nginx.com> wrote: > On Wednesday 25 November 2015 0by splitice - Nginx Development
Ok, I have a virtual machine which has a residual kernel of 3.16.0-0.bpo.4 (Debian wheezy-backport's) available I confirmed the issue is replicatable on that machine too. The testing methodology is using ab from 12 other remote servers (hopefully in order to prevent collisions) at a fairly low rate of 1r/s (the virtual machine with this older kernel is not particularly large). During this testingby splitice - Nginx Development
Hi all, I couldn't find anything in the mailing list about this issue, surely we are not the only one? When activating reuseport I am seeing all requests be served from a single nginx process. All others are just idling (SIGALARM interruption of epoll_wait / epoll_wait timeout according to strace). Process 442 attached - interrupt to quit epoll_wait(60, 8225010, 512, 4294967295) = -1 EINTR (Intby splitice - Nginx Development
In case its relevant we have been running a very similar patch Nils since the introduction of the syslog feature. Since the default and expected format on the /dev/log socket is to write without hostname perhaps unix socket should default to hostname=0 ? On Wed, Oct 28, 2015 at 6:21 AM, Nils Hermansson <3tnica@gmail.com> wrote: > Created a new patch as disabling hostame as a configuratby splitice - Nginx Development
Hi All, Yesterday we discovered a possible compatibility issue with a certain configuration, HTTP2 and Firefox. This configuration works successfully in Chrome and other HTTP2 enabled browsers, however Firefox users are unable to connect (connection reset). The pertinent part of the configuration is a port with SSLv3 enabled in the supported protocols (risk associated with POODLE attack has beenby splitice - Nginx Development
Shortly after sending my response I found the commit for BoringSSL adding the function. https://boringssl.googlesource.com/boringssl/+/4d4bff89bb8ec345d289412f0f7f135c6e51b1a6%5E!/ On Thu, May 28, 2015 at 2:43 AM, W-Mark Kubacki <wmark+nginx@hurrikane.de> wrote: > 2015-05-05 15:39 GMT+02:00 chen <gzchenym@126.com>: > > > > This is v1 of the patchset the implementing tby splitice - Nginx Development
Mark, From memory SSL_CIPHER_is_AES is a BoringSSL addition isnt it? I did a quick look over the OpenSSL source and it does not seem like its been added either. I havent had a chance to compile this yet to confirm it, but if correct then this is not compatible with OpenSSL and possibly other SSL libraries. Regards, Mathew On Thu, May 28, 2015 at 2:43 AM, W-Mark Kubacki <wmark+nginx@hurrikby splitice - Nginx Development
Good Job. Perhaps rather than changing the constants, they could be exposed as configuration options? On Wed, May 13, 2015 at 12:28 PM, chen <gzchenym@126.com> wrote: > 1) we will have that fixed > 2) no api is exposed by openssl that we can use to trigger a FLUSH, use > SSL_write is what we can do. If we inspect the data using wireshark, you > will find out that one SSL_writeby splitice - Nginx Development
Indeed. The Wikipedia page covers it quite well FYI - http://en.wikipedia.org/wiki/HTTP/2 So what is really being asked is for a roadmap for the implementation of the non-draft differences (i.e HTTP/2.0 allows for non TLS communication, and multiplexes differently). I am sure nginx will once again be at the forefront of technology and implement it when possible. :) On Wed, Feb 11, 2015 at 11:38by splitice - Nginx Mailing List - English
You appear to be behind a proxy, look at the output - http://10.254.40.54:15871/cgi-bin/blockpage.cgi?ws-session=3162698151 Nothing really to do with nginx. On Sat, Jan 3, 2015 at 4:10 PM, Yugal Mullick <yugal.mullick@gmail.com> wrote: > Hi Team, > > > > Getting below error while downloading and extracting Nginx. > > > > > > techmahindra@techmahindra-Thinkby splitice - Nginx Development
Is it just me or would access_records be per worker and hence this module not work with workers > 1 ? Additionally for (i = 0; i < NGX_HTTP_KNOCK__IP_DB_SIZE && i < ngx_http_knock_next_free_slot; i++) { if (access_records.ip_addr == ip_addr) Perhaps using the nginx Red-Black tree here would lead to better performance (in place of O(n)) and remove the limitation on number of IPs.by splitice - Nginx Development
expires -1; Does not create an "Expires: -1" header. It should create: Expires: Thu, 01 Jan 1970 00:00:00 GMT A time in the “Expires” field is computed as a sum of the current time and time specified in the directive. If the modified parameter is used (0.7.0, 0.6.32) then time is computed as a sum of the file’s modification time and time specified in the directive. On Frby splitice - Nginx Development
>> the "error_log" and "access_log" directives now support logging to syslog. Is this referring to the Open Source edition? It looks to be so. I hope so :) On Tue, May 27, 2014 at 11:59 PM, Maxim Dounin <mdounin@mdounin.ru> wrote: > details: http://hg.nginx.org/nginx/rev/0351a6d89c3d > branches: > changeset: 5711:0351a6d89c3d > user:by splitice - Nginx Development
Theres actually an example using the memcached module (and echo module to get the request body). The main advantage to the lua module is if you wanted to do something custom (e.g processing) or transmit it over a different protocol not available as an extension. On Mon, May 26, 2014 at 7:17 PM, Paulo Silva <pauloasilva@gmail.com> wrote: > On Mon, May 26, 2014 at 9:28 AM, SplitIce <mby splitice - Nginx Development
Yes, connecting with SOCK_NONBLOCK shouldnt block. I don't believe this is mentioned previously. If your code blocks (e.g blocking connect or blocking send) then it would reduce nginx throughput substantially. Thats the point I was trying to make. Have you investigated srcache ( https://github.com/openresty/srcache-nginx-module/)? srcache_store could be used without srcache_fetch to store only. Yby splitice - Nginx Development
As in blocking send and connect? I don't know the specifics of Unix Sockets, but don't they block when the buffer fills (I know FIFO queues do)? On Mon, May 26, 2014 at 9:22 AM, Paulo Silva <pauloasilva@gmail.com> wrote: > Hi, > I'm not sure whether I will face problems with other filters modifying > the response body after mine, but for know I'm comfortable as I can > rebuildby splitice - Nginx Development
Thank you, that makes sense and a bit of testing reveals that is correct. On Wed, Apr 16, 2014 at 8:59 PM, Maxim Dounin <mdounin@mdounin.ru> wrote: > Hello! > > On Wed, Apr 16, 2014 at 08:38:10PM +1000, SplitIce wrote: > > > Hi all, > > > > I have spent the day troubleshooting why one server in our network > reloaded > > / tested configuration extremby splitice - Nginx Mailing List - English
Hi all, I have spent the day troubleshooting why one server in our network reloaded / tested configuration extremely slowly. We have found that server_names scales very poorly, once a certain point is reached (approx 5.5k entries globally, 5k entries for a single host) performance drops from a <0.5s reload time to 15s+. The large host of ~5,000 entries is a malware domain zone and all serverby splitice - Nginx Mailing List - English
Thats an interesting figure, certainly worthy of consideration. I am only interested in performance savings, the memory used is negligible as this particular limit takes the brunt of quite a few attacks (insecure Wordpress blogs are quickly becoming the bane of my existence). I am not yet sure if there is room for gains here yet, was mainly curious if thought had been placed in this area (e.g exiby splitice - Nginx Development
I guess our configuration is a but of an edge case pretty much every server serves at-least one /24 (with the intention to raise this to /22 eventually). Anyway thanks for the answer, I am going to go investigate what would be involved in developing a patch for this feature and if it would provide a performance increase in our use case. On Thu, Mar 13, 2014 at 7:10 PM, Igor Sysoev <igor@sysoby splitice - Nginx Development
Has anyone put any thought into the possibility of a $binary_server_addr variable? Sometimes its quite useful to limit certain events by server_addr instead of the client address (e.g to limit requests made by certain UA's or other events). _______________________________________________ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-develby splitice - Nginx Development
I would like to second this. On Tue, Jan 28, 2014 at 11:03 PM, JackB <nginx-forum@nginx.us> wrote: > The subject is a quote of Maxim Dounin in a discussion found here: > http://forum.nginx.org/read.php?29,246885,246902#msg-246902 > > It would be nice to have a detailed list of SPDY functionality that could > be > used as a DDoS vector. And it would be even better, to havby splitice - Nginx Mailing List - English
Im not sure that patch would suit my needs, simply because most of the time I am matching on the upstream address only and need it to work regardless of the port (i.e a regex match on just the IP component). Perhaps your patch could be extended to support - map $upstream_peer_addr $bind_addr { 127.0.0.1:8001 127.0.0.1; 127.0.0.2 http://127.0.0.1:8002/ 127.0.0.1; [::1]:8003 ::1; }by splitice - Nginx Development