-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
OpenSSL fails to do handshake (or smth else?) after upgrading from Python 2.7 to Python 3.7 #132
Comments
This comment has been minimized.
This comment has been minimized.
Oh, you wrote details inside of HTML comments, which don't render visibly.. |
This comment has been minimized.
This comment has been minimized.
@matingara so ssl is not in a good shape now, but it'll probably work if you switch to |
@matingara so in your Python 3.7 log you're probably receiving an HTTP call instead of HTTPS, which is done by Checker. Try setting |
Thanks. Will have a look at this shortly. Very glad for the support guys!
Joel.
On Fri, 12 Oct 2018 at 20:55, Sviatoslav Sydorenko ***@***.***> wrote:
@matingara <https://github.com/matingara> so ssl is not in a good shape
now, but it'll probably work if you switch to builtin.
Other than that, you need to provide versions of everything and details of
what you did for someone to be able to help you.
Logs you sent differ, which probably also means different versions of
python dists. It's also not clear what are the pre-conditions for such
behavior and whether or not you did HTTP call to trigger the traceback.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#132 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACIJa8kr9V8La7l8_2sSCMtFm9g2Wjekks5ukGcFgaJpZM4XYzPX>
.
|
I set 'checker.on: False' aqnd the error still occurs.
I am investigating what 'switch to builtin' means.
My versions:
Non-working Python 3.7 versions
--------------------------------------------
python: 3.7.0
cherrypy: 18.0.1
macos: 10.13.6 (17G65)
cheroot: 6.5.2
browser: Firefox 62.0.3 (64-bit)
Working Python 2.7 versions
---------------------------------------
python: 2.7.10
cherrypy: 3.8.0
macos: 10.13.6 (17G65)
cheroot: N/A (???)
browser: Firefox 62.0.3 (64-bit)
I hope that helps somewhat.
Thanks.
…On Mon, Oct 15, 2018 at 10:57 PM joel spencer ***@***.***> wrote:
Thanks. Will have a look at this shortly. Very glad for the support guys!
Joel.
On Fri, 12 Oct 2018 at 20:55, Sviatoslav Sydorenko <
***@***.***> wrote:
> @matingara <https://github.com/matingara> so ssl is not in a good shape
> now, but it'll probably work if you switch to builtin.
> Other than that, you need to provide versions of everything and details
> of what you did for someone to be able to help you.
> Logs you sent differ, which probably also means different versions of
> python dists. It's also not clear what are the pre-conditions for such
> behavior and whether or not you did HTTP call to trigger the traceback.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#132 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACIJa8kr9V8La7l8_2sSCMtFm9g2Wjekks5ukGcFgaJpZM4XYzPX>
> .
>
--
http://about.me/joel.spencer
|
What are the new logs? And by builtin I mean cherrypy.server.ssl_module = 'builtin' As for updating CherryPy, I suggest you update to v17.4.0 (last one supporting Python 2) under Python 2.7, check that there's no regressions and then move on to next versions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@matingara is this still reproducible with current Cheroot master? |
It looks like it's solved. Feel free to reopen with new details. |
I'm submitting a ...
Describe the bug. What is the current behavior?
Below is a REPL session using Python 2.7 and another REPL session using Python 3.7.
Can anyone please shed any light on this?
Thanks.
What is the motivation / use case for changing the behavior?
???
To Reproduce
Steps to reproduce the behavior:
PYTHON 3.7 REPL SESSION
Expected behavior
PYTHON 2.7 REPL SESSION
Details
???
Environment
Additional context
???
The text was updated successfully, but these errors were encountered: