PipedreamHQ / PipedreamHQ/pipedream
[BUG] Location header missing for proxied 302 response
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
**Describe the bug**
[Connect API Proxy](https://pipedream.com/docs/connect/api-proxy) does not include the "Location" header when the response is a 302. [Example API](https://docs.github.com/en/rest/repos/contents?apiVersion=2022-11-28#download-a-repository-archive-tar) that is expected to return a 302.
**To Reproduce**
1. Connect GitHub app
2. Attempt to get repository archive with a proxied request: `/repos/{owner}/{repo}/tarball/{ref}`
3. Response has 302 status but no "Location" header
**Expected behavior**
A "Location" header is expected in the response, but only these headers are available: `"date", "content-type", "transfer-encoding", "connection", "x-frame-options", "x-xss-protection", "x-content-type-options", "x-download-options", "x-permitted-cross-domain-policies", "referrer-policy", "x-pd-proxy-error", "vary", "cache-control", "x-request-id", "x-runtime"`
**Additional context**
The goal here is to get a signed URL for downloading the contents of a non-public GitHub repo.
Contributor guide
Assessment
This issue has not been assessed yet.