Timeline



03/28/22:

11:38 Ticket #2339 (nginx fails to process "allow" statements on subsequent keepalive requests) updated by Maxim Dounin
Works fine here. Tested with the following config: […] Testing with …
08:07 Ticket #2339 (nginx fails to process "allow" statements on subsequent keepalive requests) created by ctheune@…
This is a config that used to work on nginx 1.8.1 but when ported to …

03/24/22:

21:02 Ticket #2335 (no resolver defined to resolve localhost) updated by stefankaerst.web.de@…
indeed […] works like a charm, whereas […] produces …

03/22/22:

18:00 Ticket #2338 (why nginx output status 200 in access.log when client get unexpected ...) closed by Maxim Dounin
invalid: > yes,on my case, the whole response was not complete writeten to …
17:19 Ticket #2338 (why nginx output status 200 in access.log when client get unexpected ...) updated by boost2020@…
and in error log,it output 408 code: 2022/03/20 17:41:05 [debug] …
17:07 Ticket #2338 (why nginx output status 200 in access.log when client get unexpected ...) reopened by boost2020@…
The only information nginx has is if the whole response was written to …
14:58 Ticket #2338 (why nginx output status 200 in access.log when client get unexpected ...) closed by Maxim Dounin
invalid: > i find two abnornal thing: > 1) access log status 200 That's …
09:08 Ticket #2338 (why nginx output status 200 in access.log when client get unexpected ...) updated by manmanjyb@…
append nginx debug log before epoll_wait null ,there writev happed …
08:15 Ticket #2338 (why nginx output status 200 in access.log when client get unexpected ...) updated by manmanjyb@…
sorry, the nginx debug log timestampe is different from the strace …
08:04 Ticket #2338 (why nginx output status 200 in access.log when client get unexpected ...) created by manmanjyb@…
in a special envirment, the net quality between client and nginx is so …

03/20/22:

00:17 Ticket #2336 (mTLS client verification fails in >=1.21.4) closed by Maxim Dounin
invalid: Thanks for the details. With the provided key usage extensions I was …

03/18/22:

19:35 Ticket #2337 (Version disclosure when server_tokens is set off) closed by Maxim Dounin
invalid: It looks like you are trying to set server_tokens off; in a …
15:16 Ticket #2336 (mTLS client verification fails in >=1.21.4) updated by boris_sandler.cysiv.com@…
yes, that is correct. Client cert was signed by (self-signed) Root CA …
11:16 Ticket #1756 (Invalid or Binary in URI causes core 400 and 500 errors, plus binary ...) updated by tanji@…
Note that this suggestion of named error pages is coming from a nginx …
09:08 Ticket #2337 (Version disclosure when server_tokens is set off) created by tanji@…
With server_tokens set to off: $ curl -I localhost HTTP/1.1 200 OK …

03/17/22:

22:24 Ticket #2335 (no resolver defined to resolve localhost) updated by Maxim Dounin
As soon as there are any variables in the proxy_pass parameter, …
22:16 Ticket #2334 (regex capture with $1 not work in 1.20.0 but in 1.19.10) closed by Maxim Dounin
invalid: Thanks for confirming. That's exactly why using numbered captures is …
21:58 Ticket #2336 (mTLS client verification fails in >=1.21.4) updated by Maxim Dounin
Not sure I understand your certificate configuration. From the …
10:31 Ticket #2335 (no resolver defined to resolve localhost) updated by stefankaerst.web.de@…
hi Maxim, thanks for your fast reply. may I add something.. I guess …
02:12 Ticket #2334 (regex capture with $1 not work in 1.20.0 but in 1.19.10) updated by rawbin-@…
finally found the case, It seems that some detail was missing, and the …

03/16/22:

18:56 Ticket #2336 (mTLS client verification fails in >=1.21.4) created by boris_sandler.cysiv.com@…
I am using Nginx for performing mTLS authentication, terminating it …

03/15/22:

15:06 Ticket #2334 (regex capture with $1 not work in 1.20.0 but in 1.19.10) updated by Maxim Dounin
Description changed
Both location blocks provided works fine here. Note though that using …
14:31 Ticket #2335 (no resolver defined to resolve localhost) closed by Maxim Dounin
invalid: The no resolver defined to resolve ... error means that per the …
12:32 Ticket #2335 (no resolver defined to resolve localhost) updated by stefankaerst.web.de@…
Description changed
12:24 Ticket #2335 (no resolver defined to resolve localhost) created by stefankaerst.web.de@…
I just downloaded nginx-1.21.6.tar.gz and tried a proxy pass …
03:27 Ticket #2334 (regex capture with $1 not work in 1.20.0 but in 1.19.10) updated by rawbin-@…
Description changed
03:19 iShot2022-03-15 11.19.17.png attached to Ticket #2334 by rawbin-@…
rule $1
03:18 Ticket #2334 (regex capture with $1 not work in 1.20.0 but in 1.19.10) updated by rawbin-@…
Description changed
03:17 iShot2022-03-15 11.16.04.png attached to Ticket #2334 by rawbin-@…
rule prefix
03:13 Ticket #2334 (regex capture with $1 not work in 1.20.0 but in 1.19.10) created by rawbin-@…
with the following rule: […] when access with …

03/11/22:

22:21 Ticket #808 (Defining http2 without ssl leads to HTTP/1.1 client failure) updated by stefankaerst.web.de@…
3.2. Starting HTTP/2 for "http" URIs …
21:37 Ticket #2333 (Cache-Control header spills over to different location) closed by Maxim Dounin
invalid: That's because / in your configuration is processed via an internal …
20:15 Ticket #2333 (Cache-Control header spills over to different location) created by hoffic-cz@…
I'm using the following configuration: events {} http { …

03/10/22:

23:13 Ticket #2329 (Unexpected request routing when Host header value contains colon) updated by Maxim Dounin
Thanks for the details. In this particular case Django's syntax …
11:54 Ticket #2332 (Include $request_id in error.log messages) created by heikojansen@…
In order to make debugging easier it might make sense to include the …

03/09/22:

12:09 Ticket #2329 (Unexpected request routing when Host header value contains colon) updated by Pēteris Caune
If you think this can be beneficial, please elaborate why do you think …

03/08/22:

01:19 Ticket #2330 (nginx does not choose the right certificate (with "IP" server block)) updated by kailifeforge@…
Oops, this is embarrassing... Thank you for correcting my …

03/07/22:

23:29 Ticket #2331 (proxy_cookie_path / proxy_cookie_domain and custom cookie fileds) closed by Maxim Dounin
invalid: It looks like you are trying to rewrite data in the cookie itself, not …
23:10 Ticket #2330 (nginx does not choose the right certificate (with "IP" server block)) closed by Maxim Dounin
invalid: > I am bashed by a strange problem that nginx seems always choose the …
10:28 Ticket #2331 (proxy_cookie_path / proxy_cookie_domain and custom cookie fileds) created by Tux12Fun@…
Hi, currently I have to hide a web-page behind nginx but this website …
10:21 Ticket #2330 (nginx does not choose the right certificate (with "IP" server block)) updated by kailifeforge@…
Description changed
10:17 result.example.com-9443 attached to Ticket #2330 by kailifeforge@…
result log for example.com:9443
10:17 result.192.168.1.77-9443 attached to Ticket #2330 by kailifeforge@…
result log for 192.168.1.77:9443
10:16 result.127.0.0.1-9443 attached to Ticket #2330 by kailifeforge@…
result log for 127.0.0.1:9443
10:16 9443ssl.conf attached to Ticket #2330 by kailifeforge@…
configuration file to reproduce this problem
10:15 Ticket #2330 (nginx does not choose the right certificate (with "IP" server block)) created by kailifeforge@…
I am bashed by a strange problem that nginx seems always choose the …
00:14 Ticket #2329 (Unexpected request routing when Host header value contains colon) closed by Maxim Dounin
wontfix: Anything after the : is considered to be the optional TCP port (see …

03/04/22:

14:49 Ticket #2328 (ngx_http_uwsgi_module removes chunked-encoding, but doesn't modify ...) updated by dener.kup@…
Here is the link to the issue in werkzeug: …

03/03/22:

11:47 Ticket #2329 (Unexpected request routing when Host header value contains colon) created by Pēteris Caune
Here's my nginx.conf: […] I'm expecting the server to return …
10:29 Ticket #2328 (ngx_http_uwsgi_module removes chunked-encoding, but doesn't modify ...) updated by dener.kup@…
Maxim, thanks for the reply! To be honest, I wasn't completely sure …
00:41 Ticket #2328 (ngx_http_uwsgi_module removes chunked-encoding, but doesn't modify ...) closed by Maxim Dounin
invalid: > It looks like that ngx_http_uwsgi_module removes chunked encoding …

03/02/22:

20:02 compose_project.tar attached to Ticket #2328 by dener.kup@…
20:02 tcpdump_of_uwsgi.png attached to Ticket #2328 by dener.kup@…
20:02 Ticket #2328 (ngx_http_uwsgi_module removes chunked-encoding, but doesn't modify ...) created by dener.kup@…
It looks like that ngx_http_uwsgi_module removes chunked encoding from …
13:07 Ticket #808 (Defining http2 without ssl leads to HTTP/1.1 client failure) updated by Maxim Dounin
See also #2327.
13:06 Ticket #2327 (Adding cross-domain configuration in HTTP2 is invalid) closed by Maxim Dounin
duplicate: Using listen ... http2; without ssl configures listening socket to …
12:04 Ticket #2327 (Adding cross-domain configuration in HTTP2 is invalid) updated by yl-yue
Http2 not configured with SSL causes the add_header configuration to …

03/01/22:

13:38 Ticket #2327 (Adding cross-domain configuration in HTTP2 is invalid) updated by Maxim Dounin
> But actually, the response headers doesn't have any. Could you …
08:46 Ticket #2327 (Adding cross-domain configuration in HTTP2 is invalid) updated by yl-yue
Replying to Maxim Dounin: > Could you please clarify what …
Note: See TracTimeline for information about the timeline view.