-
Notifications
You must be signed in to change notification settings - Fork 98
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
Support ssl (--[no-]ssl option) #87
Conversation
Well, that was easier than I thought it'd be. Nice!!! :) @odcinek check this awesomeness out. :) 👍 I technically have merge capability here but lets see the tests pass as well as make sure no one at ChefInc has any objections. |
woot 👍 |
That is pretty easy! Nice! |
Support ssl (--[no-]ssl option)
I'll drop this in the 3.0 release (coming soon now that enterprise support is pedant clean). |
@jkeiser A supplementary explanation, I have merged and tested this function in oc-chef-pedant branch(become 3.0?) locally. It works. |
This doesn't seem to work ... at least not with the omnibus build... knife (10, 11, and 12) get a connection refused on a
This is with chef-12 rc1, but we get the same problem with chef-10 and chef-11. chef-zero doesn't seem to notice or care... from that side, with debug on, I see:
and nothing else. CHef zero is still happy and will still accept new connections, but knife will continue to fail after the initial sandbox report. |
oh, and:
again, from chef 12 rc1 |
@jaymzh |
You talking about #99? The symptom is pretty different, we get no |
@jaymzh
Maybe, the URI scheme of response must be https when using ssl. |
You da man, thanks! |
fix: should set https to rack.url_scheme #87
update for us and #86 .