mandatoryprogrammer / mandatoryprogrammer/thermoptic
[Issue] CORS GET vs OPTIONS confusion
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
# What
Making simple GET request returns unexpected HTTP code 204
```sh
2026-01-02T21:51:21.532Z [INFO] [req:2dd5313c-5d66-46c8-9b06-0a7dfd39f50a] Inbound proxy request received. {"url":"https://torrentio.strem.fun/stream/movie/tt12908150.json","protocol":"https","method":"GET","path":"/stream/movie/tt12908150.json"}
2026-01-02T21:51:21.906Z [INFO] [req:2dd5313c-5d66-46c8-9b06-0a7dfd39f50a] Successfully generated response for proxy request. {"status_code":204,"headers_count":12}
```
# Why ?
Seems that thermoptic takes `OPTIONS` request response instead of later `GET` response when CORS is in play
# Workaround
```sh
--disable-web-security
```
( please don't )
# Where ?
https://github.com/mandatoryprogrammer/thermoptic/commit/bf8e5b37c53761fa529e1f07cacac2077a02705f
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting commit bf8e5b37c53761fa529e1f07cacac2077a02705f and tracing how the proxy handles the OPTIONS and GET requests for /stream/movie/tt12908150.json. Reproduce the request with CORS enabled and compare both responses. Done means the GET request is not replaced by the OPTIONS response and returns the expected status instead of 204.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100