-
Notifications
You must be signed in to change notification settings - Fork 134
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
add ssl support #5
base: master
Are you sure you want to change the base?
Conversation
We can reuse ["type"] field instead of introducing separate ["ssl"] field. Missed it while developing a variant. |
Now its
|
type = "http", | ||
|
||
|
||
type = "https", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because type = "http"
is a more common case, we should at least put it in a comment here?
@sitano Thank you for the patch! Will you please add some corresponding test cases to the existing test suite (under |
hi @agentzh . thanks for the comments . i will do all the changes you described . tests too . i was going to provide ssl session caching a bit later, but i will look into it . |
@sitano Great! Thanks! |
Any news about getting the ssl support merged? |
@pasikarkkainen Yeah, this is long overdue. Sorry about that. I'll look into this soon. |
Ping? :) |
hi @agentzh, why not just change socket to resty.http? And we do't have to bind this module with ngx.upstream, so we can use this module with balancer by lua ? |
@agentzh Any update on this? |
@doujiang24 Please review this PR when you have a chance. Thanks! |
Also, there's conflicts between this branch and master that must be solved before this PR can be merged. |
@agentzh yes, sorry. no still. |
@sitano is it likely you'll be able to fix/resolve the merge conflict, or should someone else pick up this work? Thanks. |
Hi. Better pickup if in a hurry. I am very short on time currently.
…Sent from my iPhone
On 6 Dec 2016, at 11:25, pasikarkkainen ***@***.***> wrote:
@sitano is it likely you'll be able to fix/resolve the merge conflict, or should someone else pick up this work? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
This work is being completed at: Shopify#1 |
I have added ssl handshake if requested to support https during health checking. It also able to skip cert checks which is fine for my use case. Session caching could be added in the future.