It looks like tripadvisor.com have decided to tell their CDN to not let us through any more. We will have to disable that test and look for an alternative.
$ curl -v https://www.tripadvisor.com/
* Trying 23.43.34.19:443...
* TCP_NODELAY set
* Connected to www.tripadvisor.com (23.43.34.19) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: businessCategory=Private Organization; jurisdictionC=US; jurisdictionST=Delaware; serialNumber=3175592; C=US; ST=Massachusetts; L=Needham; O=TripAdvisor LLC; CN=www.tripadvisor.com
* start date: May 26 00:00:00 2021 GMT
* expire date: Jun 15 23:59:59 2022 GMT
* subjectAltName: host "www.tripadvisor.com" matched cert's "www.tripadvisor.com"
* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 Extended Validation Server CA
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x56293b6c5e10)
> GET / HTTP/2
> Host: www.tripadvisor.com
> user-agent: curl/7.68.0
> accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
< HTTP/2 403
< server: AkamaiGHost
< mime-version: 1.0
< content-type: text/html
< content-length: 269
< expires: Wed, 04 Aug 2021 13:34:52 GMT
< date: Wed, 04 Aug 2021 13:34:52 GMT
<
<HTML><HEAD>
<TITLE>Access Denied</TITLE>
</HEAD><BODY>
<H1>Access Denied</H1>
You don't have permission to access "http://www.tripadvisor.com/" on this server.<P>
Reference #18.6757dd58.1628084092.66864afa
</BODY>
</HTML>
* Connection #0 to host www.tripadvisor.com left intact
Do we need these tests? If I understand this correctly, these tests are basically testing HTTP::Message->content_charset(), which is already covered by the HTTP::Message test suite.
It looks like tripadvisor.com have decided to tell their CDN to not let us through any more. We will have to disable that test and look for an alternative.