Timeline
03/06/14:
- 19:50 Ticket #516 (HTTPS breaks on 1.4.6) closed by
- invalid
- 19:37 Ticket #516 (HTTPS breaks on 1.4.6) updated by
- Crap, how do I close this? I found the problem: One of the scripts was …
- 19:28 Ticket #516 (HTTPS breaks on 1.4.6) created by
- So, I have HTTPS deployed on a testing machine (I'm replacing the …
- 10:05 Ticket #515 (1.4.6 quietly dropped support for secp521r1 in ssl_ecdh_curve) created by
- # nginx -V nginx version: nginx/1.4.6 built by gcc 4.4.7 20120313 (Red …
03/05/14:
- 10:43 Ticket #514 (worker process caused 100% CPU usage on one core on win32) created by
- Timing issue scenario: source code file (tip level): …
03/04/14:
- 15:25 Ticket #503 (Nginx worker process crash when the upstream reject the nginx connection.) updated by
- In c8a14fbd3ce9f59a0157fb0d0dbe37ca382aaba6/nginx: […]
- 10:03 Milestone 1.4.6 completed
- Status: released [[http://nginx.org/en/CHANGES-1.4 | 1.4.6 …
- 09:55 Milestone 1.5.11 completed
- Status: released [[http://nginx.org/en/CHANGES | 1.5.11 …
02/27/14:
- 14:32 Ticket #513 (Implementation of UDT support) created by
- Since the …
- 00:49 Ticket #235 (segfault with SNI and ssl_session_cache assymetrical configuration) updated by
- A colleague of mine and I have looked at this issue to help fix this …
02/25/14:
- 21:05 Ticket #512 (Passing invalid headers allow to corrupt/forge messages in error_log) created by
- "Client sent invalid header line" messages in error_log doesn't seem …
- 04:13 Ticket #428 (SPDY and Proxy Cache prematurely closes connections) updated by
- This bug makes me 3 days to investigate and search for solution to use …
02/22/14:
- 04:34 Ticket #511 (Shared Memory Add Segfaults on Small Sizes) updated by
-
120 is the size of
ngx_slab_pool_twhich is located at the top of … - 01:45 Ticket #511 (Shared Memory Add Segfaults on Small Sizes) created by
- If I call ngx_shared_memory_add() from within a module directive's …
02/20/14:
- 09:19 Ticket #510 (DAV module COPY & MOVE can't handle regex destination URI) updated by
- Replying to Ruslan Ermilov: > See if regex location can …
- 07:23 Ticket #510 (DAV module COPY & MOVE can't handle regex destination URI) updated by
- DAV module uses configuration matching the request URI to map both …
- 03:00 Ticket #510 (DAV module COPY & MOVE can't handle regex destination URI) created by
- I configure NGINX to be a WebDAV server: […] I tested COPY and …
02/19/14:
- 20:54 Ticket #509 (fastcgi_split_path_info Unsetting $fastcgi_path_info with Try_Files) created by
- When using a try_files inside a location block that will be using …
- 18:28 Ticket #508 (nginx rewrite URL decoding first encoded character in URI) created by
- I have rules like the following: location /trk/ { if …
02/18/14:
- 14:37 Ticket #503 (Nginx worker process crash when the upstream reject the nginx connection.) closed by
- fixed: Fix committed, thanks.
- 14:30 Ticket #503 (Nginx worker process crash when the upstream reject the nginx connection.) updated by
- In 7586e7b2dbe9d9999014a99fe40e58c2e90b9cf5/nginx: […]
- 13:21 Ticket #507 (Mail SSL not supporting EC Ciphers) closed by
- fixed: This is already fixed by revision 32fe021911c9 in nginx 1.5.1: […] …
- 12:57 Ticket #507 (Mail SSL not supporting EC Ciphers) created by
- The mail_ssl module does not support ciphers that are using Elliptic …
02/17/14:
- 12:17 Ticket #506 (Allow http error code 101 426 returned from auth_request) closed by
- wontfix: There are no plans to support RFC2817-style upgrades to TLS. It is …
- 04:45 Ticket #215 (SSL: decryption failed or bad record mac with upstream servers) updated by
- I found a bug in OpenSSL 1.0.0+ This …
02/16/14:
- 14:39 Ticket #503 (Nginx worker process crash when the upstream reject the nginx connection.) updated by
- With patched this fix, no crash happened. and looks no side effects. …
02/15/14:
- 16:13 Ticket #506 (Allow http error code 101 426 returned from auth_request) created by
- Send username and password with http is not secure. So if the …
- 15:04 Ticket #505 (Nginx worker randomly segfault during the day) updated by
- Ok, I'll obtain a backtrace soon. I'm not using a websocket actually, …
02/14/14:
- 23:28 Ticket #503 (Nginx worker process crash when the upstream reject the nginx connection.) updated by
- Please try the following patch: […] Note that the problem existed …
- 13:09 Ticket #505 (Nginx worker randomly segfault during the day) updated by
- Please see instructions at http://wiki.nginx.org/Debugging on how to …
- 12:40 Ticket #505 (Nginx worker randomly segfault during the day) created by
- I saw this occuring since the last update : […]
- 06:43 Ticket #504 (the resourcenot release in time when file be truncated) created by
- 1,a client request a file; 2,nginx response the request use sendfile,; …
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 …
Note:
See TracTimeline
for information about the timeline view.
