Timeline
04/05/22:
- 22:18 Ticket #2341 (Sporadic "502 Bad Gateway" with reverse proxy) updated by
- > I'm wondering why I never got 502 responses when using the upstream …
- 07:52 Ticket #2341 (Sporadic "502 Bad Gateway" with reverse proxy) updated by
- Many thanks for your quick reply! I think I've got your explanations. …
04/04/22:
- 18:58 Ticket #2341 (Sporadic "502 Bad Gateway" with reverse proxy) closed by
- invalid: The log clearly says the reason for 502: […] That is, your …
- 17:34 Changeset in nginx_org [2838:2a4bd6782451] by
- Updated with Netcraft March 2022 Web Server Survey stats.
- 15:11 Ticket #2341 (Sporadic "502 Bad Gateway" with reverse proxy) updated by
- I have also played with different proxy and other settings (cache, …
- 15:06 Ticket #2341 (Sporadic "502 Bad Gateway" with reverse proxy) updated by
-
Description changed
- 15:04 Ticket #2341 (Sporadic "502 Bad Gateway" with reverse proxy) updated by
- The nginx.conf configuration is this (although I've tried the default …
- 15:01 Ticket #2341 (Sporadic "502 Bad Gateway" with reverse proxy) created by
- For unknown reasons I've got 502 responses. AFAIK there was no change …
04/01/22:
- 19:06 Ticket #191 (literal newlines logged in error log) updated by
- With %22 and %OA, this could be used to forge error messages in the …
- 13:24 Ticket #2340 (decoded percent-encoded values written to logfiles) closed by
- duplicate: Duplicate of #191.
- 13:24 Ticket #191 (literal newlines logged in error log) updated by
- See also #2340.
- 00:55 Ticket #2340 (decoded percent-encoded values written to logfiles) created by
- Saw that bad requests that percent-encode nonprintable characters are …
03/28/22:
- 11:38 Ticket #2339 (nginx fails to process "allow" statements on subsequent keepalive requests) updated by
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
-
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
- 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
- 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
- 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
-
As soon as there are any variables in the
proxy_passparameter, … - 22:16 Ticket #2334 (regex capture with $1 not work in 1.20.0 but in 1.19.10) closed by
- 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
- Not sure I understand your certificate configuration. From the …
- 10:31 Ticket #2335 (no resolver defined to resolve localhost) updated by
- 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
- 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
- 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
-
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
-
invalid: The
no resolver defined to resolve ...error means that per the … - 12:32 Ticket #2335 (no resolver defined to resolve localhost) updated by
-
Description changed
- 12:24 Ticket #2335 (no resolver defined to resolve localhost) created by
- 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
-
Description changed
- 03:18 Ticket #2334 (regex capture with $1 not work in 1.20.0 but in 1.19.10) updated by
-
Description changed
- 03:13 Ticket #2334 (regex capture with $1 not work in 1.20.0 but in 1.19.10) created by
- 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
- 3.2. Starting HTTP/2 for "http" URIs …
- 21:37 Ticket #2333 (Cache-Control header spills over to different location) closed by
-
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
- 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
- Thanks for the details. In this particular case Django's syntax …
- 11:54 Ticket #2332 (Include $request_id in error.log messages) created by
- 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
- 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
- Oops, this is embarrassing... Thank you for correcting my …
Note:
See TracTimeline
for information about the timeline view.
