cloud flare user-agent check failure (does not happen on web or curl) => format!("{agent}'") fixes this

[singersbalm]

I don't know why this issue occurs, but when sending with the normal user agent cloudlfare denies access. This does not happen when using curl.

curl 'https://www.anime-planet.com/anime/all' \
  -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36'

use reqwest::header::USER_AGENT;

#[tokio::main]
async fn main() {
    let content = reqwest::Client::new()
        .get("https://www.anime-planet.com/anime/all").header(USER_AGENT, "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36'")
        .send()
        .await
        .unwrap()
        .text()
        .await
        .unwrap();
    println!("{}", content);
}

[seanmonstar]

Could be that Cloudflare is being strict about header order, or similar. I'm not sure.

[whispersilk]

It's possible that this is the same issue that @filips123 was having connecting to crunchyroll.com? That issue was solved by enabling the native-tls-alpn feature.