Hi folks!
I am happy to announce the new formal release, 1.13.6.2, of the
OpenResty web platform based on NGINX and LuaJIT:
https://openresty.org/en/download.html
The (portable) source code distribution, the Win32/Win64 binary
distributions, and the pre-built binary Linux packages for Ubuntu
Hi there,
I am excited to announce the new formal release, 1.13.6.1, of the
OpenResty web platform based on NGINX and LuaJIT:
https://openresty.org/en/download.html
Both the (portable) source code distribution, the Win32 binary
distribution, and the pre-built binary Linux packages for all th
Hello!
On Thu, Nov 9, 2017 at 12:19 PM, Joel Parker wrote:
> I am trying to load a table from disk (deserialize) into memory and then
> add, change, remove the values in the table then write it periodically back
> to disk (serialize). I looked at the documentation for the ngx.shared.DICT
> (https:
Haiku OS. Note: this is not an
officially supported target.
The HTML version of the change log with lots of helpful hyper-links
can be browsed here:
https://openresty.org/en/changelog-1011002.html
OpenResty is a full-fledged web platform
by bundling the standard Nginx core, Lua/LuaJIT, lots of
3rd-party Nginx modules and Lua libraries, as well as most of their external
dependencies. See OpenResty's homepage for details:
https://openresty.org/
We have run extensive testing on our Amazon EC2 test cluster and
ensured that all the components (including the Nginx core) play well
together. The latest test report can always be found here:
https://qa.openresty.org/
We also always run the latest OpenResty version in our own global CDN
network (dubbed "mini CDN") powering our openresty.org and other
sites.
Enjoy!
Best regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
as well as most of their external
dependencies. See OpenResty's homepage for details:
https://openresty.org/
OpenResty is supported by the OpenResty Software Foundation, OpenResty
Inc., and the global community.
Thanks!
-agentzh
___
nginx mai
Hi folks,
Long time no releases. We've been very busy setting up the OpenResty
Inc. commercial company in the US. That's why we've been quiet in the
last few months. The good news is that we now have a strong full-time
engineering team that can work on both the OpenResty open source
platform and h
log with lots of helpful hyper-links
can be browsed here:
https://openresty.org/en/changelog-1011002.html
OpenResty is a full-fledged web platform
by bundling the standard Nginx core, Lua/LuaJIT, lots of
3rd-party Nginx modules and Lua libraries, as well as most of their external
dependencies. See OpenResty's homepage for details:
https://openresty.org/
We have run extensive testing on our Amazon EC2 test cluster and
ensured that all the components (including the Nginx core) play well
together. The latest test report can always be found here:
https://qa.openresty.org/
Enjoy!
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
r external
dependencies. See OpenResty's homepage for details:
https://openresty.org/
We have run extensive testing on our Amazon EC2 test cluster and
ensured that all the components (including the Nginx core) play well
together. The latest test report can always be found here:
https://qa.openresty.org/
Have fun!
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ithub.com/openresty/lua-nginx-module/#ssl_certificate_by_lua_block
https://github.com/openresty/lua-resty-core/blob/master/lib/ngx/ssl.md#readme
Even dynamic OCSP stapling is supported ;)
The easiest way to get everything setup is to use the OpenResty bundle BTW:
http://openresty.org/en
* bugfix: fixed errors and warnings with C compilers without
variadic macro support.
* upgraded ngx_iconv to 0.14.
* feature: this module can now be compiled as a dynamic module
with NGINX 1.9.11+ via the "--with-dynamic-module=PATH"
option of "
a full-fledged web platform by bundling the standard
Nginx core, Lua/LuaJIT, lots of
3rd-party Nginx modules and Lua libraries, as well as most of their
external dependencies. See OpenResty's homepage for details:
https://openresty.org/
Best regards,
-ag
ck
You can fork it yourself if you want to :)
Also, you may find the following Lua library for balancer_by_lua* too:
https://github.com/agentzh/lua-resty-chash
> Basicly I'm interested in more flexible/configurable upstream server
> healthchecks (than what's available in stock
thanks Ming Wen
for the editing work of our video recordings.
We can definitely do more of such meetups in the future :)
OpenResty is a high performance web platform based on NGINX and
LuaJIT: https://openresty.org/
Best regards,
-agentzh
[
hange log with lots of helpful hyper-links
can be browsed here:
https://openresty.org/#ChangeLog1009007
OpenResty (aka. ngx_openresty) is a full-fledged web platform
by bundling the standard Nginx core, Lua/LuaJIT, lots of
3rd-party Nginx modules and Lua libraries, as well as most of the
inx modules, and most of their external
dependencies. It is designed to help developers easily build scalable
web applications, web services, and dynamic web gateways. You can find
more about OpenResty on its official web site: https://openresty.org/
See you tomorrow!
mbuild/SOURCES/modules/nginx_tcp_proxy_module-master/ngx_tcp_session.c:351:
> error: 'NGX_LOG_DEBUG_TCP' undeclared (first use in this function)
Maybe you should just use the official ngx_stream_proxy_module in NGINX 1.9.x?
http://nginx.org/en/docs/stream/ngx_stream_proxy_
en to everyone interested in
OpenResty, NGINX, and/or Lua/LuaJIT. We'll have a screen, a
microphone, and some food and beverage as well.
If it goes well, we can do it every couple of months :)
Any updates about this meetup will be published on the group page given above.
See you
ginx).
>
This is expected since the HTTP/2 mode of NGINX reads the request
header into a different place. We should branch the code accordingly.
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Thu, Jan 28, 2016 at 11:19 PM, A. Schulze wrote:
> I could not support with patches but would do some beta testing.
>
Thanks.
> Just to have ask:
> disabling http2 for a location is not possible, isn't it?
>
Nope
-2016-0746, and CVE-2016-0747.
See
<http://mailman.nginx.org/pipermail/nginx/2016-January/049700.html>
for more details.
* change: renamed the source distribution name from
"ngx_openresty" to just "openresty".
Best regards,
-agentzh
__
ainer, I've never tested it anyway). Patches welcome and
volunteers welcome :)
Best regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ier to install via the OpenResty bundle though:
https://openresty.org/
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
code runnable atop the
ngx_http_lua_module.
Hope it helps.
Best regards,
-agentzh
[1] https://metacpan.org/pod/Test::Nginx
[2] https://metacpan.org/pod/Lemplate
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ll the components (including the Nginx core) play well
together. The latest test report can always be found here:
https://qa.openresty.org
Enjoy!
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
d Lua libraries, as well as most of their external
dependencies. See OpenResty's homepage for details:
https://openresty.org/
We have run extensive testing on our Amazon EC2 test cluster and
ensured that all the components (including the Nginx core) play well
together. The latest t
esty specific questions. Please see
https://openresty.org/#Community Thanks!
Best regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
* ARM64: fix ELF bytecode saving.
* feature: parse Unicode string escape "\u{XX...}".
* FFI: add "ssize_t" declaration.
* fix unsinking check.
* feature: add "collectgarbage("isrunning")".
* flush symbol tables in "jit.dump" on trace flush.
The HTML version of the change log with lots of helpful hyper-links
can be browsed here:
https://openresty.org/#ChangeLog1009003
OpenResty (aka. ngx_openresty) is a full-fledged web
platform by bundling the standard Nginx core, Lua/LuaJIT, lots of
3rd-party Nginx
modules and Lua libraries, as well as most of their external
dependencies. See OpenResty's homepage for details:
https://openresty.org/
We have run extensive testing on our Amazon EC2 test cluster and
ensured that all the components (including the Nginx core) play well
together. The latest test report can always be found here:
http://qa.openresty.org
Have fun!
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ve testing on our Amazon EC2 test cluster and
ensured that all the components (including the Nginx core) play well
together. The latest test report can always be found here:
http://qa.openresty.org
Enjoy!
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ible here such that other more knowledgeable people
might have a chance to help you out. Well, just a suggestion.
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
on in your apps, then you should try
those fastcgi or uwsgi options instead.
Just my 2 cents.
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
The next formal release of OpenResty will be based on the new Nginx 1.9.x core.
OpenResty (aka. ngx_openresty) is a full-fledged web application
server by bundling the standard Nginx core, Lua/LuaJIT, lots of 3rd-party Nginx
modules and Lua libraries, as well as most of their external
dependencies. See OpenResty's homepage for details:
http://openresty.org/
We have run extensive testing on our Amazon EC2 test cluster and
ensured that all the components (including the Nginx core) play well
together. The latest test report can always be found here:
http://qa.openresty.org
Have fun!
Best regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
something. Not sure if there's a ready-to-use 3rd-party Lua
libraries that can already parse that for you.
BTW, you're recommended to post ngx_lua related questions to the
openresty-en mailing list instead. Please see
https://openresty.org/#Community for mo
sured that all the components (including the Nginx core) play well
together. The latest test report can always be found here:
http://qa.openresty.org
And we have always been running the latest OpenResty in CloudFlare's
global CDN network.
Have fun!
Best regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
hich can be enabled by the user by
specifying the
--with-luajit-xcflags='-DLUAJIT_ENABLE_LUA52COMPAT'
./configure option while building OpenResty.
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
homepage for details:
http://openresty.org/
We have run extensive testing on our Amazon EC2 test cluster and
ensured that all the components (including the Nginx core) play well
together. The latest test report can always be found here:
http://qa.openresty.org
And we have always been running the latest OpenResty in CloudFlare's
global CDN network for years.
Enjoy!
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
no good. I was talking about extracing nameserver addresses
automatically from /etc/resolv.conf (or similar places in other exotic
operating systems) and feed them into nginx's current nonblocking
resolver.
And yes, for now, the latter workaround should be the simpl
garding the
error message "no resolver defined to resolve ..." over the years.
Alas.
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
penresty.org/
We have run extensive testing on our Amazon EC2 test cluster and
ensured that all the components (including the Nginx core) play well
together. The latest test report can always be found here:
http://qa.openresty.org
Enjoy!
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
r nginx's performance to Apache's worker mpm.)
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ling session tickets to force sessions IDs is a complete loss.
The session tickets are almost always preferred.
> P.S.S. I've used this mail-listing, because it's not Lua-related problem.
>
The openresty-en mailing list is not a Lua-specific list :)
Regards,
-agentzh
_
olve
with the right tools. For example, the on-CPU flame graph tool like
this:
https://github.com/openresty/nginx-systemtap-toolkit#sample-bt
Linux's "perf top" can be useful here as well.
Well, just FYI :)
Regards,
-agentzh
___
more
effective (and cheaper) than SSL session IDs (if available).
BTW, for such ngx_lua questions, please post to the openresty-en
mailing list in the future instead. See
http://openresty.org/#Community for details. That way you may get
responses faster and get more respons
imit_rate builtin variable. You can not only limit on a per-server
basis (across worker processes) but also limit on a cluster-level
(across machines). It's all up to you. Thanks to the flexibility of
Lua.
Regards,
-agentzh
[1] https://github.com/open
ot in use and you use ngx.eof), your
dev upstream connection will also be aborted prematurely.
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
recommended to join the openresty-en mailing list [3] for
such ngx_lua related questions that way you may get more responses and
get responses sooner.
For your very use case, maybe lower level tools like tcpcopy [4] is a
better fit? Not sure though :)
Regards,
-agentzh
[1] https://github.com/b
my use case.
>
It uses the lock mechanism provided by the nginx core to ensure
atomicity and consistency. Basically it uses spinlocks to try first,
failing that, falling back to semaphores.
Regards,
-agentzh
___
nginx mailing list
nginx
at overwrites the existing
"cjson.so" file in place which could cause already running
processes with this ".so" file loaded to crash. thanks
ywsample for the report.
The HTML version of the change log with lots of helpful hyper-links
can be browsed h
Hello!
On Fri, Sep 19, 2014 at 12:50 PM, igorhmm wrote:
> I don't known how to reproduce, not yet :-)
>
> I couldn't identify which worker was responding too, but I can see with
> strace warnings in the old wolker about EAGAIN (Resource temporarily
> unavailable). I can see that because old worker
r size is less than 81568 characters. When
> the parameter size is greater than 81568, we get error 502.
>
Apparently you're hitting the URL length limit on your backend server.
BTW, it's better to post such questions to the openresty-en mailing
list instead:
subrequest because your
"receiving application" might require that.
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
he former should be
on the latter as well. Thank you for your cooperation.
Best regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Fri, Aug 1, 2014 at 2:18 PM, Yichun Zhang (agentzh) wrote:
>
> You can try this: https://github.com/juce/lua-resty-shell
>
But for expensive image compression involved with relatively large
data volumn and CPU computation, it is better to be done in a
dedicated daemon proces
Hello!
On Fri, Aug 1, 2014 at 5:03 AM, c0nw0nk wrote:
> Does anyone know a way you can execute a program via the echo module or
> another way with the lua module ?
>
You can try this: https://github.com/juce/lua-resty-shell
Regards,
gt;
Oh no, os.execute() is blocking. You should avoid that whenever possible :)
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Tue, Jul 29, 2014 at 4:09 PM, Piotr Sikora wrote:
>
> Just to make this clear, the zlib library that Richard is referring to
> is a fork of standard zlib (like ours), not IPP zlib.
>
Okay, I see. Thank you for pointing that out :)
Regar
Hello!
On Tue, Jul 29, 2014 at 3:47 PM, Richard Stanway wrote:
> Thank you for the patch. This solves the issue with streamed responses,
> however when the "if (r->headers_out.content_length_n > 0)" branch is taken,
> eg with static content, I still receive the 2nd alert type below.
Oh, we should
Hello!
On Tue, Jul 29, 2014 at 1:46 PM, Richard Stanway wrote:
> I recently came across a modified version of zlib with code contributed by
> Intel [1] that makes use of modern CPU instructions to increase performance.
> In testing, the performance gains seemed substantial, however when I tried
>
A_ABORT_AT_PANIC"
to the the ngx_lua module build.
The HTML version of the change log with lots of helpful hyper-links
can be browsed here:
http://openresty.org/#ChangeLog1007002
OpenResty (aka. ngx_openresty) is a full-fledged web application
server by
ad, which
> is just incoming data.
>
Sounds like a perfect use case for the tcpcopy tool:
https://github.com/wangbin579/tcpcopy
Best regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
s, as well as most of their external
dependencies. See OpenResty's homepage for details:
http://openresty.org/
We have run extensive testing on our Amazon EC2 test cluster and
ensured that all the components (including the Nginx core) play well
together. The latest test report can always be
ed.
That's cool. Looking forward to that.
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
es" statement. The standard
ngx_memcached module only supports the memcached "get" command while
ngx_memc supports way more commands like "set", "add", "replace",
"append", "prepend", "delete", "incr", "decr&qu
, and etc) on my Amazon EC2 test cluster for
long: http://qa.openresty.org
This module is also well supported on the openresty-en mailing list:
https://groups.google.com/group/openresty-en
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://ma
ence here. OpenResty bundles this ngx_echo module directly.
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
the request
processing lifetime (like when processing the request header).
Because it should be done in the nginx core, and I can do very little
on my 3rd-party modules side about this.
Maxim Dounin: what is your opinion on this?
Best regards,
-agentzh
__
loop.
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
. try to enable the nginx debugging logs for more details for your
problematic request: http://nginx.org/en/docs/debugging_log.html If
you do not understand the debugging logs, you can put it somewhere on
the web (like GitHub Gist) and provide the link here.
Regards,
-agentzh
_
commended to use the rewrite_by_lua
directive directly in the server {} block." and the reason follows
that. The same statement also applies to access_by_lua.
Also, please read the full text of my previous email and correct all
the things I listed
plicate
responses for the same request.
Another suggestion is to check out your nginx error logs for hints (if
any). If the existing info is not enough, you can further enable
nginx's debugging logs: http://nginx.org/en/docs/debugging_log.html
Finally
ACE and nginx gets GET.
>
Will you elaborate your problem and use case? Preferably with a
minimal but still complete example to demonstrate your intention and
problem. As the author of the ngx_memc module, I'd like to have to
look (and find a solution for
always be found here:
http://qa.openresty.org
Just a side note: I recently added the "Profiling page" to the
openresty.org site where you can find useful Flame Graph tools for
analyzing and optimizing OpenResty web apps' online performance (as
well as o
thor of both the ngx_echo and ngx_xss modules, I'd recommend
ngx_xss module for your JSONP use case:
https://github.com/openresty/xss-nginx-module#readme
It should be a bit faster and also safer for this very case.
Regards,
-agentzh
___
ng
failures at least in recent Mac OS X systems. thanks
Hamish Forbes for the report.
* feature: bundled new component
LuaRestyUpstreamHealthcheckLibrary 0.01.
* see the documentation for details:
https://github.com/agentzh/lua-resty-upstream-healthcheck#re
adme
attempt to call ngx.exec after sending
> out response headers
The error clearly indicates the problem. You should not send the
response header before doing redirects (note that, ngx.say, ngx.print,
ngx.flush all trigger sending out the response header automatically,
so avoid them).
Regards
ua?
If you still can, please post the details (bt full ouptuts in gdb, for
example) to the openresty-en mailing list instead:
https://groups.google.com/group/openresty-en Both ngx_lua and
ngx_postgres are supported modules in the OpenResty bundle so you're
welcome to ask there.
that lead to weird issues that are extremely hard to
debug. Just share the NGINX variables you want to share.
Best regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
lawful/lua-nginx-module#ngxredirect
https://github.com/chaoslawful/lua-nginx-module#ngxexec
Speaking of running order, I suggest you read my NGINX tutorials to
prevent such confusions:
http://openresty.org/download/agentzh-nginx-tutorials-en.html
BTW, you're recommended to join the open
deal if you can take a C-land on-CPU flame graph for your
worker processes spining at 100% CPU time, which will give the whole
picture about how CPU time is distributed among all the code paths:
https://github.com/agentzh/nginx-systemtap-toolkit#sample-bt
We've been using this to analyse
ite_by_lua to inject some Lua code and use
ngx.location.capture to issue a subrequest to your postgres location.
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
with high CPU usage by sampling for a few or a dozen seconds:
https://github.com/agentzh/nginx-systemtap-toolkit#sample-bt
The graph would tell us the complete story about all the hot spots
during the sampling window.
Regards,
-agentzh
___
nginx mai
s sounds like a good analysis candidate for the off-CPU flame graph tool:
https://github.com/agentzh/nginx-systemtap-toolkit#sample-bt-off-cpu
This can help us identify exactly what the bottleneck is in your nginx.
Also, measuring the epoll loop blocking latency distribution could be
insi
following sample for more details:
http://openresty.org/#GettingStarted
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Thu, Feb 13, 2014 at 7:50 AM, Reinis Rozitis wrote:
>> Does it enables to request fileA and be able to get fileA + fileB + file C
>> ?
>> Any code example (even the most basic) ?
>
> https://github.com/agentzh/echo-nginx-module#readme
> http://wiki.nginx.org/
cated location (say, location =
/post) for the POST/GET target of your HTML form.
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
content_by_lua '
ngx.header["Content-Type"] = "text/plain"
ngx.say("hello world")
';
or use the default_type directive:
default_type text/plain;
content_by_lua '
ngx.say("hello world")
';
Regards,
-agentz
7;s header to
locate dynamic libraries (like the libluajit-5.1.so.2 file).
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
full-fledged web application
server by bundling the standard Nginx core, lots of 3rd-party Nginx
modules and Lua libraries, as well as most of their external
dependencies. See OpenResty's homepage for details:
http://openresty.org/
We have run extens
(We actually have systemtap-based tools to
measure the epoll loop blocking effect:
https://github.com/agentzh/stapxx#epoll-loop-blocking-distr and the
off-CPU flamegraph tool is very useful for determining the
contributors:
https://github.com/agentzh/nginx-systemtap-toolkit#sample-bt-off-cpu
).
Basic
Hello!
On Sat, Jan 4, 2014 at 11:59 PM, Jeffrey Walton wrote:
> I've been studying agentzh's encrypted session module from
> https://github.com/agentzh/encrypted-session-nginx-module/tree/master/src.
>
Thank you for checking it out! :)
>
> The problem I am having is:
cking other requests served by the same
nginx worker.
Regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
;
> sr->method_name = r->method_name;
> ???
>
Yeah, you can do something like that.
My Nginx modules ngx_echo, ngx_srcache, and ngx_lua all support custom
method names in their subrequests. See
https://github.com/agentzh/echo-nginx-module#echo_subrequest_async
https
Hello!
On Sat, Dec 14, 2013 at 4:42 PM, Yichun Zhang (agentzh) wrote:
> I am happy to announce that the new mainline version of ngx_openresty,
> 1.4.3.7, is now released:
> http://openresty.org/#Download
>
I just kicked out the ngx_openresty 1.4.3.9 release, including an
emer
detailed information from the JIT
compiler.
Below is the complete change log for this release, as compared to the
last (stable) release, 1.4.3.6:
* upgraded LuaJIT to v2.1-20131211.
* see changes here:
https://github.com/agentzh/luajit2/commits/v2.1-agentzh
* bundled LuaRestyCoreLi
for the cooperation.
Best regards,
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Fri, Nov 22, 2013 at 10:07 AM, Roberto Ostinelli wrote:
> can I ask you why the 'stable' version is more recent than the 'mainline'
> one?
>
Because the new mainline version of openresty is not ready to release
atm :) It's expected to be
Hello!
I just released a new stable version for ngx_openresty, 1.4.3.6, which
includes the latest official fix for the security issue CVE-2013-4547
in the Nginx core:
http://openresty.org/#Download
Best regards,
-agentzh
___
nginx mailing list
* set-misc-nginx-module-0.22
* srcache-nginx-module-0.24
* xss-nginx-module-0.04
Just a quick heads-up: I've been working on the LuaJIT 2.1 support and
the new FFI-based API for ngx_lua, which is in the form of the
lua-resty-core library: https://github.com/agentzh/lua-resty-core
he Nginx core) play well
together. The latest test report can always be found here:
http://qa.openresty.org
Have fun!
-agentzh
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ot;This module is no longer needed for Nginx 1.3.9+ because since 1.3.9,
the Nginx core already has built-in support for the chunked request
bodies."
See also https://github.com/agentzh/chunkin-nginx-module#status
Best regards,
-agentzh
___
nginx m
ersion of the change log with lots of helpful hyper-links
can be browsed here:
http://openresty.org/#ChangeLog1004003
OpenResty (aka. ngx_openresty) is a full-fledged web application
server by bundling the standard Nginx core, lots of 3rd-party Nginx
modules and
1 - 100 of 144 matches
Mail list logo