-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rediss:// url clobbers custom TLS options #947
Comments
Merged
paulmelnikow
added a commit
to badges/shields
that referenced
this issue
Aug 20, 2019
ioredis 4.14.0 introduced an issue where custom TLS options are no longer honored. I reported it here: redis/ioredis#947 For now let's downgrade to the latest working version, which I've confirmed working via the script (checked in).
Sorry, duplicate of #940. |
paulmelnikow
added a commit
to badges/shields
that referenced
this issue
Aug 20, 2019
ioredis 4.14.0 introduced an issue where custom TLS options are no longer honored. I reported it here: redis/ioredis#947 This has been preventing the server from using GitHub tokens, however I'm not sure whether or not this has been causing noticeable issues. For now let's downgrade to the latest working version, which I've confirmed working via the script (checked in).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As mentioned at #939 (comment), the change in #939 clobbers any custom
tls
value that may be passed in. It would be better to set{ tls: true }
only whentls
isn't already set by the caller.The text was updated successfully, but these errors were encountered: