Timeline



08/10/12:

21:43 Ticket #192 (504 Gateway Time-out for proxyed site after Server IP change) updated by Gambino ZaDarkSide
Setting config to […] doesn't resolve this issue, any other advice ?
19:54 Ticket #159 (Implement fcgi_buffering option) updated by Artyom Beilis
I'm second to vote about this ticket. Please note, without this …
18:07 Ticket #194 (mp4 streaming module breaks embedded text data) updated by Martin Fjordvald
Original reporter here. I have updated my bug example and I can …
16:50 Ticket #160 (Nginx -V Output Format) reopened by Nginxuser
Hello! Both worlds of readability and allowing for copy pasting can …
10:57 Ticket #194 (mp4 streaming module breaks embedded text data) updated by Maxim Dounin
Status changed
Thank you for report. As of now nginx's mp4 module only allows tracks …
10:47 Ticket #160 (Nginx -V Output Format) closed by Maxim Dounin
wontfix: There is actually a major difference: current format is usable for …
09:12 Ticket #194 (mp4 streaming module breaks embedded text data) created by Dan Rossi
The mp4 streaming module is breaking onTextData stream events from …
08:56 Ticket #193 (nginx bug) closed by Maxim Dounin
invalid: Message more or less clearly says that nginx complained about …
05:24 Ticket #193 (nginx bug) created by Feng Sheng
/usr/local/services/nginx-1.2.3/sbin/nginx -t nginx: [emerg] duplicate …

08/08/12:

22:02 Ticket #191 (literal newlines logged in error log) updated by Paul Henson
Wow, a CVE from 2009 :). I'm really more concerned about log …
20:54 Ticket #192 (504 Gateway Time-out for proxyed site after Server IP change) closed by Maxim Dounin
invalid: This is expected behaviour, as nginx resolves hostnames in …
19:42 Ticket #192 (504 Gateway Time-out for proxyed site after Server IP change) updated by Gambino ZaDarkSide
My internet connection is via PPPOE, don't know if it's important or …
19:33 Ticket #192 (504 Gateway Time-out for proxyed site after Server IP change) created by Gambino ZaDarkSide
I have this config: […] If Server IP changes while nginx is running …
18:27 Ticket #191 (literal newlines logged in error log) updated by Maxim Dounin
Status changed
From security point of view we don't consider this to be a problem …
17:45 Ticket #191 (literal newlines logged in error log) updated by Paul Henson
Similar issues in other software packages have been considered …

08/07/12:

15:39 Milestone 1.2.3 completed
Status: released [[http://nginx.org/en/CHANGES-1.2 | 1.2.3 …

08/06/12:

16:04 Ticket #187 (incorrect handling of bind option on wildcard listen addresses) updated by Maxim Dounin
In 4793/nginx: […]
15:20 Ticket #184 (Unspecified behavior when going through multiple named locations) updated by Maxim Dounin
In 4788/nginx: […]
14:04 Ticket #182 (map with hostnames does not drop terminating dot) updated by Maxim Dounin
In 4786/nginx: […]

08/01/12:

18:06 Ticket #191 (literal newlines logged in error log) created by Paul Henson
I noticed that when a %0a exists in the URL, nginx includes a literal …
12:57 Ticket #190 (Error 337 (net::ERR_SPDY_PROTOCOL_ERROR) (spdy-48 and nginx 1.3.3)) closed by Valentin V. Bartenev
fixed
12:43 Ticket #190 (Error 337 (net::ERR_SPDY_PROTOCOL_ERROR) (spdy-48 and nginx 1.3.3)) updated by Lowshadow .
I can confirm that patch fixes this bug on Nginx 1.3.4. Best regards.
11:11 Ticket #190 (Error 337 (net::ERR_SPDY_PROTOCOL_ERROR) (spdy-48 and nginx 1.3.3)) updated by Valentin V. Bartenev
Status, Owner changed
Thanks for reporting the bug. Please try the new patch: …

07/31/12:

18:00 Milestone 1.3.4 completed
Status: scheduled Trunk: development * …
17:57 spdy_chrome_debug_log.txt attached to Ticket #190 by Lowshadow .
debug of a spdy session using chrome://net-internals/#spdy
17:55 Ticket #190 (Error 337 (net::ERR_SPDY_PROTOCOL_ERROR) (spdy-48 and nginx 1.3.3)) created by Lowshadow .
== Short description == Nginx 1.3.3 patched with latest SPDY patch …

07/27/12:

21:07 Ticket #189 (timeouts break when time changes) updated by Kristof Provost
Thanks, I missed that one. The additional syscall may be an issue on …
20:58 Ticket #189 (timeouts break when time changes) updated by Maxim Dounin
Take a look at ngx_time_update() in src/core/ngx_times.c. The …
17:05 Ticket #189 (timeouts break when time changes) updated by Kristof Provost
I checked the uses of ngx_gettimeofday() in ngix 1.0.5 (core). …
15:30 Ticket #189 (timeouts break when time changes) updated by Maxim Dounin
While clock_gettime(CLOCK_MONOTINIC) is certainly better choice for …
14:20 nginx-gettimeofday.patch attached to Ticket #189 by Kristof Provost
14:19 Ticket #189 (timeouts break when time changes) created by Kristof Provost
nginx uses gettimeofday() to obtain the current time for use with …

07/17/12:

17:13 Ticket #188 (client_body_in_file_only clean remove files before php can read them) updated by Krzysztof Warzecha
This was indeed configuration issue, fastcgi_ignore_client_abort fixed …
15:16 Ticket #188 (client_body_in_file_only clean remove files before php can read them) closed by Maxim Dounin
invalid: According to strace provided unlink() happens after request processing …
12:51 strace-log-1 attached to Ticket #188 by Krzysztof Warzecha
12:50 Ticket #188 (client_body_in_file_only clean remove files before php can read them) created by Krzysztof Warzecha
Hello, If i use "client_body_in_file_only clean;" upload will …
04:47 Ticket #187 (incorrect handling of bind option on wildcard listen addresses) closed by Ruslan Ermilov
fixed: In 4756/nginx: […]

07/13/12:

13:13 Ticket #187 (incorrect handling of bind option on wildcard listen addresses) updated by Roman Odaisky
This makes the comparator fail the strict antisymmetry property …
11:51 Ticket #187 (incorrect handling of bind option on wildcard listen addresses) updated by Maxim Dounin
Priority, Status, Summary changed
11:45 Ticket #187 (incorrect handling of bind option on wildcard listen addresses) updated by Maxim Dounin
Ok, thanks, the problem is clear. It's in fact due to bind option (in …

07/12/12:

15:26 Ticket #187 (incorrect handling of bind option on wildcard listen addresses) updated by Roman Odaisky
Most definitely. I encountered this in an actual setup. Minimal …
13:32 Ticket #187 (incorrect handling of bind option on wildcard listen addresses) updated by Ruslan Ermilov
I can't reproduce this. Is this actually exploitable? ngx_sort() does …

07/11/12:

23:14 Ticket #187 (incorrect handling of bind option on wildcard listen addresses) created by Roman Odaisky
Given the configuration listen 10.2.2.2:80; ... listen …
20:59 Ticket #186 (listen directive should use AAAA record) created by Roman Odaisky
Given the directive: listen f.q.d.n; where f.q.d.n has an AAAA …
Note: See TracTimeline for information about the timeline view.