Timeline
07/26/16:
- 23:09 Ticket #1033 (nginx configtest doesn't fail when missing semicolon on server_name ...) created by
- I was tracking down an issue where workers were not being assigned as …
- 16:43 Ticket #1032 (1.11.3 doesn't build if built with stream support, but without ...) closed by
- fixed
- 16:40 Ticket #1032 (1.11.3 doesn't build if built with stream support, but without ...) updated by
- In [changeset:"d43ee392e825186545d81e683b88cc58ef8479bc/nginx" …
- 16:00 Ticket #1032 (1.11.3 doesn't build if built with stream support, but without ...) updated by
-
Status changed
- 15:48 Ticket #1032 (1.11.3 doesn't build if built with stream support, but without ...) created by
- I built 1.11.3 using a spec file that worked with 1.11.2. However, it …
- 15:10 Milestone 1.11.3 completed
- Status: released Trunk: mainline * Stream's goodies: resolver, …
07/22/16:
- 22:08 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- Since the connection is going to pass to lingering, and with the patch …
- 15:21 Ticket #1031 (nginx return 416 error if client set Range header and requested file < ...) updated by
- What makes you think that the current behaviour is invalid? Quoting …
- 14:11 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- It doesn't matter what application server will return in its response …
- 13:21 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- I think I need to see this in action with keep-alive working. I'm …
- 10:15 Ticket #1031 (nginx return 416 error if client set Range header and requested file < ...) updated by
- Sorry, problem only if file zero size. HEAD /do_not_delete.txt …
- 09:33 Ticket #1031 (nginx return 416 error if client set Range header and requested file < ...) created by
- File do_not_delete.txt exist, size zero or 1 byte. HEAD …
07/21/16:
- 22:15 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- Replying to iamasmith.home@…: > I may be misunderstanding …
- 18:17 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- Replying to mdounin: > .... >What may help is always …
- 16:38 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- Yes, currently the keepalive timeout is set to 0 and we do see …
- 16:19 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- Overall, it looks like a CFNetwork problem, it seems to not be able to …
- 16:12 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- You may also try if disabled keepalive will make any difference (that …
- 15:22 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- Just finished... it took a little while because I don't maintain this …
- 08:37 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- OK, interesting, I reviewed the traffic being sent by the client using …
07/20/16:
- 15:47 Ticket #1030 (100% CPU with hash consistent balancing method without live upstreams) updated by
- Such configuration results in a …
- 14:55 Ticket #1029 ([Feature request] Please enable support for SPDY + HTTP/2 at the same ...) closed by
- wontfix: > in some real cases advertising and supporting also SPDY can give …
- 14:52 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- As explained in comment:5, the mode suggested (without …
- 13:53 Ticket #1029 ([Feature request] Please enable support for SPDY + HTTP/2 at the same ...) updated by
- Just some stats for consideration. As of now, SPDY is supported by …
- 13:36 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- Actually, I can see other scenarios where it may be desirable to …
- 13:07 Ticket #1030 (100% CPU with hash consistent balancing method without live upstreams) created by
- Good day, For caching purposes I have the following upstream …
- 01:33 Ticket #1029 ([Feature request] Please enable support for SPDY + HTTP/2 at the same ...) created by
- I know it's not so 'cool' to ask for this, now that http/2 is working …
07/19/16:
- 20:33 Ticket #1028 (Build failure on debian-kbsd) updated by
- I can't confirm. While nginx does not recognize Debian/kFreeBSD, it …
- 17:49 Ticket #1003 (Growing amount of active connections with http/2) closed by
- fixed: I suppose it to be fixed by e78eca6bfaf0, b5d1c17181ca, and …
- 12:10 Ticket #1027 (HTTP2 Long URL issues) closed by
- invalid: These settings are irrelevant to the HTTP/2 module. Please, read the …
- 07:13 Ticket #1027 (HTTP2 Long URL issues) updated by
- Does it work with 64k in large_client_header_buffers? […]
- 02:09 Ticket #1028 (Build failure on debian-kbsd) created by
- Downstream bug report: https://bugs.debian.org/826061 The patch that …
- 00:49 Ticket #1027 (HTTP2 Long URL issues) created by
- Long URLs appear to be broken with HTTP2. The threshold I've observed …
07/18/16:
- 17:23 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- (for policy control over the stack I mean things like standard …
- 17:22 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- Also great feedback. I did consider what one might lose if shutdown …
- 11:06 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- Client _can_ maintain the SSL/TLS layer, it continue sending data but …
- 08:31 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- So, summarising what is actually happening. 1. Response is sent back …
- 07:46 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- Many thanks mdounin@ that was bang on the money. I would argue that …
07/15/16:
- 22:12 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- It is a good point, however, there is a difference in behaviour …
- 18:20 Ticket #826 (Add config option for NGX_HTTP_CACHE_VARY_LEN) updated by
- As a reference point, varnish actually …
- 18:08 Ticket #826 (Add config option for NGX_HTTP_CACHE_VARY_LEN) reopened by
- I agree that adding a configuration option seems overkill, but I would …
- 17:52 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) updated by
- The goal of the lingering close code is to prevent TCP RST from being …
- 15:45 Ticket #1025 (No country detected for requests with X-Forwarded-For 127.0.0.1 or any ...) updated by
-
Type changed
It looks like you are asking for something similar to … - 14:36 Ticket #1026 (Abrupt linger disconnect on SSL offload connections through nginx ...) created by
- Relevant settings To ensure that chunked encoding is passed directly …
- 10:56 Ticket #1025 (No country detected for requests with X-Forwarded-For 127.0.0.1 or any ...) updated by
- Sorry Alternative solution is not correct and does not solve the problem.
- 10:43 Ticket #1025 (No country detected for requests with X-Forwarded-For 127.0.0.1 or any ...) created by
- I use ngx_http_geoip_module to detect origin country of every request …
07/14/16:
- 20:50 Ticket #1009 (Upstream sent invalid header while reading response header from upstream) updated by
- Replying to mdounin: > The error suggests there is NUL …
- 20:35 Ticket #1024 (openssl: crl processing fails with X509_NAME_EX_D2I:too long) closed by
- wontfix: Any OpenSSL fixes are expected to be available once a new version of …
- 19:01 Ticket #1024 (openssl: crl processing fails with X509_NAME_EX_D2I:too long) updated by
- Here is the fix, can someone please patch this and provide a windows …
- 18:52 Ticket #1024 (openssl: crl processing fails with X509_NAME_EX_D2I:too long) created by
- Hello, Is it possible to port this bugfix into NGINX Windows Binary? …
07/13/16:
- 12:46 Ticket #1023 (SNI problem with nginx and apache httpclient) closed by
- invalid: This doesn't looks like a problem in nginx. Likely the client you use …
- 12:13 Ticket #1023 (SNI problem with nginx and apache httpclient) updated by
- with apache httpclient 4.5.3-SNAPSHOT problem is solved! I have …
- 08:24 Ticket #1023 (SNI problem with nginx and apache httpclient) created by
- Using this code causes problems when connecting to nginx server. I …
07/12/16:
- 17:30 Ticket #1022 (Nginx graceful shutdown doesn't inform clients to close "keep-alive" ...) closed by
- wontfix: During configuration reload existing connections are closed as soon as …
- 15:03 Ticket #1022 (Nginx graceful shutdown doesn't inform clients to close "keep-alive" ...) created by
- In case a client uses the keep-alive feature to make requests, during …
- 14:30 Ticket #1021 (Ports 11310 and 11820 are considered to be the same) closed by
- fixed: Thanks, this is already fixed by 6f8254ae61b8 (see 68854ce64ec7 for …
- 14:13 Ticket #1021 (Ports 11310 and 11820 are considered to be the same) created by
- Steps to reproduce Configure two server blocks in stream …
07/11/16:
- 22:24 Ticket #933 (include with wildcard but non-existent parent is not detected by nginx -t) updated by
- You've been understood. Including all files from a directory if the …
- 18:33 Ticket #933 (include with wildcard but non-existent parent is not detected by nginx -t) updated by
- Replying to mdounin: > Wildcard includes intentionally …
07/08/16:
- 10:08 Ticket #1015 (image_filter module failure to perform image_filter_jpeg_quality step) updated by
- > Sets the desired quality of the transformed JPEG images. I think …
07/06/16:
- 20:53 Ticket #1020 (Allow proxy_http_version to use variables) updated by
- Thanks.
- 19:19 Ticket #1020 (Allow proxy_http_version to use variables) closed by
-
wontfix: Just use
proxy_http_version 1.1. Most modern backends handle this … - 19:01 Ticket #1020 (Allow proxy_http_version to use variables) created by
-
I would like to conditionally set the
proxy_http_versionsuch that … - 12:56 Ticket #1019 (400 Bad request error on Edge Browser) closed by
- duplicate: Looks like a duplicate of #830. Please see 830#comment:1, …
- 12:56 Ticket #830 (400 Bad Request - No required SSL certificate was sent occurs randomly ...) updated by
- See also #1019.
- 12:47 Ticket #1002 (worker process 9255 exited on signal 11 (core dumped)) closed by
- worksforme: Feedback timeout. Looks like a problem in a 3rd party module.
- 03:30 Ticket #1019 (400 Bad request error on Edge Browser) updated by
- uname -a Linux ip-10-70-10-108 3.13.0-35-generic #62-Ubuntu SMP Fri …
- 03:25 Ticket #1019 (400 Bad request error on Edge Browser) created by
- Hi Support, our website uses client side certs and while accessing …
07/05/16:
- 16:15 Milestone 1.11.2 completed
- Status: released Trunk: mainline * maps and vars support in …
- 10:59 Ticket #1018 (nginx.org debian repo package inconsistent with official debian) closed by
- invalid: Official nginx.org packages were never intended to be a drop-in …
- 10:12 Ticket #1015 (image_filter module failure to perform image_filter_jpeg_quality step) closed by
- invalid: Replying to kenoir@…: > So to be clear you are stating …
- 10:02 Ticket #1018 (nginx.org debian repo package inconsistent with official debian) updated by
- IMHO it's not bug because Debian/Ubuntu package from nginx.org …
- 09:27 Ticket #1018 (nginx.org debian repo package inconsistent with official debian) created by
- Hi, package available in {{{deb …
- 08:41 Ticket #1015 (image_filter module failure to perform image_filter_jpeg_quality step) reopened by
- 08:41 Ticket #1015 (image_filter module failure to perform image_filter_jpeg_quality step) updated by
-
So to be clear you are stating
image_filter_jpeg_qualitycannot be …
07/04/16:
- 12:02 Ticket #814 (Support for parallel ECDSA / RSA certificates) updated by
- LibreSSL doesn't have support for multiple certificate chains and …
- 11:02 Ticket #1000 (Domain-relative redirects doesn't work, they are absolute instead) updated by
- Yes, nginx does not know public origin behind proxy. It only knows …
07/03/16:
- 21:36 Ticket #814 (Support for parallel ECDSA / RSA certificates) updated by
- And some additional info. As you can see both ECDSA and RSA based …
- 21:18 Ticket #814 (Support for parallel ECDSA / RSA certificates) updated by
- Some additional info about my Gentoo Linux Nginx server: […] …
07/02/16:
- 12:31 Ticket #1011 (Allow changing 'Server' header in HTTP/2) updated by
- Oh! I see, thanks for explaining.
- 12:05 Ticket #1011 (Allow changing 'Server' header in HTTP/2) updated by
- And the summary of the #936 says "For security purposes it is …
07/01/16:
- 23:40 Ticket #1011 (Allow changing 'Server' header in HTTP/2) updated by
- Replying to mdounin: > And that's why this ticket is …
- 22:21 Ticket #1017 (Custom Error page not possible if uri contains % + Special Character) closed by
-
invalid: The
%character is only valid in URI if followed by two hexadecimal … - 22:19 Ticket #1011 (Allow changing 'Server' header in HTTP/2) updated by
- Replying to raeesiqbal@…: > The purpose of this patch is …
- 21:01 Ticket #1011 (Allow changing 'Server' header in HTTP/2) updated by
- Nevermind, there was an issue with HTTP/2 module but it has been …
- 20:43 Ticket #1011 (Allow changing 'Server' header in HTTP/2) updated by
- @vbart I've just updated the patch and have confirmed it to be working …
- 20:21 Ticket #1017 (Custom Error page not possible if uri contains % + Special Character) created by
- If a user calls a not existing website on my server my application …
- 19:16 Ticket #1014 (RFC 7230 Compliance: Err 400 on space+colon for header field separator) updated by
- OK, but the problem is not this specific character. It's more about …
- 18:22 Ticket #1014 (RFC 7230 Compliance: Err 400 on space+colon for header field separator) updated by
- There are 256 different 1-byte characters, and only about 70 of them …
- 17:56 Ticket #814 (Support for parallel ECDSA / RSA certificates) updated by
- The error reported suggests that you are using an old OpenSSL (before …
- 17:51 Ticket #1014 (RFC 7230 Compliance: Err 400 on space+colon for header field separator) updated by
- Well, at least it would prevent innocent errors from bad http client …
- 17:44 Ticket #1015 (image_filter module failure to perform image_filter_jpeg_quality step) closed by
-
invalid: The
image_filter_jpeg_qualitydirective isn't a step, is't a … - 17:36 Ticket #1016 (limit_except accepts multiple methods but docs don't say so) closed by
- invalid: The syntax provided in the documentation is as follows: […] The …
- 17:07 Ticket #1014 (RFC 7230 Compliance: Err 400 on space+colon for header field separator) updated by
- Current nginx behaviour predates RFC 7230 by years and universally …
- 16:18 Ticket #1011 (Allow changing 'Server' header in HTTP/2) updated by
- Could you clarify the purpose of this change? Your patch breaks the …
- 13:44 Ticket #1011 (Allow changing 'Server' header in HTTP/2) updated by
- bump.…
- 12:43 Ticket #1016 (limit_except accepts multiple methods but docs don't say so) created by
- The …
- 09:32 Ticket #1015 (image_filter module failure to perform image_filter_jpeg_quality step) created by
- When nginx is built from source to include the image_filter module as …
06/30/16:
- 17:23 Ticket #1011 (Allow changing 'Server' header in HTTP/2) updated by
- This ticket is completely different from ticket #936, which talks …
- 15:57 Ticket #1014 (RFC 7230 Compliance: Err 400 on space+colon for header field separator) created by
- https://tools.ietf.org/html/rfc7230#section-3.2.4 > No whitespace is …
- 15:20 Ticket #814 (Support for parallel ECDSA / RSA certificates) updated by
- I got my RSA and ECDSA certificates from Let's Encrypt. So, both …
- 15:13 Ticket #1013 (problem on restart nginx) created by
- Hi all, we have some nginx on production environment. I have see this …
- 14:22 Ticket #1012 (Allow changing 'Server' header in HTTP/2) closed by
- duplicate: Duplicate of #1011.
- 14:18 Ticket #1012 (Allow changing 'Server' header in HTTP/2) created by
- The 'server' header has been hardcoded for HTTP/2 with `u_const …
- 13:02 Ticket #1011 (Allow changing 'Server' header in HTTP/2) closed by
- duplicate
- 13:02 Ticket #1011 (Allow changing 'Server' header in HTTP/2) updated by
- Duplicate of #936. Please also note that referring to identifiers in …
- 12:38 Ticket #1011 (Allow changing 'Server' header in HTTP/2) created by
- Commit 531e6fbfd6c785a7b42c285c12d3f0721cc989c7 introduced HPACK …
- 09:56 Ticket #1010 (Invalid request sent when serving error pages from upstream) created by
- The bug appears when request_body_buffering is off (but maybe not …
06/29/16:
- 20:12 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- The RFC 2616 is foggy in some places. However, RFC 7231 attempts to …
- 18:21 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- The first option is basically identical to what RFC 2616 recommends in …
- 17:37 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- After researching the RFC, I agree with you about the second option. …
- 17:07 Ticket #1006 (two more server listen 443(ssl), none-default server's ...) updated by
- Replying to cjhust1986@…: > if we parse tlsext server_name …
- 16:38 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- The only thing to do with the rest of body bytes after an error is to …
- 15:19 Ticket #1009 (Upstream sent invalid header while reading response header from upstream) closed by
- worksforme: Unless you have some additional information to support the idea there …
- 15:18 Ticket #1009 (Upstream sent invalid header while reading response header from upstream) updated by
- The error suggests there is NUL character or stray CR character (not …
- 14:52 Ticket #1008 (Nginx ignores reload) closed by
- worksforme: Normal nginx behaviour is to reject a configuration if there are any …
- 14:11 Ticket #1007 (Version 1.10.0->1.10.1 config with alias with versioning failed to work) updated by
- Thank you for the quick answer. I modified all of these entries in my …
- 13:11 Ticket #1007 (Version 1.10.0->1.10.1 config with alias with versioning failed to work) closed by
- duplicate: Changes between 1.10.0 and 1.10.1 do not affect the above …
- 12:40 Ticket #1009 (Upstream sent invalid header while reading response header from upstream) created by
- Some background: in our solution we've got several Java microservices …
- 11:41 Ticket #1008 (Nginx ignores reload) created by
- Good day. We've bumped with the problem, when nginx don't update …
- 08:57 Ticket #1007 (Version 1.10.0->1.10.1 config with alias with versioning failed to work) created by
- I was upgrading from 1.10.0 to 1.10.1 and nginx was getting failed to …
- 03:15 Ticket #1006 (two more server listen 443(ssl), none-default server's ...) updated by
- if we parse tlsext server_name (ssl_scan_clienthello_tlsext) before …
06/28/16:
- 22:42 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- Hmmm... there seems to be some confusion still. Why would the Amazon …
- 22:30 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- Again: there is no "Amazon ELB to nginx timeout incompatibility". …
- 21:26 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- The reason I'm setting 'Content-Length' to an incorrect value is …
- 21:19 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- By manually defining "Content-Length" to an incorrect value you …
- 21:04 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- Here another example of how nginx confuses the httpie [1] client: …
- 20:52 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- "Fixing the client is a correct way to go if you want problems to be …
- 20:37 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- Replying to simonhf@…: > However, at this point the …
- 20:35 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- Interestingly, the current nginx behavior of a TCP connection drop to …
- 20:26 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- Here's what the nginx timeout looks like with and without the patch: …
- 20:09 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- FYI I've been working on a small patch which works as follows: If the …
- 19:55 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- Maybe we are talking about the same thing? When I say the "request is …
- 18:27 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- Monitoring a connection for errors is not the same as "signal that the …
- 18:01 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- "there is no way to "signal that the 1st request is finished"" This …
- 16:48 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- In HTTP/1.x there is no way to "signal that the 1st request is …
- 16:23 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- Thanks for the comments. Disclaimer: The perl code is just a quick …
- 14:47 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- The perl code in question does the following: 1. sends part of a …
- 14:16 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- Thanks for looking at the perl code in case there's a bug in it. …
- 11:04 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- It looks like the problem is in the client then: it fails to send the …
- 01:30 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- FYI Amazon is also refusing to change / fix anything. They say the …
06/27/16:
- 18:39 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- WRT 504: I agree with you that 504 is perhaps not the best choice. …
- 18:29 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- From what you describe it looks like ELB just screws up protocol …
- 18:01 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- Would it be possible to add an option to nginx to switch on sending …
- 16:55 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- Returning a response in case of timeouts almost always doesn't make …
- 16:17 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
- Why is it preferred to drop the connection (potentially upsetting the …
- 12:59 Ticket #1003 (Growing amount of active connections with http/2) updated by
- This problem is likely similar to the one that has been already …
- 12:25 Ticket #1006 (two more server listen 443(ssl), none-default server's ...) closed by
- wontfix: Yes, that's expected behaviour. Sessions are saved/restored by OpenSSL …
- 12:17 Ticket #1005 (client_body_timeout does not send 408 as advertised) updated by
-
Component changed
Yes, no 408 response is returned. That's expected behaviour, … - 03:16 Ticket #1006 (two more server listen 443(ssl), none-default server's ...) created by
- server{ listen 443 ssl default_server; server_name a.com; ... …
Note:
See TracTimeline
for information about the timeline view.
