Skip to content

Native http remote cache client gets malformed response due to missing Accept header #33092

@ScaredStorm

Description

@ScaredStorm

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

Metadata

Metadata

Assignees

Labels

priority: highHigh Priority (important issues which affect many people severely)scope: corecore nx functionalitytype: bug

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions