[Bug]: Subsonic POST stream/download ignores credentials in the form body

Open
#111 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
api, backend

Research direction

Start at src/api/subsonic/mod.rs:324, where stream/download hand the raw request straight to the file response without reading the body. Read how the other endpoints parse the form body and validate u/p/t/s/id, then see what the file response builder actually needs from the request (method and Range header) so it can be constructed from those parts. Done when the curl command in the issue authenticates and returns audio, and the existing subsonic tests still pass.

Written by the indexing model from the issue text.

Description

bug

[!NOTE]
This issue was written by Claude (Claude Opus 5.5) from a code review session with @PhrolovaMoe. It was found by reading the code and hasn't been reproduced on a running server.

Version

0.40.0 (feat/desktop, 017a837b)

Area

Other

What happened?

For stream and download, rest never reads the request body so it can hand the request to the file response (src/api/subsonic/mod.rs:324). A client using the advertised formPost extension sends u, p/t/s and id in the body, so those requests fail with "required parameter is missing: u".

Steps to reproduce

curl -X POST -H 'Content-Type: application/x-www-form-urlencoded' -d 'u=me&p=…&c=test&id=…' http://host/rest/stream

Expected behavior

POST stream/download authenticate and play like every other endpoint.

Suggested fix

Read and parse the form body for these too, then build the file response from the remaining request parts (method and Range headers) instead of the original Request.

Dominant language
TypeScript
Stars
4
Forks
1
Avg merge
4h 49m
Merged PRs (30d)
5

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tinystream-dev/tinystream

All issues in tinystream-dev/tinystream

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.