Timeline
12/12/14:
- 18:25 Ticket #75 (Thousand separators in autoindex pages) closed by
- wontfix: There are no plans to enhance HTML representation of autoindex. …
- 18:12 Ticket #9 (autoindex_max_name_len directive) closed by
- wontfix: There are no plans to enhance HTML representation of autoindex. …
12/11/14:
- 20:56 Ticket #113 (Add apache ExpiresByType equivalent functionality) closed by
-
fixed: The
expiresdirective now supports variables, and this allows to do … - 20:45 Ticket #113 (Add apache ExpiresByType equivalent functionality) updated by
- In 4983f7d18fe36859a700cee06b162ae12aff5fa0/nginx: […]
- 14:59 Ticket #683 (proxy_store) updated by
- Сохраняются только ответы с кодом 200. Научить proxy_store …
- 14:26 Ticket #683 (proxy_store) created by
- Здравствуйте. Если включить proxy_store и сделать обычный запрос на …
12/09/14:
- 16:49 Ticket #645 (proxy_pass does not work as expected in if context) closed by
- fixed: Fix committed, thanks.
- 15:55 Ticket #86 (the "if" directive have problems in location context) updated by
- In aeea0522332f4007b30683ad2a8c77a9a4bd2371/nginx: […]
- 15:55 Ticket #645 (proxy_pass does not work as expected in if context) updated by
- In 5b9f711dc819466a023c2f7e849569987474e8d7/nginx: […]
- 15:35 Ticket #537 (TE hop header not stripped when proxying) closed by
- fixed: Fix committed.
- 15:25 Ticket #537 (TE hop header not stripped when proxying) updated by
- In 2d39085161018ca7d7608589737d8d8a9a20c74d/nginx: […]
- 13:19 Ticket #682 (fastcgi problem under 42 CPU cores) closed by
- invalid: Your upstream server is overloaded, not a bug in nginx.
- 11:56 Ticket #650 (proxy_protocol in virtual hosts) updated by
- @Andrei, sure, will share the error log and configuration. No, port …
- 11:50 Ticket #650 (proxy_protocol in virtual hosts) updated by
- I tried with a number of virtual hosts defined with valid server names …
- 10:41 Ticket #682 (fastcgi problem under 42 CPU cores) created by
- Yesterday we used 42 CPU cores on our server. We had a lot of traffic …
- 06:48 Ticket #650 (proxy_protocol in virtual hosts) updated by
- @arut, @Andrei - Have you guys tried with configuration that involves …
12/08/14:
- 14:24 Ticket #681 (Pass custom Host in upstream module) updated by
- Exact configuration depends on your needs. E.g., you can select a …
- 14:03 Ticket #681 (Pass custom Host in upstream module) updated by
- I understand the logic. However, I would guess, that there is place …
- 13:53 Ticket #650 (proxy_protocol in virtual hosts) updated by
- We've just checked with a similar configuration using live ELB with …
- 13:49 Ticket #650 (proxy_protocol in virtual hosts) updated by
- I tried nginx+aws/elb, but it's still fine. Could you provide error …
- 13:40 Ticket #681 (Pass custom Host in upstream module) closed by
- wontfix: In nginx, request to upstream is created only once, and then used …
- 13:34 Ticket #681 (Pass custom Host in upstream module) created by
- Currently, proxy_pass via upstream sends $host resolved in server_name …
- 13:15 Ticket #680 (bug in ngx_http_upstream_process_body_in_memory) closed by
- invalid: As previously said, another call to recv() is needed to detect …
- 12:28 Ticket #650 (proxy_protocol in virtual hosts) updated by
- I tested it several times with nginx + AWS ELB - got this issue. …
- 12:24 Ticket #650 (proxy_protocol in virtual hosts) updated by
- No, I tested it manually. Does this issue occur only behind AWS ELB?
- 12:17 Ticket #650 (proxy_protocol in virtual hosts) updated by
- @arut, did you check the configuration with proxy_protocol enabled on …
- 11:30 Ticket #650 (proxy_protocol in virtual hosts) updated by
- Could you provide more details or even a simple small config for the …
- 08:38 Ticket #680 (bug in ngx_http_upstream_process_body_in_memory) reopened by
- Thanks for your reply. In order to try to prove my point, I …
- 02:36 Ticket #631 (server_names_hash_bucket_size seems too low by default) closed by
- wontfix: The name you are trying to use is likely larger than what fits into 32 …
- 01:36 Ticket #651 (Service 'stop' signal: replace TERM with QUIT) closed by
- wontfix: If you are going to stop nginx, it usually means that you aren't doing …
- 01:15 Ticket #661 (when more has increased the demand) closed by
- invalid: Spam.
- 01:12 Ticket #646 (can not compile nginx-1.7.6(with epoll supported) with uclibc) closed by
- worksforme: Feedback timeout. The problem is believed to be due to 3rd party …
- 00:58 Ticket #680 (bug in ngx_http_upstream_process_body_in_memory) closed by
- invalid: The upstream module is designed to work with various protocols and …
- 00:29 Ticket #679 (Nginx Memcached Sasl support) closed by
- wontfix: There are no plans to add support for this, as well as there are no …
12/07/14:
- 16:36 Ticket #680 (bug in ngx_http_upstream_process_body_in_memory) created by
- I believe that in ngx_http_upstream_process_body_in_memory the for …
12/05/14:
- 22:30 Ticket #679 (Nginx Memcached Sasl support) created by
- the ngx_http_memcached_module currently does not have functionality to …
- 18:00 Ticket #655 (access_log fails to create log file when path contains variables) closed by
- invalid: Variables can be used in access_log in any place, including path. But …
- 17:50 Ticket #659 (Incomplete dependencies on NGINX RPM for CentOS7) closed by
- invalid
- 12:50 Ticket #678 (Image_filter don't turn the interlace bit on without resize.) closed by
- wontfix: That's expected behaviour. Image filter does …
- 09:39 Ticket #678 (Image_filter don't turn the interlace bit on without resize.) created by
- I need just make my images interlaced (progressive jpeg), not resize …
12/04/14:
- 09:44 Ticket #677 (FQDN treated as syslog tag by rsyslog) closed by
- invalid: nginx uses message format described in RFC 3164 which includes …
- 00:59 Ticket #677 (FQDN treated as syslog tag by rsyslog) updated by
- This is also reported to rsyslog by sindarina here: …
- 00:53 Ticket #677 (FQDN treated as syslog tag by rsyslog) created by
- not sure if this is a nginx issue or rsyslog issue. For messages sent …
12/03/14:
- 11:55 Ticket #675 (spdy after a single connect send data big than 65535 , last frame size ...) closed by
- invalid: Replying to bin tom <tom8888889@gmail.com>: > .. > The …
- 08:06 Ticket #675 (spdy after a single connect send data big than 65535 , last frame size ...) updated by
- Replying to Valentin V. Bartenev: > It's limited by the …
- 05:50 Ticket #675 (spdy after a single connect send data big than 65535 , last frame size ...) updated by
- 05:26 Ticket #675 (spdy after a single connect send data big than 65535 , last frame size ...) updated by
- 04:02 Ticket #675 (spdy after a single connect send data big than 65535 , last frame size ...) updated by
- 03:49 Ticket #675 (spdy after a single connect send data big than 65535 , last frame size ...) updated by
- 03:43 Ticket #675 (spdy after a single connect send data big than 65535 , last frame size ...) reopened by
12/02/14:
- 14:10 Milestone 1.7.8 completed
- Status: released [[http://nginx.org/en/CHANGES | 1.7.8 …
- 13:24 Ticket #675 (spdy after a single connect send data big than 65535 , last frame size ...) closed by
- invalid: It's limited by the SPDY flow control mechanism. From your debug log …
- 12:55 Ticket #676 (Different ssl_protocols per server won`t work) closed by
- wontfix: This is per OpenSSL behaviour, and there isn't much nginx can do to …
- 11:43 Ticket #676 (Different ssl_protocols per server won`t work) created by
- I configured Nginx for two TLS virtualhost 'example.one' and …
- 10:33 Ticket #675 (spdy after a single connect send data big than 65535 , last frame size ...) created by
- I use spdy for benchmark, my test html size is 2011, when i use okhttp …
12/01/14:
- 12:40 Ticket #674 (SSL server config without cert-file passes configtest) closed by
- duplicate: Duplicate of ticket #178.
- 08:33 Ticket #674 (SSL server config without cert-file passes configtest) created by
- pys@dev116:/etc/nginx/ > cat ./conf.d/example_ssl.conf # HTTPS server …
11/29/14:
- 14:34 Ticket #673 (Redirecting with SPDY does not work) closed by
-
worksforme: It works as expected using the
spdycattool which is able to use … - 14:07 Ticket #673 (Redirecting with SPDY does not work) created by
- Using SPDY together with a 301 redirect, will result in the client …
11/28/14:
- 18:36 Ticket #132 (alert "the http output chain is empty" triggered by ssi) closed by
- fixed
- 14:05 Ticket #132 (alert "the http output chain is empty" triggered by ssi) updated by
- In 08bfc7188a41d13b47239fb393188b6f3dca16f2/nginx: […]
11/27/14:
- 12:58 Ticket #672 (Age header support) closed by
- duplicate: We already have #146.
- 10:32 Ticket #672 (Age header support) created by
- * No Age response header in cached response (2616, 14.6): […] * …
11/26/14:
- 13:47 Ticket #97 (try_files and alias problems) updated by
- I can test it on my test project. But I don't have test suite large …
- 13:35 Ticket #97 (try_files and alias problems) updated by
- And did you ever try to test the proposed patch? Due to the …
- 12:57 Ticket #97 (try_files and alias problems) updated by
- Will it ever be fixed? :)
- 11:07 Ticket #671 (X-Forwarded-For problem when using HTTPS) closed by
- invalid
- 11:06 Ticket #671 (X-Forwarded-For problem when using HTTPS) updated by
- Just a note that to keep the original X-Forwarded-For proxied to your …
- 11:04 Ticket #671 (X-Forwarded-For problem when using HTTPS) updated by
- This ticket can be closed. After i had get the same behavior with …
11/25/14:
- 21:47 Ticket #671 (X-Forwarded-For problem when using HTTPS) updated by
- 127.0.0.1/8 --> 127.0.0.0/8;
- 21:04 Ticket #671 (X-Forwarded-For problem when using HTTPS) created by
- I m using nginx as reverse proxy for some rails apps (unicorn). Im …
- 07:44 Ticket #654 (Nginx directives ignored) updated by
- Yes, I can reproduce problem with nginx provided by nginx.org. In …
11/24/14:
- 16:50 Ticket #670 (%0a. routing bypass) closed by
- invalid: The problem is in this line: […] It doesn't match unencoded URI as …
- 16:38 Ticket #670 (%0a. routing bypass) updated by
- Replying to Maxim Dounin: > Could you please show some …
- 14:52 Ticket #654 (Nginx directives ignored) updated by
- Are you able to reproduce the problem with the original nginx provided …
- 14:27 Ticket #654 (Nginx directives ignored) updated by
- I agree that response seems to be provided by Orion Server. I simply …
- 12:23 Ticket #670 (%0a. routing bypass) updated by
- Could you please show some minimal config to reproduce the problem?
- 09:57 Ticket #670 (%0a. routing bypass) updated by
- Look at ticket #191
- 09:27 Ticket #670 (%0a. routing bypass) created by
- Hello, I have noticed in my logs a following issue: […] My …
11/21/14:
- 12:45 Ticket #668 (location with spaces in URI + alias fails) closed by
- invalid: This is a result of how alias works (it just replaces matching part of …
- 09:20 Ticket #669 (Upstream keepalive connections do not properly handle early error responses) created by
- When using upstream keepalive connections and the upstream server …
11/20/14:
- 19:48 Ticket #668 (location with spaces in URI + alias fails) updated by
-
The URL was badly parsed:
http://example.org/here you go/or … - 19:43 Ticket #668 (location with spaces in URI + alias fails) created by
- When using the following configuration: […] Hitting …
- 18:13 Ticket #667 (_ (underscore) is not allow for syslog tag) updated by
- Thanks @vl, I didn't expect it to be this quick. Look forward to the …
- 17:46 Ticket #667 (_ (underscore) is not allow for syslog tag) updated by
- Since the underscore is a commonly used thing in real life, I agree …
- 17:41 Ticket #667 (_ (underscore) is not allow for syslog tag) closed by
- fixed
- 17:40 Ticket #471 (GZIP does not compress 201 Created Responses) updated by
- The statement "201 should be as safe as 200" should be backed by some …
- 17:40 Ticket #667 (_ (underscore) is not allow for syslog tag) updated by
- In 68f64bc17fa4d09392c624850e0ed5d3e3025ec4/nginx: […]
- 15:22 Ticket #471 (GZIP does not compress 201 Created Responses) updated by
- I have seen ticket 394. It doesn't say anything about 200/201 …
- 14:55 Ticket #471 (GZIP does not compress 201 Created Responses) updated by
- Please see ticket #394 for details. While it may be safe to gzip such …
- 11:29 Ticket #471 (GZIP does not compress 201 Created Responses) updated by
- I just encountered this issue today for the first time. I understand …
- 00:26 Ticket #667 (_ (underscore) is not allow for syslog tag) created by
- When running 'nginx -t', nginx complains: [emerg] syslog "tag" only …
11/19/14:
- 17:32 Ticket #666 (Nginx retry the failed http request not only from the servers defined ...) closed by
- invalid: If you need help with understanding how nginx works, consider asking …
- 17:02 Ticket #666 (Nginx retry the failed http request not only from the servers defined ...) reopened by
- 16:05 Ticket #666 (Nginx retry the failed http request not only from the servers defined ...) updated by
- So, in my case, am I correct to say since all the servers in my …
- 15:42 Ticket #666 (Nginx retry the failed http request not only from the servers defined ...) closed by
- invalid: Again: the upstream name is logged when all configured servers are …
- 14:33 Ticket #653 (Remove SSLv3 from Default ssl_protocols behavior) updated by
- Replying to Bernard Rosset <be.rosset@gmail.com>: > We are …
- 14:15 Ticket #653 (Remove SSLv3 from Default ssl_protocols behavior) updated by
- We are talking about default configuration, right? That means to …
- 13:30 Ticket #666 (Nginx retry the failed http request not only from the servers defined ...) reopened by
- 13:29 Ticket #666 (Nginx retry the failed http request not only from the servers defined ...) updated by
- Now, following is my test nginx.conf […] And I have the server …
- 13:15 Ticket #666 (Nginx retry the failed http request not only from the servers defined ...) updated by
- Replying to Maxim Dounin: > The upstream name is logged …
- 12:50 Ticket #666 (Nginx retry the failed http request not only from the servers defined ...) closed by
- invalid: The upstream name is logged when all configured servers are down.
- 11:01 Ticket #666 (Nginx retry the failed http request not only from the servers defined ...) created by
- Please read the attached nginx.conf file. This is what I want to …
11/18/14:
- 18:27 Ticket #665 ($upstream_http_var not able to be used in proxy_set_header) closed by
- duplicate
- 18:27 Ticket #664 ($upstream_http_var not able to be used in proxy_set_header) closed by
- invalid: This behaviour is correct. The $upstream_http_* variables are response …
- 18:19 Ticket #665 ($upstream_http_var not able to be used in proxy_set_header) created by
- Maybe I'm doing this wrong, but see below. == Doesn't work: == …
- 18:19 Ticket #664 ($upstream_http_var not able to be used in proxy_set_header) created by
- Maybe I'm doing this wrong, but see below. == Doesn't work: == …
- 17:53 Ticket #663 (Variable interpolation inside Map directive) updated by
- Just updated the comment. It was meant to compare the $http_referer …
- 17:31 Ticket #663 (Variable interpolation inside Map directive) updated by
- It's not clear what you are trying to do with the example, as it's …
- 17:19 Ticket #663 (Variable interpolation inside Map directive) updated by
- I would also like to base map conditions on existing variables... map …
- 15:08 Ticket #663 (Variable interpolation inside Map directive) updated by
-
Status, Type changed
This is expected behaviour. Only a single variable can be used as a … - 15:01 Ticket #663 (Variable interpolation inside Map directive) created by
- http://stackoverflow.com/questions/26976535/variable-interpolation-insi …
11/17/14:
- 13:47 Ticket #662 (Handle SSL_R_INAPPROPRIATE_FALLBACK like the other handshake failures) closed by
- fixed: Committed, thanks.
- 13:45 Ticket #662 (Handle SSL_R_INAPPROPRIATE_FALLBACK like the other handshake failures) updated by
- In b7a37f6a25eaf68efaa16dbc61ae925745b479a3/nginx: […]
- 06:07 Ticket #662 (Handle SSL_R_INAPPROPRIATE_FALLBACK like the other handshake failures) created by
- Handle the new SSL_R_INAPPROPRIATE_FALLBACK like the other handshake …
11/16/14:
- 03:35 Ticket #319 (koi-utf koi-win win-utf in conf are artifacts of the past) reopened by
- I dislike these archaic files being installed into the nginx …
11/15/14:
11/12/14:
- 15:35 Ticket #660 (Documentation on `location` directive lacks info on prefix strings) closed by
- worksforme: The documentation explicitly says "A location can either be defined by …
- 13:51 Ticket #660 (Documentation on `location` directive lacks info on prefix strings) created by
- The following configuration code in nginx will match any request URI …
Note:
See TracTimeline
for information about the timeline view.
