Timeline
02/22/14:
- 08:08 Changeset in nginx [5583:f47c844acbd4] by
- Core: allocate enough memory to hold IPv6 text address plus port.
- 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:
- 17:40 Changeset in nginx-tests [375:5fdde9f755c9] by
- Tests: a couple of auxiliary environment variables introduced.
- 13:27 Changeset in nginx [5582:545a4d393e2f] by
- Resolver: properly handle connect() failures. If initial attempt to …
- 09:48 Changeset in nginx [5581:4dee5ad51e9e] by
- Upstream: fixed error message wording.
- 09:20 Changeset in nginx-tests [374:ac804fd1eb56] by
- Tests: basic SPDY tests.
- 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 …
- 17:45 Changeset in nginx [5580:06c227e9edd0] by
- Access: supplemented the obfuscated code with a comment.
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:30 Changeset in nginx [5594:c8a14fbd3ce9]stable-1.4 by
- Upstream: ngx_post_event() instead of upgraded call (ticket #503). If …
- 13:30 Changeset in nginx [5579:7586e7b2dbe9] by
- Upstream: ngx_post_event() instead of upgraded call (ticket #503). If …
- 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, …
- 11:12 Changeset in nginx [9318:7fb8724bc97d] by
- Upstream: re-resolvable servers. Specifying the upstream server by a …
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 : […]
- 11:14 Changeset in nginx [5578:e280ece17020] by
- Mp4: remove useless leading stsc entry in result mp4. The fix removes …
- 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:
- 12:54 Changeset in nginx [5577:bfe536716dbf] by
- Win32: MSVC 2013 compatibility. Warnings about GetVersionEx() …
- 11:21 Changeset in nginx-tests [373:1e6e216b06c2] by
- Tests: range filter tests with charset.
- 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:
- 17:02 Changeset in nginx [5576:2bc609a4b516] by
- SPDY: fixed reversed priority order in window waiting queue.
- 15:54 Changeset in nginx-tests [372:1d6abf0db011] by
- Tests: whitespace fix.
- 15:15 Changeset in nginx-tests [371:6fb6fea36560] by
- Tests: proxy cache and range filter tests.
- 09:02 Changeset in nginx-tests [370:74cfe56c7b83] by
- Tests: simple https tests. Includes tests for $ssl_session_reused and …
- 07:53 Ticket #431 (directory redirect ex: try_files $uri $uri/ @backend;) updated by
- […] вероятно решает эту проблему.
- 05:54 Changeset in nginx [5575:d15822784cf9] by
- Upstream: fix $upstream_status variable. Previously, upstream's …
02/11/14:
- 15:20 Changeset in nginx [5573:7c05f6590753] by
- SSL: the $ssl_session_reused variable.
- 13:24 Changeset in nginx [5572:bbf43d63af4e]stable-1.4 by
- release-1.4.5 tag
- 13:24 Changeset in nginx [5571:844b2af1d65c]stable-1.4release-1.4.5 by
- nginx-1.4.5-RELEASE
- 12:54 Changeset in nginx [5574:cff36d2d7fe6] by
- SPDY: fixed parsing of http version. There is an error while parsing …
- 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 …
- 14:51 Changeset in nginx [5556:4006bf77943b] by
- Version bump.
- 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 …
- 13:13 Changeset in nginx [5558:eeb3c2719147] by
- Range filter: fixed duplicate charset. If a proxied response had …
- 12:26 Changeset in nginx [5555:3abb7076b3ec] by
- release-1.5.10 tag
- 12:26 Changeset in nginx [5554:b798fc020e3a]release-1.5.10 by
- nginx-1.5.10-RELEASE
- 05:06 Changeset in nginx [5553:60c4179f76ad] by
- SPDY: fixed parsing of the priority field. The size of the priority …
- 03:45 Changeset in nginx [5552:02ec169f683f] by
- Updated PCRE used for win32 builds.
- 00:59 Changeset in nginx [5551:a602e1006579] by
- Core: added ngx_encode_base64url().
02/03/14:
- 22:17 Changeset in nginx [5557:188481078faf] by
- Use ngx_socket_errno where appropriate. Signed-off-by: Piotr Sikora …
- 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.
- 15:17 Changeset in nginx [5549:39d7eef2e332] by
- SPDY: protocol implementation switched to spdy/3.1.
- 10:18 Changeset in nginx [5548:4d47722d76b2] by
- Fixed false compiler warning. Newer gcc versions (4.7+) report …
- 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:
- 22:58 Changeset in nginx [5550:3c5ddf0575d8] by
- Core: handle getsockopt(TCP_FASTOPEN) failures. Linux returns …
- 15:13 Changeset in nginx [5547:2e40188f83ef] by
- Fixed a compile warning introduced by 01e2a5bcdd8f. On systems with …
- 14:57 Changeset in nginx [5546:f385349d584b] by
- Proxy: fixed upstream search by proxy_pass with variables. If …
- 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:44 Changeset in nginx [5544:2f586f1684fa] by
- Mp4: fix seeks to standalone last chunk. If seek position is within …
- 09:40 Ticket #414 (Ошибка 500 при использовании seek для файлов с mp4s stream) updated by
- In 5730c0193842dfb6bb30ca3d2401a7b36be12b4f/nginx: […]
- 09:33 Changeset in nginx [5543:5730c0193842] by
- Mp4: skip tracks shorter than seek position (ticket #414). Mp4 module …
- 09:30 Changeset in nginx [5542:847c308917af] by
- Mp4: fix seeks after the last key frame. Mp4 module does not allow …
01/28/14:
- 23:33 Changeset in nginx [5545:01e2a5bcdd8f] by
- SSL: support ALPN (IETF's successor to NPN). Signed-off-by: Piotr …
- 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:18 Changeset in nginx-tests [369:4ac3588485f5] by
- Tests: added tests for embedded ssi variable.
- 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: […]
- 11:40 Changeset in nginx [5541:fdb67cfc957d] by
- Fixed TCP_DEFER_ACCEPT handling (ticket #353). Backed out …
- 11:40 Changeset in nginx [5540:3a8e19528b30] by
- SSI: fixed $date_local and $date_gmt without SSI (ticket #230). If …
01/27/14:
- 20:31 Changeset in nginx [5539:c86dd32573c0] by
- Configure: enabled -Werror for clang. Modern clang versions seem to …
- 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 …
Note:
See TracTimeline
for information about the timeline view.
