[Bug] ChatGPT file downloads fail with HTTP 403 when intercepted by Gopeed (Authorization header not forwarded?)
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 56/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- typescript
- Ambito
- networking
Direzione di ricerca
Start by reading the request header listener changed in PR #104 and trace how intercepted downloads are handed to Gopeed. Check whether Fetch requests categorized as xmlhttprequest preserve the Authorization header, using a ChatGPT download request to reproduce the reported 403. Done means the authenticated download succeeds and the original filename is retained; the report does not name test files.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Environment
- Gopeed: 2.0.0-beta4
- Gopeed Browser Extension: 1.1.5
- OS: macOS
- Browser: Microsoft Edge (Chromium)
- Website: https://chatgpt.com/
- Download endpoint:
https://chatgpt.com/backend-api/estuary/content(query parameters redacted)
Bug Description
Downloading files generated by ChatGPT fails when the download is intercepted by the Gopeed browser extension.
Gopeed creates the download task, but the task fails with HTTP 403 and downloads 0 bytes.
The same file can be downloaded successfully using the browser's native download functionality when Gopeed interception is bypassed.
Steps to Reproduce
- Open ChatGPT in Microsoft Edge and sign in.
- Generate a file (e.g., a Markdown
.mdfile). - Enable download interception in Gopeed Browser Extension 1.1.5.
- Click the generated file's download button.
- Observe that Gopeed creates a download task.
- The task fails with
Exception: http request fail, code:403. - Bypass Gopeed interception for
chatgpt.comand retry the download using Edge's native downloader. - The file downloads successfully.
Actual Behavior
- HTTP 403 Forbidden.
- Downloaded size: 0 B.
- Gopeed identifies the filename as
contentinstead of the original.mdfilename. - Failed URL path:
/backend-api/estuary/content.
Expected Behavior
Gopeed should successfully download files that are accessible through the browser's authenticated session, preserving any required authentication headers when transferring the download request.
Investigation
I inspected the successful download request using Edge DevTools (Network tab).
The request:
- Uses the Fetch API (shown as
fetchin DevTools). - Contains an
Authorization: Bearer ...request header. - Succeeds when handled by the browser directly.
When Gopeed intercepts the download, the resulting Gopeed task returns HTTP 403.
Opening the download URL manually in Gopeed also results in HTTP 403, although that test does not preserve the browser's authentication headers.
Possible Cause
This may be related to how the browser extension captures and forwards authenticated requests.
In PR #104:
https://github.com/GopeedLab/browser-extension/pull/104
The request header listener appears to filter the following request types:
types: ["main_frame", "sub_frame"]
Chrome categorizes Fetch/XHR requests as xmlhttprequest in the webRequest API.
Could this prevent the extension from capturing authentication headers associated with ChatGPT's Fetch-based downloads?
This is a hypothesis rather than a confirmed root cause. It would be helpful to verify whether the intercepted download request contains all required authentication headers when handed over to Gopeed.
Workaround
Adding chatgpt.com to the extension's domain exclusion list allows the browser's native downloader to handle ChatGPT files successfully.
Security Note
Authentication tokens, cookies, and signed URL query parameters have been deliberately omitted from this report.
- Lingua principale
- TypeScript
- Stelle
- 382
- Fork
- 27
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di GopeedLab/browser-extension
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
GopeedLab/browser-extension#118 · 1 commento ·
-
接管下载没有反馈Aperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 55/100
GopeedLab/browser-extension#116 ·
-
无法接管chrome的下载Aperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 45/100
GopeedLab/browser-extension#114 · 2 commenti ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 65/100
GopeedLab/browser-extension#112 ·
-
干扰其他插件工作Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 30/100
Tutte le issue di GopeedLab/browser-extension
Issue simili
-
inference/go type/feature
Difficoltà 1/5 1-3 ore Idoneità per principianti 72/100
anomalyco/opencode#65148 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
truapi-release
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
paritytech/product-sdk#529 ·
I maintainer di solito rispondono entro 1 giorno
-
Add: Mansudae TVApertaapproved check:passed streams:add
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
I maintainer di solito rispondono entro 1 giorno
-
[Perf] Canvas layer composition is quadratic: splitRenderLayers re-copies the node array per nodeAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
devlikeapro/waha#2369 ·
I maintainer di solito rispondono entro 5 giorni