Fix oob with inprogress

[adamdickmeiss]

No description provided.

[Copilot]

Copilot review overview

🟡 Changes recommended

Handle EAGAIN/EWOULDBLOCK correctly before closing healthy proxy connections.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1

Open (1)

• Handle EAGAIN/EWOULDBLOCK on nonblocking recv · New

What changed in this PR

Fixes proxy receive handling to prevent out-of-bounds access and improves URL wildcard matching.

Changes:

• Safely handles non-positive proxy reads.
• Corrects ZURL wildcard matching and empty-pattern handling.
• Receive-side would-block errors still need separate handling from EINPROGRESS.

File	Summary
src/​http.c	Prevents indexing the buffer with a negative receive result.
src/​database.c	Corrects URL wildcard matching logic.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Copilot review overview

🟡 Changes recommended

The nonblocking retry check must be made platform-aware before approval.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1

Open (1)

• Use platform-aware would-block check before closing socket · New

Resolved since last review (1)

• Handle EAGAIN/EWOULDBLOCK on nonblocking recv

[Copilot]

Copilot review overview

🟡 Changes recommended

src/http.c should handle EWOULDBLOCK as an in-progress read condition.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1

Open (1)

• Handle EWOULDBLOCK separately from disconnect in nonblocking recv · New

Resolved since last review (1)

• Use platform-aware would-block check before closing socket

[Copilot]

Copilot review overview

🔵 Needs a closer look

Preserve diagnostic warnings for negative recv() errors before approval.

Review effort: Lite
Findings: None

Resolved since last review (1)

• Handle EWOULDBLOCK separately from disconnect in nonblocking recv