Timeline
02/13/14:
- 10:22 Ticket #503 (Nginx worker process crash when the upstream reject the nginx connection.) updated by
-
Status, Owner changed
Thank you for your report, I'll take a look how to properly fix this. - 09:31 Ticket #503 (Nginx worker process crash when the upstream reject the nginx connection.) created by
- Actually, this defect is existed from v1.4.4 to v1.5.19 This defect …
02/12/14:
- 07:53 Ticket #431 (directory redirect ex: try_files $uri $uri/ @backend;) updated by
- […] вероятно решает эту проблему.
02/11/14:
- 09:53 Milestone 1.4.5 completed
- Status: released [[http://nginx.org/en/CHANGES-1.4 | 1.4.5 …
02/10/14:
- 17:14 Ticket #502 (Problems with serving content on 1.4.4) updated by
- Hi Hongli Lai. Thank you for investigation of the issue. There are a …
- 15:35 Ticket #502 (Problems with serving content on 1.4.4) updated by
- Dear Hongli Lai, thank you for the troubleshooting and sorry for the …
- 15:27 Ticket #502 (Problems with serving content on 1.4.4) updated by
- Hi Valentin. My name is Hongli Lai, CTO at Phusion and lead developer …
- 13:40 Ticket #353 (nginx 1.4.[0|1] empty reply from server) updated by
- In 462ae7eedc681205070d53bb3d46a9bc4eed9744/nginx: […]
- 09:38 Ticket #488 (proxy_next_upstream_action to distinguish different network actions) updated by
- Highly unlikely to be introduced in this form. Some better options to …
- 07:50 Ticket #488 (proxy_next_upstream_action to distinguish different network actions) updated by
- So how about the idea : add proxy_next_upstream_action directive ？
02/07/14:
- 20:41 Ticket #502 (Problems with serving content on 1.4.4) updated by
- Passenger is known for introducing strange bugs in nginx even when not …
- 19:21 Ticket #502 (Problems with serving content on 1.4.4) updated by
- Hmm are you sure because a static page that doesn't go through …
- 19:18 Ticket #502 (Problems with serving content on 1.4.4) closed by
- worksforme: From what you describe it looks like Passenger problem. If you think …
- 18:34 Ticket #502 (Problems with serving content on 1.4.4) updated by
- PS: I didn't install anything on that VPS for a long time and the only …
- 18:33 Ticket #502 (Problems with serving content on 1.4.4) created by
- Hi, after upgrading to Passenger 4.0.35 which installed Ningx 1.4.4 …
- 17:50 Ticket #501 (Incorrect Host HTTP header when using upstream element in location) closed by
- invalid: As already explained, name of a host is one written in the …
- 16:51 Ticket #501 (Incorrect Host HTTP header when using upstream element in location) updated by
- Replying to Antti Huokko <huokko@gmail.com>: > According …
- 16:28 Ticket #501 (Incorrect Host HTTP header when using upstream element in location) reopened by
- 16:28 Ticket #501 (Incorrect Host HTTP header when using upstream element in location) updated by
- Hello, I opened the issue one last time because I really want to …
- 11:06 Ticket #501 (Incorrect Host HTTP header when using upstream element in location) closed by
- invalid: You have to configure all your backend servers to recognize one single …
- 10:22 Ticket #501 (Incorrect Host HTTP header when using upstream element in location) reopened by
- 10:13 Ticket #501 (Incorrect Host HTTP header when using upstream element in location) updated by
- Hello, Thank you for the quick reply. However I still don't …
- 09:26 Ticket #501 (Incorrect Host HTTP header when using upstream element in location) closed by
- invalid: This is the expected behaviour. You specify actual name of a server …
- 06:54 Ticket #501 (Incorrect Host HTTP header when using upstream element in location) created by
- Hello, I have a simple load balancing configuration using upstream …
02/06/14:
- 23:19 Ticket #500 (nginx segfaults on Solaris 11.1 x86 when compiled with -m64) closed by
- invalid: With the parameters you've supplied, nginx will assume it's building …
- 22:46 Ticket #500 (nginx segfaults on Solaris 11.1 x86 when compiled with -m64) created by
- Hi, nginx 1.5.10 segfaults on Solaris 11.1 x86/amd64 when compiled …
- 15:38 Ticket #499 (WebSocket will not connect from iOS Safari if ssl_verify_client is set ...) updated by
- Submitted to Apple as ticket 16001290.
- 15:21 Ticket #499 (WebSocket will not connect from iOS Safari if ssl_verify_client is set ...) closed by
- invalid: This doesn't looks like nginx problem, try reporting it to Apple …
- 15:19 Ticket #498 (APIs need ability to set ssl_verify_client per Location) updated by
- Ticket 499 now covers this …
- 15:18 Ticket #499 (WebSocket will not connect from iOS Safari if ssl_verify_client is set ...) updated by
- Instead a client cert will only be used when servers interact with …
- 15:16 Ticket #499 (WebSocket will not connect from iOS Safari if ssl_verify_client is set ...) updated by
- Our constraints are also that setting up client certificates on an …
- 15:12 Ticket #499 (WebSocket will not connect from iOS Safari if ssl_verify_client is set ...) created by
- The latest iOS Safari fails to connect a WebSocket if …
- 15:09 Ticket #498 (APIs need ability to set ssl_verify_client per Location) updated by
- Is there any technical solution to our problem using nginx as the …
- 14:48 Ticket #498 (APIs need ability to set ssl_verify_client per Location) updated by
- What is the nginx's group's stance on …
- 11:17 Ticket #498 (APIs need ability to set ssl_verify_client per Location) updated by
- Technical reasons are quite simple - client certificates are requested …
02/05/14:
- 19:37 Ticket #498 (APIs need ability to set ssl_verify_client per Location) updated by
- From a business perspective, where we install a medical server on-site …
- 19:21 Ticket #498 (APIs need ability to set ssl_verify_client per Location) updated by
- ssl_verify_client optional is broken with respect to WebSockets. iOS 7 …
- 17:27 Ticket #498 (APIs need ability to set ssl_verify_client per Location) closed by
- duplicate: As already said in ticket #317, there are no plans to add per-location …
- 09:21 Ticket #428 (SPDY and Proxy Cache prematurely closes connections) updated by
- Replying to Phil Sweeney <philcollect@gmail.com>: > Do you …
- 06:50 Ticket #428 (SPDY and Proxy Cache prematurely closes connections) updated by
- Thanks for that. I have tried it against 1.5.10 and it does appear to …
02/04/14:
- 19:40 Ticket #498 (APIs need ability to set ssl_verify_client per Location) created by
- Our API and service design requires that there be a single server on a …
- 15:29 Ticket #496 (Windows upstream 60 proxy_pass timeout) updated by
- Thanks a lot Maxim!! I have tested opening the backend on ipv6 and …
- 14:11 Ticket #437 (Add Support for SPDY/3) closed by
- fixed: Support for SPDY/3.1 was committed as 39d7eef2e332 and released in …
- 13:19 Milestone 1.5.10 completed
- Status: released [[http://nginx.org/en/CHANGES | 1.5.10 …
02/03/14:
- 21:50 Ticket #497 (X-Accel-Redirect problem with proxy_pass and proxy_set_heder) closed by
- invalid: The X-Accel-Redirect header is to do an internal redirect to the …
- 20:38 Ticket #497 (X-Accel-Redirect problem with proxy_pass and proxy_set_heder) updated by
- We also tried to set full path on the backend for the X-Accel-Redirect …
- 19:43 Ticket #497 (X-Accel-Redirect problem with proxy_pass and proxy_set_heder) created by
- Will try to describe the problem we have: We are doing proxy_pass to …
- 15:43 Ticket #496 (Windows upstream 60 proxy_pass timeout) closed by
- invalid: Apparently, your backend doesn't respond on IPv6 localhost address …
- 15:24 Ticket #496 (Windows upstream 60 proxy_pass timeout) created by
- Normal usage of proxy_pass produces a delay of 60 seconds (on a second …
01/31/14:
- 21:15 Ticket #97 (try_files and alias problems) updated by
- Also not works with rewrite. I tried to make fallback with rewrite.
- 10:17 Ticket #488 (proxy_next_upstream_action to distinguish different network actions) updated by
- I second that. The "error" directive should be split at least into an …
01/30/14:
- 14:25 Ticket #428 (SPDY and Proxy Cache prematurely closes connections) updated by
- This patch should fix the problem: […] Feel free to use it.
01/29/14:
- 16:00 Ticket #377 (etag не отдается с gzip) updated by
- Would be great if we could actually do something about it, instead of …
- 14:27 Ticket #475 (http_mp4_module seeking problem: "start time is out mp4 stts samples") updated by
- Just for record: looking though debug log suggests that the problem is …
- 13:51 Ticket #475 (http_mp4_module seeking problem: "start time is out mp4 stts samples") updated by
-
Status, Owner changed
Roman, could you please take a look? - 09:40 Ticket #414 (Ошибка 500 при использовании seek для файлов с mp4s stream) updated by
- In 5730c0193842dfb6bb30ca3d2401a7b36be12b4f/nginx: […]
01/28/14:
- 19:33 Ticket #495 (error_page 497 handling resulting in 504 error doesn't use configured ...) updated by
- Ahh, thanks that works
- 18:12 Ticket #495 (error_page 497 handling resulting in 504 error doesn't use configured ...) closed by
- invalid: http://nginx.org/r/recursive_error_pages
- 17:25 Ticket #495 (error_page 497 handling resulting in 504 error doesn't use configured ...) created by
- If I try to proxy a HTTP request on the HTTPS port to an upstream with …
- 12:11 Ticket #353 (nginx 1.4.[0|1] empty reply from server) closed by
- fixed: Fix committed, thanks.
- 12:10 Ticket #230 (Values of $date_local and $date_gmt variables depend on SSI turned on/off) closed by
- fixed: Fixed.
- 12:05 Ticket #353 (nginx 1.4.[0|1] empty reply from server) updated by
- In fdb67cfc957d110ea887961cc8c08a590df5f62c/nginx: […]
- 12:05 Ticket #230 (Values of $date_local and $date_gmt variables depend on SSI turned on/off) updated by
- In 3a8e19528b3098c6dde461dadab07e8cb48f6d91/nginx: […]
01/27/14:
- 16:13 Ticket #416 (proxy_cache_use_stale run updating in new thread and serve stale data ...) updated by
- Hey Igor, sounds good. I'll make a point to be in the nginx channel …
- 15:02 Ticket #355 (Proxy protocol support) updated by
- +1 from me too. Nate, I'm not familiar enough with C and nginx to …
01/26/14:
- 01:15 Ticket #416 (proxy_cache_use_stale run updating in new thread and serve stale data ...) updated by
- Replying to Brian Davis: > I agree, this would be a very …
01/23/14:
- 21:59 Ticket #494 (nginx should not ignore log_format changes during reload) closed by
- invalid
- 21:41 Ticket #494 (nginx should not ignore log_format changes during reload) updated by
- Close the ticket. Human error.
- 21:27 Ticket #494 (nginx should not ignore log_format changes during reload) created by
- nginx should not ignore log_format changes during -HUP signal or reload.
- 16:46 Ticket #482 (supported linux packages inconsistent) closed by
- fixed: I've built packages for nginx 1.4.4 for Ubuntu 13.10 (saucy).
01/22/14:
- 13:35 Milestone 1.5.9 completed
- Status: released [[http://nginx.org/en/CHANGES-1.5 | 1.5.9 …
- 06:31 Ticket #355 (Proxy protocol support) updated by
- +1 for this feature from me as well. It would be incredibly useful for …
01/21/14:
- 17:52 Ticket #493 (nginx always sends 100-continue instead of delegating that ...) updated by
- Good to know that unbuffered upload is on your roadmap. Is there any …
- 10:48 Ticket #493 (nginx always sends 100-continue instead of delegating that ...) closed by
- wontfix: This how it works - nginx needs to read the request body before it …
01/20/14:
- 22:42 Ticket #493 (nginx always sends 100-continue instead of delegating that ...) created by
- What I did: curl -X PUT http://foo.bar/api/deadbeef -T largefile …
01/19/14:
- 22:13 Ticket #491 (performance issue on same url) updated by
- Are you able to reproduce the problem without 3rd party modules …
01/18/14:
- 16:38 Ticket #492 (location-specific charset not respected) closed by
- worksforme: I've just tested with the configuration below: […] and it seems all …
- 16:04 Ticket #492 (location-specific charset not respected) created by
- Is it intended that location /somelocation { index index.htm; …
- 04:38 Ticket #491 (performance issue on same url) created by
- i have a site with one both http and websocket location map …
01/17/14:
- 17:11 Ticket #490 (ngx_reset_pool() memory wastage) closed by
- fixed: Fix committed, thanx.
- 15:55 Ticket #490 (ngx_reset_pool() memory wastage) updated by
- In 320abeb364e697f86d080616de07ad09080aaea9/nginx: […]
- 01:37 Ticket #489 (Segfault in ngx_log_error_core under load) closed by
- invalid: The traceback clearly shows that the problem is related to …
- 00:38 Ticket #490 (ngx_reset_pool() memory wastage) created by
- ngx_reset_pool() seems to free up large buffers and sets d.last to …
- 00:26 Ticket #489 (Segfault in ngx_log_error_core under load) created by
- When running nginx under load, we can routinely trigger a segfault. …
01/16/14:
- 12:54 Ticket #487 (Connection problems after multiple reloads.) closed by
- invalid: Ok, closing this, looks like 3rd party module problem.
01/15/14:
- 18:45 Ticket #487 (Connection problems after multiple reloads.) updated by
- Stack: #0 0x000000000044b006 in ngx_http_script_flush_complex_value …
- 17:40 Ticket #486 (ngx_http_upstream module lack the check of broken peer connection ...) updated by
- The suggested change doesn't look right. The …
- 13:24 Ticket #487 (Connection problems after multiple reloads.) updated by
- Thanks, we are waiting for a core dump to get the stack trace. …
- 07:22 Ticket #488 (proxy_next_upstream_action to distinguish different network actions) created by
- add proxy_next_upstream_action The directive "proxy_next_upstream …
01/14/14:
- 18:39 Ticket #487 (Connection problems after multiple reloads.) updated by
- Are you able to reproduce the problem without 3rd party modules …
- 17:40 Ticket #487 (Connection problems after multiple reloads.) created by
- We are seeing failing inbound HTTP (non-SSL) connection attempts after …
- 11:31 Ticket #486 (ngx_http_upstream module lack the check of broken peer connection ...) created by
- HI, guys, ngx_http_upstream module use ngx_http_upstream_test_connect …
- 08:46 Ticket #485 (Multiple WWW-Authenticate headers) created by
- RFC allows a server to respond with multiple WWW-Authenticate header …
Note:
See TracTimeline
for information about the timeline view.
