fix(api): remove WriteTimeout that aborted downloads and SSE at 120s

[s0up4200]

http.Server.WriteTimeout is an absolute deadline on the whole response, set when the request headers are read, so any response still streaming past 120s gets its socket killed. That aborts large file downloads (DownloadTorrentContentFile) at exactly the 2-minute mark and silently severs long-lived SSE streams (masked by EventSource auto-reconnect). It reproduces even against localhost from inside the pod, which rules out the reverse proxy.

There is no clean per-route escape here: http.ResponseController.SetWriteDeadline can't reach the socket because the gzip middleware (CAFxX/httpcompression v0.0.9, latest) doesn't implement Unwrap(). Since qui is single-user self-hosted, response-side slow-client protection isn't worth permanently breaking streaming, so this drops WriteTimeout while keeping ReadHeaderTimeout/ReadTimeout/IdleTimeout to bound slow-header and idle connections.

Summary by CodeRabbit

• Chores
  • Updated HTTP server write timeout configuration to allow unlimited response writing time, removing the previous deadline enforcement.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 89c029b4-c2c0-4f1a-8e0d-27a533762324

📥 Commits

Reviewing files that changed from the base of the PR and between 8df70a5 and 084315d.

📒 Files selected for processing (1)

• internal/api/server.go

---

Walkthrough

The PR adjusts HTTP server timeout configuration in internal/api/server.go. The WriteTimeout value in NewServer is changed from a fixed 120-second deadline to 0 (unlimited), with comments clarifying that response-side slow-client protection is not applied.

Changes

HTTP Server Write Timeout Configuration

Layer / File(s)	Summary
HTTP server write timeout configuration internal/api/server.go	WriteTimeout is set to 0 instead of 120s, with comments explaining that no separate write deadline is enforced and slow-client response protection is disabled.

🎯 2 (Simple) | ⏱️ ~5 minutes

🐰 A timeout was set too tight, causing slowpokes pain,
Now WriteTimeout is free, unbounded and plain,
Comments explain the choice, crystal and clear,
The server breathes easy, no rush, no fear! 🌙✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: removing WriteTimeout that was causing downloads and SSE streams to abort at 120 seconds.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/download-write-timeout

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}