Native http remote cache client gets malformed response due to missing Accept header #33092
Description
Current Behavior
When self hosting the cache api, depending on the implementation, I get a malformed tar file back from the server.
The current implementation is via AWS API Gateway, which has a hard requirement to include the Accept header for binary data.
Expected Behavior
The expected behavior is to always get the tar file, without depending on the implementation.
GitHub Repo
No response
Steps to Reproduce
Not really applicable.
Nx Report
Not really applicable.Failure Logs
Package Manager Version
No response
Operating System
- macOS
- Linux
- Windows
- Other (Please specify)
Additional Information
No response