Show all posts by user
Any other nginx or tech related discussion may be entered here.
Re: [PATCH] Avoid unnecessary restriction on nohash http variables - 3 years ago
Thanks! It looks good. Cheers, Alexey. вт, 26 окт. 2021 г., 03:42 Maxim Dounin <mdounin@mdounin.ru>: > Hello! > > On Thu, Aug 19, 2021 at 09:34:39PM +0300, Alexey Radkov wrote: > > > # HG changeset patch > > # User Alexey Radkov <alexey.radkov@gmail.com> > > # Date 1629395487 -10800 > > # Thu Aug 19 20:51:27 2021 +0300 > > # Node Iby alexey.radkov - Nginx Development
[PATCH] Avoid unnecessary restriction on nohash http variables - 3 years ago
# HG changeset patch # User Alexey Radkov <alexey.radkov@gmail.com> # Date 1629395487 -10800 # Thu Aug 19 20:51:27 2021 +0300 # Node ID a1065b2252855730ed8e5368c88fe41a7ff5a698 # Parent 13d0c1d26d47c203b1874ca1ffdb7a9ba7fd2d77 Avoid unnecessary restriction on nohash http variables. When I use variables with long names albeit being tagged as NGX_HTTP_VARIABLE_NOHASH, Nginx says "cby alexey.radkov - Nginx Development
Re: Arbitrary async tasks and services with nginx-haskell-module - 8 years ago
I cannot compare them side by side as far as I know lua very little, but I can try to list some prominent features of haskell. 1. Haskell compiles libraries to machine codes and can be loaded as simple as dlopen() lets it. 2. Strong static typing won't let occasionally replace a handler by another one of a wrong type. 3. Even more, strong static typing allows reasoning about impossibility ofby alexey.radkov - Other discussion
Arbitrary async tasks and services with nginx-haskell-module - 8 years ago
Here is the article from my blog: http://lin-techdet.blogspot.com/2016/10/asynchronous-handlers-in-nginx-haskell.html Link to the module: http://github.com/lyokha/nginx-haskell-moduleby alexey.radkov - Other discussion
Nginx Custom Counters module - 8 years ago
See https://github.com/lyokha/nginx-custom-counters-module Just finished implementing. Perhaps it might be interesting or useful for others. Cheers.by alexey.radkov - Ideas and Feature Requests
Re: rewrite / proxy_pass different bahaviour in 1.0 and 1.2 - 12 years ago
Maxim, thank you! This "bug" was a "feature" in our own proxy module based upon standard nginx proxy module. When i ported changes in 1.2 into our module i was surprised why some of our rules were not working until i found this change. We cannot use something like proxy_pass http://$arg_a$request_uri; because our directives do not support this. So currently i just rby alexey.radkov - Nginx Mailing List - Russian
rewrite / proxy_pass different bahaviour in 1.0 and 1.2 - 12 years ago
Hi guys. Is the following result of a bug fix in proxy module in 1.2 series? Imagine following config (sorry, i do not know how to format it here): events { worker_connections 1024; } http { upstream ubackend { server localhost:8020; } server { listen 8010; server_name router; location /test.html {by alexey.radkov - Nginx Mailing List - Russian
 |
 |
 |
 |
|