Timeline
07/09/19:
- 21:16 Ticket #1806 (New Set of Map files causing server segmentation fault) updated by
- I get the same failure on Ubuntu 16.4 servers as well. this was …
- 20:50 Ticket #1806 (New Set of Map files causing server segmentation fault) updated by
- Here is the log from 1.17 version 2019/07/09 15:46:33 [notice] …
- 20:36 Ticket #1806 (New Set of Map files causing server segmentation fault) updated by
- nginx version: nginx/1.17.0 (Ubuntu) built by gcc 7.4.0 (Ubuntu …
- 20:35 Ticket #1806 (New Set of Map files causing server segmentation fault) updated by
- Same problem on 1.17.0
- 17:32 Ticket #1806 (New Set of Map files causing server segmentation fault) updated by
- I have recently been playing with adding larger values for a number of …
- 17:29 Ticket #1806 (New Set of Map files causing server segmentation fault) created by
- I have some 40 NGINX servers running, working just fine. I am trying …
- 13:46 Ticket #1805 (Cannot reopen log files without restarting nginx) closed by
- invalid
- 13:42 Ticket #1792 (grpc module handles RST_STREAM(NO_ERROR) improperly on closed streams) updated by
- From HTTP/2 specification point of view, RST_STREAM(NO_ERROR) is a …
- 13:35 Ticket #1805 (Cannot reopen log files without restarting nginx) updated by
- Thank you for your help. The problem was caused by insufficient …
07/08/19:
- 15:41 Ticket #1805 (Cannot reopen log files without restarting nginx) updated by
- Reopening log files may fail if new log files cannot be opened for …
- 13:46 Ticket #1805 (Cannot reopen log files without restarting nginx) created by
- Reopening log files after log rotation silently fails. There is no …
- 13:07 Ticket #1792 (grpc module handles RST_STREAM(NO_ERROR) improperly on closed streams) updated by
- Replying to oleg.dropbox.com@…: > It looks like there is …
07/06/19:
- 17:53 Ticket #1804 (proxy_pass/proxy_redirect doesn't work if port 80 is explicitly specified) closed by
-
invalid: The
proxy_redirectdirective does prefix comparison on what is … - 17:42 Ticket #1803 (set_decode_base64 not working for combination of Japnese and ...) closed by
- invalid: The set-misc-module is a 3rd party module. You may want to contact its …
07/05/19:
- 13:30 Ticket #1804 (proxy_pass/proxy_redirect doesn't work if port 80 is explicitly specified) created by
- When you have a configuration like: […] the Location header for …
07/04/19:
- 16:06 Ticket #1803 (set_decode_base64 not working for combination of Japnese and ...) created by
- When "5Yy755mC57Wx6KiIX+Wbszg=" is given as Input to set_decode_base64 …
07/03/19:
- 00:44 Ticket #1520 (HTTP/2 connection dropped when URL has large numbers of same parameter) updated by
- See also #1802.
- 00:43 Ticket #1802 (Bad response for request with large cookie via http2) closed by
- duplicate: Duplicate of #1520.
07/02/19:
- 10:51 Ticket #1801 (Stale cache is not updated after some time) closed by
- invalid: Close per submitter request.
- 09:52 Ticket #1801 (Stale cache is not updated after some time) updated by
- Please close this ticket. It is not a bug, just my misunderstanding of …
07/01/19:
- 14:39 Ticket #1802 (Bad response for request with large cookie via http2) created by
- При включении http2 в конфигурации сервера и отправки куки превышающий …
- 09:08 Ticket #1801 (Stale cache is not updated after some time) created by
- I configured a reverse caching proxy which makes use of …
06/29/19:
- 13:52 Ticket #1794 (Difference Between Upstream Response Time And Nginx Response Time) closed by
- invalid: The $request_time variable measures …
- 11:00 Ticket #1508 (When browser access nginx http/2 server with large cookies, nginx ...) closed by
- duplicate: Closing this as a duplicate of #1520 (which was selected mostly …
- 10:56 Ticket #1520 (HTTP/2 connection dropped when URL has large numbers of same parameter) updated by
- See also #1508.
- 10:48 Ticket #1520 (HTTP/2 connection dropped when URL has large numbers of same parameter) updated by
- See also #1800.
- 10:48 Ticket #1800 (nginx close http2 connection if request too large) closed by
- duplicate: Duplicate of #1520.
- 10:01 Ticket #1799 (client_max_body_size ignored except at the bottom of http context) updated by
- Please provide full configuration which demonstrates the problem, as …
- 09:57 Ticket #1798 (Gateway timeout error when JSON Payload size > 1400 bytes and MTU size 9000) closed by
- invalid: This doesn't look like a bug in nginx, but rather like a network issue.
06/27/19:
- 14:46 Ticket #1800 (nginx close http2 connection if request too large) created by
- nginx close http2 connection if request too large see the max simple …
- 08:51 Ticket #1794 (Difference Between Upstream Response Time And Nginx Response Time) updated by
- Replying to mdounin: > There is no "nginxResponsetime" in …
06/26/19:
- 19:22 Ticket #1792 (grpc module handles RST_STREAM(NO_ERROR) improperly on closed streams) updated by
- It looks like there is another similar issue with RST_STREAM(NO_ERROR) …
- 13:52 Ticket #1797 (grpc module handles WINDOW_UPDATE improperly on closed streams) updated by
- Yep, I considered this addition when cooking patch for ticket #1792. …
- 13:15 Ticket #1799 (client_max_body_size ignored except at the bottom of http context) created by
- When attempting to PUT a resource of about 40MB to an nginx endpoint, …
- 04:48 Ticket #1798 (Gateway timeout error when JSON Payload size > 1400 bytes and MTU size 9000) created by
- ifconfig eth0 Link encap:Ethernet HWaddr 00:50:56:01:0A:66 …
- 01:05 Ticket #1797 (grpc module handles WINDOW_UPDATE improperly on closed streams) created by
- Current implementation fails the request on receiving WINDOW_UPDATE …
06/25/19:
- 19:48 Milestone njs-0.3.3 completed
- Planned features: * Objects setter and getter properties * "process" …
- 19:48 Milestone nginx-1.17.1 completed
- Status: scheduled Trunk: mainline * limit_req dry run feature
06/24/19:
06/21/19:
- 12:01 Ticket #1794 (Difference Between Upstream Response Time And Nginx Response Time) updated by
- There is no "nginxResponsetime" in the log pattern provided. Do you …
- 07:54 Ticket #1794 (Difference Between Upstream Response Time And Nginx Response Time) updated by
- Replying to mdounin: > Please define "nginx response time" …
06/19/19:
- 19:35 Ticket #1795 (Nginx proxy serving non-existent proxy cache files) closed by
- invalid: This sounds like a problem in your setup and/or your cache …
- 19:27 Ticket #1795 (Nginx proxy serving non-existent proxy cache files) created by
- Hello. I make custom program for reverse proxy cache invalidation. And …
- 12:12 Ticket #1794 (Difference Between Upstream Response Time And Nginx Response Time) updated by
- Please define "nginx response time" - how do you measure it? What are …
06/18/19:
- 13:13 Ticket #1794 (Difference Between Upstream Response Time And Nginx Response Time) created by
- HI Folks, From past few months we are facing issue in nginx , wherein …
06/17/19:
- 19:26 Ticket #1786 (Send file from Perl module) closed by
- fixed: Fix committed.
- 18:40 Ticket #1786 (Send file from Perl module) updated by
- In [changeset:"36c52a0f6ded3e9755f0f32273abebc9eec916c9/nginx" …
06/13/19:
- 06:43 Ticket #1793 (auth_request does not expand variables) closed by
-
invalid: Variables are not supported by the
auth_requestdirective. Note that …
06/12/19:
- 16:13 Ticket #1793 (auth_request does not expand variables) created by
- This example configuration doesn't work as desired - backend receives …
06/11/19:
- 18:59 Ticket #1792 (grpc module handles RST_STREAM(NO_ERROR) improperly on closed streams) updated by
- Yes, that patch appears to fix my issue. Thank you!
- 14:57 Ticket #1792 (grpc module handles RST_STREAM(NO_ERROR) improperly on closed streams) updated by
-
Status changed
Could you please try this patch. […] - 08:29 Ticket #1792 (grpc module handles RST_STREAM(NO_ERROR) improperly on closed streams) created by
- Per the code, we have: […] saying that if we ever receive any …
Note:
See TracTimeline
for information about the timeline view.
