You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because lua_ssl_*(such as lua_ssl_ciphers) are configured in the http/server/location context,
but if there is more than one cosockets will request to diffent SSL/TLS servers in one lua script( or nignx http request), such as sock1 is used for http upstream server, sock2 is used for mysql upstream server, but they use diffent SSL/TLS configure.
And the question is, is it a problem or how to sovle it ?
The text was updated successfully, but these errors were encountered:
laozi2
changed the title
About lua_ssl question
About lua_ssl question?
Jan 4, 2016
@laozi2 Correct. Right now all the cosockets in a single location share the same lua_ssl_* configurations. To solve this, I think we can implement cosocket object level SSL ctx API, as in
And then just reference the SSL ctx on a particular cosocket object before calling sslhandshake, as in
localok, err=cosocket:setsslctx(ssl_ctx)
ifnotokthenreturnerror("failed to set ssl ctx: ", err)
endok, err=cosocket:sslhandshake(...)
What do you think of it? Are you interested in contributing an implementation for this? You can check how the existing ngx.ssl module is implemented in the following PRs, for example.
Because lua_ssl_*(such as lua_ssl_ciphers) are configured in the http/server/location context,
but if there is more than one cosockets will request to diffent SSL/TLS servers in one lua script( or nignx http request), such as sock1 is used for http upstream server, sock2 is used for mysql upstream server, but they use diffent SSL/TLS configure.
And the question is, is it a problem or how to sovle it ?
The text was updated successfully, but these errors were encountered: