![chrome store tubedigger chrome store tubedigger](https://stat.ameba.jp/user_images/20211008/08/macgyverisms/9f/18/p/o0200026115012605006.png)
< expect-ct: max-age=604800, report-uri=""Īnd this is the response body from the server, an html page requesting CAPTCHA < cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0 * Connection state changed (MAX_CONCURRENT_STREAMS = 256)! * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
![chrome store tubedigger chrome store tubedigger](http://www.extremetech.com/wp-content/uploads/2012/01/chromewebstore.png)
> GET /en-gb/blood-blockade-battlefront/episode-6-get-the-lock-out-754075 HTTP/2
![chrome store tubedigger chrome store tubedigger](https://lh5.googleusercontent.com/-HEZLUr4EBME/VUZfaSPSxMI/AAAAAAAATy8/5ub-steUswQ/w620-h469-no/SpeedZooka.png)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Connection state changed (HTTP/2 confirmed) OU= CN=Go Daddy Secure Certificate Authority - G2 * issuer: C=US ST=Arizona L=Scottsdale O=, Inc. * subjectAltName: host "matched cert's "*." * subject: OU=Domain Control Validated CN=*. * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * TLSv1.3 (OUT), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (OUT), TLS handshake, Client hello (1): * CAfile: /etc/ssl/certs/ca-certificates.crt * successfully set certificate verify locations: I think this might be solved if cookies used with PyIDM, however i have no luck trying this