SSL error: [Errno 0] Error is present also on Python 3.7

[Safihre]

❓ What kind of change does this PR introduce?

• 🐞 bug fix
• 🐣 feature
• 📋 docs update
• 📋 tests/coverage improvement
• 📋 refactoring
• 💥 other

📋 What is the related issue number (starting with #)

cherrypy/cherrypy#1618

❓ What is the current behavior? (You can also link to an open issue here)

cherrypy/cherrypy#1618
Error is still present with Python 3.7.2, as reported by users on Windows and Linux machines.

❓ What is the new behavior (if this is a feature change)?

Always suppress this error.

📋 Other information:

📋 Checklist:

• I think the code is well written
• I wrote good commit messages
• I have squashed related commits together after the changes have been approved
• Unit tests for the changes exist
• Integration tests for the changes exist (if applicable)
• I used the same coding conventions as the rest of the project
• The new code doesn't generate linter offenses
• Documentation reflects the changes
• The PR relates to only one subject with a clear title
  and description in grammatically correct, complete sentences

---

This change is 

[Safihre]

Is there a chance for an update on this one?

[webknjaz]

It would be nice to have some reproducible testcases for this...

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@378f099). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master     #180   +/-   ##
=========================================
  Coverage          ?   75.59%           
=========================================
  Files             ?       22           
  Lines             ?     3516           
  Branches          ?        0           
=========================================
  Hits              ?     2658           
  Misses            ?      858           
  Partials          ?        0

[Safihre]

I think it can be reproduced with Selenium and Chrome, but that's a big additional test load.

[webknjaz]

@Safihre it's fine. It could go to cron job without being executed each time. I suspect that it might be connected to TLS 1.3 and maybe ciphers mismatch...

[webknjaz]

TCPdump/Wireshark dump may be useful for analysis...