Skip to content

Tests: upstream read timeout tests. - #1

Open
climagabriel wants to merge 1 commit into
masterfrom
pipe-flush-raw-bufs-on-read-timeout
Open

Tests: upstream read timeout tests.#1
climagabriel wants to merge 1 commit into
masterfrom
pipe-flush-raw-bufs-on-read-timeout

Conversation

@climagabriel

Copy link
Copy Markdown
Owner

Tests for climagabriel/nginx PR: data already read from an upstream is flushed to the client on a read timeout. The four new timeout assertions fail on nginx 1.31.5 and pass with that PR; proxy_noclose.t and proxy_upgrade.t pass too.

  • proxy_timeout.t covers a fixed-length body received with the headers, a fixed-length body received later, a cache-enabled location, and a response without Content-Length. The four assertions are TODO before nginx 1.31.6; update the gate if the change misses that release. It also verifies that the incomplete response is not cached and that a timed-out chunked response has no terminating zero-length chunk.
  • proxy_noclose.t: the existing TODO on "bad backend - no content length" is gated on 1.31.6, mirroring freenginx nginx-tests 718f3b83e5.

When running as root, set TEST_NGINX_GLOBALS='user root;'; otherwise the cache location returns 500 because the worker cannot open the cache path.

https://claude.ai/code/session_01BERKTkJd6r3FPviAuD9SyE

Partially read event pipe buffers are now flushed on read timeouts,
so the proxy_noclose.t no content length test finally passes.  The
$SIG{__WARN__} redefinition was only needed for the "content-length
actually used" test, which succeeds since HTTP/1.1 support.

Claude-Session: https://claude.ai/code/session_01BERKTkJd6r3FPviAuD9SyE
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant