classification
Title: https://2.python-requests.org/ missing TLS certicate
Type: Stage: resolved
Components: Library (Lib) Versions:
process
Status: closed Resolution: third party
Dependencies: Superseder:
Assigned To: Nosy List: ned.deily, timdaman
Priority: normal Keywords:

Created on 2019-09-28 13:51 by timdaman, last changed 2019-09-28 16:37 by ned.deily. This issue is now closed.

Messages (2)
msg353452 - (view) Author: Tim Laurence (timdaman) Date: 2019-09-28 13:51
I am unsure how to route this given the recent transition of Requests to PSF so my apologies if this is the wrong spot.

The page where I think most people look for Requests documentation appears to be broken 
  https://2.python-requests.org/

When I look more closely it looks like the server may not have a TLS certificate loaded. 

When I connect via http I get a redirection page to https://requests.kennethreitz.org/en/master/


Below is a dump of what openssl sees when trying to connect.

===========================
$ openssl s_client -connect 2.python-requests.org:443
CONNECTED(00000005)
4608755308:error:14004438:SSL routines:CONNECT_CR_SRVR_HELLO:tlsv1 alert internal error:/BuildRoot/Library/Caches/com.apple.xbs/Sources/libressl/libressl-22.260.1/libressl-2.6/ssl/ssl_pkt.c:1205:SSL alert number 80
4608755308:error:140040E5:SSL routines:CONNECT_CR_SRVR_HELLO:ssl handshake failure:/BuildRoot/Library/Caches/com.apple.xbs/Sources/libressl/libressl-22.260.1/libressl-2.6/ssl/ssl_pkt.c:585:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 7 bytes and written 0 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : 0000
    Session-ID:
    Session-ID-ctx:
    Master-Key:
    Start Time: 1569678290
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
---
msg353463 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2019-09-28 16:37
Thanks for the report but this is not something relevant to this issue tracker.  A quick whois lookup for the domain did not reveal an owner.  Suggest you pursue by asking the PSF infrastructure team via an email to infrastructure-staff at python.org.
History
Date User Action Args
2019-09-28 16:37:47ned.deilysetstatus: open -> closed

nosy: + ned.deily
messages: + msg353463

resolution: third party
stage: resolved
2019-09-28 13:51:46timdamancreate