Resty | The minimalist framework of RESTful | REST library

Just figured out how it works. I have to use internal as the prefix to call this method.

TL; DR: The problem lied not within certificate validation, but in a security group rule.

1. As Marc Gravell kindly pointed out, the DangerousAcceptAnyServerCertificateValidator already achieves the aim of ignoring certificate validation problems.
2. After deploying the same code in an EC2 instance in the same VPC and subnet I noticed, that the .NET Core code was making one more HTTP call than the Go code (Although I still do not understand why). The IP adress was not within the allowed IP range of outgoing traffic, thus blocking the request and causing a timeout of the HttpClient.

First I want to tell you that what you did in Java is AES-256-CBC encryption with PKCS7 padding. The number 256 is the key length in bits, which means 32 bytes as you used in Java code.

For communicating between multiple docker-compose clients, you need to make sure that the containers you want to talk to each other are on the same network.

For example, (edited for brevity) here you have one of the docker-compose.yml

Just use recursion:

Fantastic, I got it working now.

The solution is simply waiting! it was confusing because I can't find any explanation about this on the doc, and also the error message isn't user-friendly.

in summary, after the dev app is created, and the public key is uploaded there, we have to wait for a few hours/days, and then the credentials will eventually be usable.

The waiting part is applied to both open epic and app orchard dev accounts.

It is impossible to share a cosocket object (and, therefore, a redis object, check this answer for details) between different requests:

The cosocket object created by this API function has exactly the same lifetime as the Lua handler creating it. So never pass the cosocket object to any other Lua handler (including ngx.timer callback functions) and never share the cosocket object between different Nginx requests.

However, nginx/ngx_lua uses a connection pool internally:

Before actually resolving the host name and connecting to the remote backend, this method will always look up the connection pool for matched idle connections created by previous calls of this method

That being said, you just need to use sock:setkeepalive() instead of sock:close() for persistent connections. The redis object interface has a corresponding method: red:set_keepalive().

You'll still need to create a redis object on a per request basis, but this will help to avoid a connection overhead.

I found the solution but I did not the root cause of problem:

I changed my Nginx-Lua image from danday74/nginx-lua to fabiocicerchia/nginx-lua, and It worked like a charm. the first one was created on Nginx version 1.16 and the last one was created by Nginx 1.19.

You should ffi.load your .so library before using functions from it.