Alexander Turenko

Looks as duplicate of #91.

I guess that URL encoding was missed for those test cases either from scratch or after some change in the testing utilites. I guess we can just fix it without...

Try something like this: https://github.com/tarantool/nginx_upstream_module/tree/82355b8a1276ad584308f3ee4cc6e6129ecb302f#http-headers-and-status

I agree that it is not convenient to add extra logic on nginx side just to implement an API you need. AFAIU the module was initially made with RPC in...

Hope we should not close the issue, but rather add an option that will do something like the Lua code that I linked above.

We have no planned works regarding the upstream module in a near future. You can open a pull request or contact with our [commercial support](https://www.tarantool.io/en/services/).

We can conditionally set -fPIC flag: enable it only for dynamic build.

The question here is about yajl in the submodule. Everything work with system-wide yajl (at least for me).

`HACKING.md` or `CONTRIBUTING.md` in the repository root is okay for developer oriented information. I prefer the first, but seen the second sometimes. I would leave `doc/` for user oriented information.

@LeonidVas AFAIR, you tried to reproduce it, but without lack. Can you share your approach (maybe scripts, workload sizes) and results?