no HTTP response; curl exit 43

[MagicManRandySavage]

Version: 5.1.4
OS: Windows 10
Shell: Git Bash(?)
Anime: Hunter x Hunter, One Piece, any

Describe the bug
run: "ani-cli hunter x hunter" (any anime does this)
Connection error: could not fetch https://hianime.at/search?keyword=One+Piece (no HTTP response; curl exit 43)

Steps To Reproduce

1. Run ani-cli -d flcl
2. Connection error: could not fetch https://hianime.at/search?keyword=flcl (no HTTP response; curl exit 43)

Expected behavior
Should not have a connection error

Additional context
Hasn't worked for weeks through multiple versions, been following other issues hoping for a resolution but nothing in those has fixed it either. Today's update at least changed the error to include "no HTTP response; ".
going to "https://hianime.at/search?keyword=hunter+x+hunter" etc manually in a web browser works fine.

I've been updating ani-cli every few days hoping for an incidental fix, last working early September, and recently attempted manually updating curl, cannot seem to get it above 8.8.0 even following steps provided in another issue trying to get it to 8.21.0 (#1913 (comment))

[U-L-M-S]

This looks like the same thing as #1913, where the exact same exit 43 showed up on Windows and turned out to be the curl that ships inside Git for Windows.

Exit 43 is curl complaining about one of its own arguments, before it even tries to connect. That's why the site loads fine in your browser and why every anime fails the same way. It's not the network and not the site.

Which brings me to the part you already noticed: you can't get curl above 8.8.0. That's the actual clue. Git Bash puts its own folder first in the PATH, so it always runs the curl that came bundled inside Git, at /mingw64/bin/curl.exe, no matter what other curl you install alongside it. 8.8.0 is roughly what Git for Windows 2.45 shipped with. On my machine Git 2.55 ships curl 8.21.0 and the exact same request comes back with a 200.

So the thing to update is Git, not curl. That's also why Brainlazy's scoop update git worked in the other thread while installing curl on its own didn't.

Could you run this inside Git Bash (not PowerShell) and paste the output?

command -v curl; curl --version; git --version

If it shows 8.8.0 from a mingw path, that confirms it. Then depending on how you installed Git:

scoop update git        # if it came from scoop; plain "scoop update" only updates scoop itself
winget upgrade Git.Git  # if you used the installer or winget

Afterwards check again with the same command, you should see 8.21.0 or similar. One heads-up from the other thread: if you go the scoop route and bash stops being found afterwards, you may need to re-add %USERPROFILE%\scoop\apps\git\current\bin to your PATH.

[veloxiromus]

This looks more like that your terminal/powershell can't access to internet. Have you tried entering a normal url through curl? Also does wget work?

[MagicManRandySavage]

command -v curl; curl --version; git --version
results in:

$ command -v curl; curl --version; git --version
/mingw64/bin/curl
curl 8.8.0 (x86_64-w64-mingw32) libcurl/8.8.0 Schannel zlib/1.3.1 brotli/1.1.0 zstd/1.5.6 libidn2/2.3.7 libpsl/0.21.5 libssh2/1.11.0
Release-Date: 2024-05-22
Protocols: dict file ftp ftps gopher gophers http https imap imaps ipfs ipns ldap ldaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS brotli HSTS HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM PSL SPNEGO SSL SSPI threadsafe UnixSockets zstd
git version 2.45.2.windows.1

scoop update git
was successful and ended with

Scoop was updated successfully!
git: 2.55.0.5 (latest version)

running command -v curl; curl --version; git --version again, results in

/mingw64/bin/curl
curl 8.8.0 (x86_64-w64-mingw32) libcurl/8.8.0 Schannel zlib/1.3.1 brotli/1.1.0 zstd/1.5.6 libidn2/2.3.7 libpsl/0.21.5 libssh2/1.11.0
Release-Date: 2024-05-22
Protocols: dict file ftp ftps gopher gophers http https imap imaps ipfs ipns ldap ldaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS brotli HSTS HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM PSL SPNEGO SSL SSPI threadsafe UnixSockets zstd
git version 2.45.2.windows.1

following with scoop update curl shows it was already 8.22.0_1, and updates to 8.22.0_2

curl: 8.22.0_1 -> 8.22.0_2
WARN  Scoop uses 'aria2c' for multi-connection downloads.
WARN  Should it cause issues, run 'scoop config aria2-enabled false' to disable it.
WARN  To disable this warning, run 'scoop config aria2-warning-enabled false'.
Updating one outdated app:
Updating 'curl' (8.22.0_1 -> 8.22.0_2)
Downloading new version
Starting download with aria2 ...
Download: Download Results:
Download: gid   |stat|avg speed  |path/URI
Download: ======+====+===========+=======================================================
Download: 2a9873|OK  |    34MiB/s|C:/Users/Randy/scoop/cache/curl#8.22.0_2#f86ad5e.xz
Download: Status Legend:
Download: (OK):download completed.
Checking hash of curl-8.22.0_2-win64-mingw.tar.xz ... ok.
Uninstalling 'curl' (8.22.0_1)
Removing shim 'curl.shim'.
Removing shim 'curl.exe'.
Unlinking ~\scoop\apps\curl\current
Installing 'curl' (8.22.0_2) [64bit] from 'main' bucket
Loading curl-8.22.0_2-win64-mingw.tar.xz from cache.
Extracting curl-8.22.0_2-win64-mingw.tar.xz ... done.
Linking ~\scoop\apps\curl\current => ~\scoop\apps\curl\8.22.0_2
Creating shim for 'curl'.
'curl' (8.22.0_2) was installed successfully!

running the check again results in:

/mingw64/bin/curl
curl 8.8.0 (x86_64-w64-mingw32) libcurl/8.8.0 Schannel zlib/1.3.1 brotli/1.1.0 zstd/1.5.6 libidn2/2.3.7 libpsl/0.21.5 libssh2/1.11.0
Release-Date: 2024-05-22
Protocols: dict file ftp ftps gopher gophers http https imap imaps ipfs ipns ldap ldaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS brotli HSTS HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM PSL SPNEGO SSL SSPI threadsafe UnixSockets zstd
git version 2.45.2.windows.1

to address the other comment,
curl https://hianime.at
results in html of the page, so I don't believe it's an issue accessing the internet
as for wget, it states wget: command not found