package/pubkey.gpg returns invalid HTTP responses from 13.59.70.33

Problem

Downloading the OpenResty repository signing key consistently fails from a Docker build environment.

Reproduction

curl -fsSL https://openresty.org/package/pubkey.gpg

With HTTP/2, curl repeatedly returns:

curl: (92) HTTP/2 stream was not closed cleanly: INTERNAL_ERROR

Forcing HTTP/1.1:

curl --http1.1 -fsSL https://openresty.org/package/pubkey.gpg

returns:

curl: (52) Empty reply from server

Using wget also fails:

wget -O - https://openresty.org/package/pubkey.gpg

Output:

Resolving openresty.org (openresty.org)... 13.59.70.33
Connecting to openresty.org (openresty.org)|13.59.70.33|:443... connected.
HTTP request sent, awaiting response...
Read error (The request is invalid.) in headers.

wget retried multiple times with the same result.

### Environment

- Date: 2026-08-24
- Base image: nginx:stable-bookworm
- Architecture: ARM64
- Debian: Bookworm
- curl: Debian Bookworm package 7.88.1-10+deb12u15
- Docker Engine: 27.1.1
- Docker environment: Colima on macOS
- Location: Brazil

### Expected result

The endpoint should return the OpenResty repository signing key, as documented in the official Debian installation instructions.

### Impact

Docker builds that configure the official OpenResty Debian repository fail before apt-get update and package installation.

No repository files or tests are named. Start by reproducing the failure with the documented curl and wget commands against https://openresty.org/package/pubkey.gpg, then investigate the server-side response path; done means the endpoint returns the OpenResty signing key reliably from the described Docker environment.