Custom Query (2297 matches)
Results (85 - 87 of 2297)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#2503 | invalid | Unable to build nginx quic | ||
Description |
I am trying to build nginx quic with nginx version as release-1.25.0 but facing below error
cc -c -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter -Werror -g -I/src/boringssl/include -I src/core -I src/event -I src/event/modules -I src/event/quic -I src/os/unix -I objs \
cc -c -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter -Werror -g -I/src/boringssl/include -I src/core -I src/event -I src/event/modules -I src/event/quic -I src/os/unix -I objs \
src/event/ngx_event_openssl.c: In function ‘ngx_ssl_get_curve’: src/event/ngx_event_openssl.c:5110:20: error: ‘TLSEXT_nid_unknown’ undeclared (first use in this function)
src/event/ngx_event_openssl.c:5110:20: note: each undeclared identifier is reported only once for each function it appears in make[1]: * [objs/Makefile:999: objs/src/event/ngx_event_openssl.o] Error 1 make[1]: Leaving directory '/src/nginx-quic' make: * [Makefile:10: build] Error 2 root@ubuntu:/src/nginx-quic# Could you please confirm is this known issue or am i missing anything? Commands i ran
cd /src/nginx-quic/
auto/configure |
|||
#2502 | duplicate | HTTP2 with non SSL causing downgrade to HTTP0.9 for HTTP1.0/HTTP1.1 clients | ||
Description |
I have an nginx installation with 2 servers, one listening HTTPS and one listening HTTP, both of them with http2 enabled in the listen directive. The HTTP server is quite simple and it's just used by an AWS ALB to perform healthchecks: server {
} The HTTPS is working just fine, but I cannot stablish successful connections to the HTTP server with non HTTP2 capable clients: $ curl -v http://127.0.0.1:81 --http1.1
curl: (1) Received HTTP/0.9 when not allowed As you can see, even forcing curl to send HTTP1.1 headers, nginx is downgrading it to HTTP0.9, causing curl to reject the protocol and disconecting. Performing the same test in https works fine: $ curl -o test -k -v https://127.0.0.1 --http1.1
Connected to 127.0.0.1 (127.0.0.1) port 443 (#0)
< HTTP/1.1 200 OK < Server: nginx < Date: Tue, 30 May 2023 11:53:48 GMT < Content-Type: text/html; charset=UTF-8 < Transfer-Encoding: chunked < Connection: keep-alive < Set-Cookie: <redacted> < Set-Cookie: <redacted> < As far as I understand, as long as the client is sending a HTTP protocol header, nginx should honour this header and try to serve this protocol instead of forcing to use the oldest one, specially when it's a protocol from begining 90s which now is considered ineficient.Also this is the behaviour being observed in HTTPS connections. The current behaviours leaves the HTTP servers with HTTP2 enabled in an almost non-funciontal state as most of the HTTP clients doesn't support HTTP0.9. For example AWS ALB is not capable to perform the healthchecks, curl is not working, nor wget, etc. |
|||
#2501 | invalid | TLS handshake fails with internal_error if signature_algorithms is not provided | ||
Description |
I suspect this issue was introduced when implementing ticket #814 |