fix: raise the proxy and tunnel read and write timeouts to 120s

[alnr]

Closes #302

graceful.WithDefaults applies a 5s read and 10s write timeout to the proxy and tunnel server. Any exchange slower than that was cut off mid-flight, so the client got an empty reply with no status and no error:

$ curl localhost:4000/long -v
* Empty reply from server
curl: (52) Empty reply from server

The reporter's observed 9.5s-works / 10.5s-fails boundary matches the 10s write deadline exactly. The read timeout caused the same silent truncation for slow or large request bodies. The upstream here is the developer's own application and may legitimately take longer than either.

Raises both to 120s. graceful.WithDefaults only fills in zero values, so non-zero values set on the server pass through untouched.

Note that ReadHeaderTimeout stays at graceful's 5s, since net/http prefers it over ReadTimeout for the header phase — request headers still have to arrive promptly, while the body now gets the full 120s.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JYzGVwAKQ4ormxRHZg1eDu

[coderabbitai]

📝 Walkthrough

Walkthrough

The proxy adds read and write timeout flags, validates and applies them when creating HTTP servers, adjusts header deadlines, and routes reverse-proxy server creation through the new helper. Response-writer unwrapping and tests cover streaming, hijacking, and timeout behavior.

Changes

Proxy timeout and response handling

Layer / File(s)	Summary
Server timeout configuration cmd/cloudx/proxy/helpers.go, cmd/cloudx/proxy/helpers_test.go	Adds timeout flags and config fields, validates timeout values, applies HTTP server deadlines, and tests default, configured, invalid, and write-timeout behavior.
Reverse proxy writer integration cmd/cloudx/proxy/helpers.go, cmd/cloudx/proxy/helpers_test.go	Routes reverse-proxy server creation through newServer, adds Unwrap() to responseStatusCatcher, and tests Flush, Hijack, and status forwarding.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Sequence Diagram(s)

sequenceDiagram
  participant CLI
  participant registerConfigFlags
  participant newServer
  participant http.Server
  participant ReverseProxy
  CLI->>registerConfigFlags: configure read-timeout and write-timeout
  registerConfigFlags->>newServer: pass timeout durations
  newServer->>http.Server: apply read, header, and write deadlines
  ReverseProxy->>http.Server: serve proxied request
  http.Server-->>ReverseProxy: enforce configured response deadline

Loading

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	It explains the bug and fix, but it doesn't follow the required template sections or include the checklist and further comments.	Add the template headings for big picture, related issue/design doc, checklist, and further comments, and fill the required checklist items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The changes address issue #302 by removing the default deadline that caused empty proxy responses and by adding the requested timeout controls.
Out of Scope Changes check	✅ Passed	The extra Unwrap fix and tests are directly related to proxy response handling and streaming behavior, so they are not out of scope.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title matches the main change: increasing proxy/tunnel read and write timeouts.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/302-proxy-timeouts

---

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.}