Merged
Conversation
Member
|
"Starting from openresty 1.13.6.2, all our official pre-built packages have switched from OpenSSL 1.0.2 over to the OpenSSL 1.1.0 series" |
Contributor
Author
|
@eguzki if this breaks your local setup we could vendor that resty.evp (SkyLothar/lua-resty-jwt#79) change into APIcast until it is merged. |
Member
|
Just wanted bring heads up on this issue. I can manage to have local setup up and running. |
Setting cjson.array_mt would not serialize non integer elements resulting in always empty array response.
davidor
approved these changes
Jun 11, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrade OpenResty to 1.13.6.2. See the changelog: http://openresty.org/en/changelog-1013006.html
Major change is OpenSSL 1.1, so some FFI code needed to be changed: (cdbattags/lua-resty-jwt#4)
using 3scale/s2i-openresty#58