Extremely slow response times with certain servers
Bug
Experiencing 5-10x slower response times when sending HTTP requests to certain servers
Confirmed fixes:
- Offloading remote connection to a local proxy (Proxyman in my case)
- Swapping rustls with native-tls in saucesteals/yaak
Possibly related: reqwest#763
MacDev
@Greg Schier sent example on X DMs
I just reproduced on my Mac. At 3 minutes it’s still not complete via Yaak. Executing the
curldirectly took ~10s.Thanks for the report! Unfortunately we can’t use
native-tlsbecause it doesn’t support TLS 1.3. See also the PR that switches torustls-platform-verifier. Any other ideas?Issues on Github claim to fix it by upgrading rustls or reqwest or both or even tokio (?).
Not too experienced with Rust so I’m not sure how deep these dependencies go and how they peer, but running `cargo update` seems to have fixed it for me. Although now I’m getting blocked by the CDN’s WAF on my example specifically unlike with native-tls or even curl and Postman, as long as the remote certificate is the same I assume the problem with Yaak is fixed.
Do you mean
cargo update? I tried running this withinsrc-tauri/but it didn’t seem to make a difference.Yep cargo update in src-tauri/
> git status
HEAD detached at f62e9029
modified: src-tauri/Cargo.lock
> npm start
Exact curl request imported
Although now the Yaak 2025.3.1 release is also getting a response, but the same 429 from the WAF on my home IP. It could have just been the WAF “blocking” it all along by never responding, but that’s really unusual, and instead, I believe the server is replying with a more compatible handshake whenever it decides to actually block.
Until there is a more reliable server to test with, I assume this is not in the scope of Yaak. Even though it does work on Postman without any blocks, it is purely by chance of it having a node backend for its http requests.