openresty / openresty/headers-more-nginx-module

HTTP/3 Connection Issue with Nginx 1.27.1 and headers-more-nginx-module

Open
#165 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
1.8k
Forks
236
Avg merge
1h 34m
Merged PRs (30d)
2

Description

I encountered an issue while using Nginx 1.27.1 with the headers-more-nginx-module. When I added the following line to the "http" block in the global configuration file:

more_set_headers "Server: Microsoft-IIS/8.5";

I was unable to access the site using HTTP/3. The specific symptoms were as follows:

curl --http3-only https://my.domain -Ivi
Note: Using embedded CA bundle, for proxies (228633 bytes)
* Host my.domain:443 was resolved.
* IPv6: (none)
* IPv4: my.server.ip.address
*   Trying my.server.ip.address:443...
*  CAfile: D:\Scoop\apps\curl\current\bin\curl-ca-bundle.crt
*  CApath: none
* ngtcp2_conn_handle_expiry returned error: ERR_HANDSHAKE_TIMEOUT
* Failed to connect to ba7jcm.live port 443 after 10016 ms: Failed sending data to the peer
* closing connection #0
curl: (55) ngtcp2_conn_handle_expiry returned error: ERR_HANDSHAKE_TIMEOUT

Commenting out or removing the added line does not resolve the issue. Additionally, when I recompiled Nginx without the headers-more-nginx-module, it worked fine.

Could you please investigate this issue? Thank you!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with Nginx 1.27.1, HTTP/3, and headers-more-nginx-module using the shown curl --http3-only command and the more_set_headers directive in the http block. Compare the module-enabled and module-disabled builds to isolate the interaction. Done means identifying the cause and confirming that HTTP/3 connections succeed with the module enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, nginx
Domain
backend, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.