Context Navigation

Timeline

12:01 Ticket #2335 (no resolver defined to resolve localhost) updated by nara3m: I agree with Stefan's comment. Error log message is misleading. I …

12:01 Changeset in nginx [9017:c2f5d79cde64]quic by Roman Arutyunyan <arut@…>: QUIC: separate UDP framework for QUIC. Previously, QUIC used the …

19:53 Ticket #2343 (net::ERR_CONTENT_LENGTH_MISMATCH) updated by Maxim Dounin: The size as logged in the access log corresponds to the amount of …
17:05 Milestone njs-0.7.3 completed: Planned features and enhancements: * Better njs modules loading …
14:16 Ticket #2343 (net::ERR_CONTENT_LENGTH_MISMATCH) created by krsvital@…: this error apears every fourth time 84.22.140.8 - - …

21:44 Changeset in nginx_org [2839:eeac73766df4] by Yaroslav Zhuravlev <yar@…>: njs-0.7.3.

18:51 Ticket #2342 (Setting a very high max-age value for Cache-Control causes int overflow) closed by Maxim Dounin: invalid: The maximum supported expiration time is limited by the size of …

20:41 Ticket #2342 (Setting a very high max-age value for Cache-Control causes int overflow) updated by hyphenized@…: My bad, this is the result for nginx -V […]
20:38 Ticket #2342 (Setting a very high max-age value for Cache-Control causes int overflow) created by hyphenized@…: When proxying to a ruby on rails application, it is possible to …

22:18 Ticket #2341 (Sporadic "502 Bad Gateway" with reverse proxy) updated by Maxim Dounin: > 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 robsch@…: Many thanks for your quick reply! I think I've got your explanations. …

18:58 Ticket #2341 (Sporadic "502 Bad Gateway" with reverse proxy) closed by Maxim Dounin: invalid: The log clearly says the reason for 502: […] That is, your …
17:34 Changeset in nginx_org [2838:2a4bd6782451] by Yaroslav Zhuravlev <yar@…>: Updated with Netcraft March 2022 Web Server Survey stats.
15:11 Ticket #2341 (Sporadic "502 Bad Gateway" with reverse proxy) updated by robsch@…: I have also played with different proxy and other settings (cache, …
15:06 Ticket #2341 (Sporadic "502 Bad Gateway" with reverse proxy) updated by robsch@…: Description changed
15:04 Ticket #2341 (Sporadic "502 Bad Gateway" with reverse proxy) updated by robsch@…: The nginx.conf configuration is this (although I've tried the default …
15:02 test-reverse-proxy.log attached to Ticket #2341 by robsch@…: debug log
15:01 Ticket #2341 (Sporadic "502 Bad Gateway" with reverse proxy) created by robsch@…: For unknown reasons I've got 502 responses. AFAIK there was no change …

19:06 Ticket #191 (literal newlines logged in error log) updated by mozai@…: 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 Maxim Dounin: duplicate: Duplicate of #191.
13:24 Ticket #191 (literal newlines logged in error log) updated by Maxim Dounin: See also #2340.
00:55 Ticket #2340 (decoded percent-encoded values written to logfiles) created by mozai@…: Saw that bad requests that percent-encode nonprintable characters are …

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 …

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

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 …

Note: See TracTimeline for information about the timeline view.